=== snadg3 is now known as snadge [13:03] Can I speak? Or do I need to register first? [13:03] OK. Looks like I can speak. Can somebody help me fill in the blanks in this bug? https://bugs.launchpad.net/ubuntu/+bug/1771109 [13:03] Ubuntu bug 1771109 in Ubuntu "Domain names containing emoji characters are not supported in console applications" [Undecided,New] [20:22] So, it's been a long time since I last reported an ubuntu bug, and I don't really remember the process. [20:22] `ubuntu-bug PACKAGE` on the terminal [20:22] Can somebody check my bug report and tell me whether it's alright? https://bugs.launchpad.net/ubuntu/+bug/1771109 [20:22] Ubuntu bug 1771109 in libidn2-0 (Ubuntu) "Domain names containing emoji characters are not supported in console applications" [Undecided,New] [20:22] without the backticks [20:23] augeus: that looks like a curl bug/error, it might not be the library but something that's not configured properly. [20:24] teward, I see! However, I get the same error when using telnet/ssh/other apps [20:24] that's because emoji aren't valid IDNs [20:24] so this is a blog post that touches on it, a little... https://daniel.haxx.se/blog/2015/02/24/curl-smiley-urls-and-libc/ [20:24] However, they seem to exist, and firefox accepts them without complaining [20:25] not saying that's not true, but it may requires some 'fun' to work properly. [20:25] * augeus bought an emoji domain for novelty's sake, then found out this [20:25] I think this is more of a spec problem for IDN [20:25] IDN allowed some emojis, then a later RFC disallowed it [20:25] so depending on IDN spec emojis may or may not be valid [20:25] * augeus knows.. I did my googling [20:25] I believe that the proper behavior should be looking the domain up, and returning a warning [20:26] augeus: the question is how it's translated, which sounds like a resolver / glib issue, but i'm not confident in that [20:26] So, is it a bug or a feature? [20:26] I get that it's not standard, but such domains exist, and can be bought [20:27] augeus: not discounting, but keep in mind 'new' specs come up and libraries aren't always up-to-date with latest spec [20:27] My two cents: THis is neither a feature nor a bug, and is more a case of an undefined spec. [20:27] so therefore in some cases it's a bug, and in some cases it's a feature. [20:27] I see.. So, how should I report this? [20:27] I think this is a "Leave the bug, and let the devs figure it out" type situation. [20:27] augeus: the way you did seems fine, but I think it's going to be an 'open ended' discussion to trace it [20:28] just my two cents [20:28] I'm fairly tired, just came back home, so forgive me if I cannot parse properly [20:28] nah you're fine. I've been staring at email server logs all day so I'm in the same boat :P [20:28] I see. :) [20:29] So, should I add something to my bug report to increase my chances of getting a response? [21:12] Anyway, thanks for your time, teward - Good luck with your troubleshooting