Conversation

Notices

1. Embed this notice
   Ada (ada@mk.wytch.space)'s status on Sunday, 20-Aug-2023 06:39:26 JST Ada

   yesterday i found out that "i am a fox"@[IPv6::0000:0000:0000:0000:0000:0000:0000:0001] is a valid email address.

   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     feld (feld@bikeshed.party)'s status on Sunday, 20-Aug-2023 06:42:02 JST feld

     in reply to

     • :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:
     • sam :verified_woem:
     • Natty :butterflyN:
     UTF8 support in domains DOES exist
     
     http://🦇🍲😋.eth.co
   • Embed this notice
     :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse: (selea@social.linux.pizza)'s status on Sunday, 20-Aug-2023 06:42:04 JST :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:

     in reply to

     • sam :verified_woem:
     • Natty :butterflyN:

     @natty

     There is talks about making utf8 support in domains possible.

     Imagine a site called https://🤮.💩

     @starshine @ada

   • Embed this notice
     Natty :butterflyN: (natty@astolfo.social)'s status on Sunday, 20-Aug-2023 06:42:05 JST Natty :butterflyN:

     in reply to

     • sam :verified_woem:

     @starshine@woem.space @ada@mk.wytch.space I have a pending follow request from https://🌈🌈🌈.st :blobfoxnotlikethisgoogly:

   • Embed this notice
     sam :verified_woem: (starshine@woem.space)'s status on Sunday, 20-Aug-2023 06:42:07 JST sam :verified_woem:

     in reply to

     @ada does that mean i can’t send email from "😳👉👈"@starshines.gay :neofox_cry:

   • Embed this notice
     Ada (ada@mk.wytch.space)'s status on Sunday, 20-Aug-2023 06:42:08 JST Ada

     in reply to

     • sam :verified_woem:

     @starshine@woem.space not sure, the spec is written for compliance with 7-bit ascii and emoji are utf8 multibyte sequences

   • Embed this notice
     sam :verified_woem: (starshine@woem.space)'s status on Sunday, 20-Aug-2023 06:42:09 JST sam :verified_woem:

     in reply to

     @ada aren’t emoji technically valid too, just rejected by almost everything

   • Embed this notice
     Ada (ada@mk.wytch.space)'s status on Sunday, 20-Aug-2023 06:42:10 JST Ada

     in reply to

     gl finding anything that lets you send email from this
     
     but yeah apparently email is @ where host part can be any valid address, and local part can be any ascii string without control characters, and that includes spaces if you use quotes.

   • Embed this notice
     feld (feld@bikeshed.party)'s status on Sunday, 20-Aug-2023 06:43:42 JST feld

     in reply to

     • :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:
     • sam :verified_woem:
     • Natty :butterflyN:
     Some don't need conversion to punycode. I have examples, I had to do thorough testing of this a few months back
   • Embed this notice
     :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse: (selea@social.linux.pizza)'s status on Sunday, 20-Aug-2023 06:43:43 JST :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:

     in reply to

     • feld
     • sam :verified_woem:
     • Natty :butterflyN:

     @feld @natty @ada @starshine

     Yes with punycode, nothing new

   • Embed this notice
     feld (feld@bikeshed.party)'s status on Sunday, 20-Aug-2023 07:41:47 JST feld

     in reply to

     • :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:
     • sam :verified_woem:
     • Natty :butterflyN:
     The emojis need to be within a certain codepoint range and if I recall correctly it only worked in Firefox and Brave IIRC. The Safari and others converted to punycode, but these supported the emojis in the location/address bar.
   • Embed this notice
     :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse: (selea@social.linux.pizza)'s status on Sunday, 20-Aug-2023 07:41:48 JST :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:

     in reply to

     • feld
     • sam :verified_woem:
     • Natty :butterflyN:

     @feld

     Really, what examples?

     @natty @ada @starshine

   • Embed this notice
     feld (feld@bikeshed.party)'s status on Sunday, 20-Aug-2023 07:45:08 JST feld

     in reply to

     • :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:
     • sam :verified_woem:
     • Natty :butterflyN:
     The user was *never* shown punycode in this scenario, which is the important part.
   • Embed this notice
     :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse: (selea@social.linux.pizza)'s status on Sunday, 20-Aug-2023 07:45:09 JST :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:

     in reply to

     • feld
     • sam :verified_woem:
     • Natty :butterflyN:

     @feld

     So punycode then ;)

     @natty @ada @starshine

   • Embed this notice
     feld (feld@bikeshed.party)'s status on Sunday, 20-Aug-2023 07:47:34 JST feld

     in reply to

     • :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:
     • sam :verified_woem:
     • Natty :butterflyN:
     I'll have to ask the frontend devs if they received punycode in javascript for window.location, but I believe they did not.
     
     Searching for this is annoying as my discussions around this were all in our Discord LOL
   • Embed this notice
     :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse: (selea@social.linux.pizza)'s status on Sunday, 20-Aug-2023 07:47:36 JST :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:

     in reply to

     • feld
     • sam :verified_woem:
     • Natty :butterflyN:

     @feld

     Well that is how it used to work, until the famous apple.com example

     @natty @ada @starshine

   • Embed this notice
     feld (feld@bikeshed.party)'s status on Sunday, 20-Aug-2023 07:59:58 JST feld

     in reply to

     • :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:
     • sam :verified_woem:
     • Natty :butterflyN:
     Just found a working example in Safari, but this has another issue (should be a black cat)
   • Embed this notice
     :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse: (selea@social.linux.pizza)'s status on Sunday, 20-Aug-2023 08:00:00 JST :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:

     in reply to

     • feld
     • sam :verified_woem:
     • Natty :butterflyN:

     @feld

     The domain is always punycoded, it is up to the browsers to display it or not
     It all changed when this got the attention of the big companies, even if other has warned against it for years

     https://www.xudongz.com/blog/2017/idn-phishing/

     Just a week after this article, Chrome chosed to display the punycode instead of the utf-8 encoded characters. Up until that point, every browser did

     @natty @ada @starshine

   • Embed this notice
     Sexy Moon (moon@shitposter.club)'s status on Sunday, 20-Aug-2023 08:01:12 JST Sexy Moon

     in reply to

     • feld
     • :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:
     • sam :verified_woem:
     • Natty :butterflyN:
     @feld @natty @ada @selea @starshine it is actually broken out that way on purpose according to display guidelines. it is meant to prevent spoofing.
     feld likes this.
   • Embed this notice
     feld (feld@bikeshed.party)'s status on Sunday, 20-Aug-2023 08:02:45 JST feld

     in reply to

     • Sexy Moon
     • :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:
     • sam :verified_woem:
     • Natty :butterflyN:
     Ahh right.
     
     This is all stupidly complicated 🥹
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Sunday, 20-Aug-2023 10:21:46 JST Haelwenn /элвэн/ :triskell:

     in reply to

     @ada Well email is nearly anything goes in terms of encoding but then implementations have all kinds of limitations, which is why the best is to try sending.

     OpenSMTPd says 501 5.1.3 Recipient address syntax error for that email address btw.

   • Embed this notice
     LEdoian (ledoian@pleroma.ledoian.cz)'s status on Sunday, 20-Aug-2023 19:16:05 JST LEdoian

     in reply to

     • Haelwenn /элвэн/ :triskell:

     @lanodan @ada I checked RFC 5321 and there should only be one or three colons after IPv6 (i.e. either [IPv6:0:0:…] or [IPv6:::1]). The initial colon is separator of the address type and actual address.

     Then my Postfix accepts it says there is no such user (obviously), before it was bad syntax.

     the best is to try sending

     Does anyone remember the VRFY command?

     Haelwenn /элвэн/ :triskell: likes this.