home.social

#idn — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #idn, aggregated by home.social.

  1. Introducing: Support for laser DACs by Bitlasers

    In our ongoing quest to making #vvvv a great tool for operating lasers, we've just added support for another series of laser DACs, see: vvvv.org/blog/2026/introducing

    #visualprogramming #creativecoding #dotnet #laser #dac #bitlaser #idn

  2. Introducing: Support for laser DACs by Bitlasers

    In our ongoing quest to making #vvvv a great tool for operating lasers, we've just added support for another series of laser DACs, see: vvvv.org/blog/2026/introducing

    #visualprogramming #creativecoding #dotnet #laser #dac #bitlaser #idn

  3. Introducing: Support for laser DACs by Bitlasers

    In our ongoing quest to making #vvvv a great tool for operating lasers, we've just added support for another series of laser DACs, see: vvvv.org/blog/2026/introducing

    #visualprogramming #creativecoding #dotnet #laser #dac #bitlaser #idn

  4. Introducing: Support for laser DACs by Bitlasers

    In our ongoing quest to making #vvvv a great tool for operating lasers, we've just added support for another series of laser DACs, see: vvvv.org/blog/2026/introducing

    #visualprogramming #creativecoding #dotnet #laser #dac #bitlaser #idn

  5. Introducing: Support for laser DACs by Bitlasers

    In our ongoing quest to making #vvvv a great tool for operating lasers, we've just added support for another series of laser DACs, see: vvvv.org/blog/2026/introducing

    #visualprogramming #creativecoding #dotnet #laser #dac #bitlaser #idn

  6. When a top domain only allow a certain set of characters, like #Norid for .no-domain norid.no/en/om-domenenavn/rege allowing only:

    á
    à
    ä
    č
    ç
    đ
    é
    è
    ê
    ï
    ŋ
    ń
    ñ
    ó
    ò
    ô
    ö
    š
    ŧ
    ü
    ž
    æ
    ø
    å

    If there exist a domain `vørterøl.no`, would it then be considered rude (or not allowed) to add non supported characters in sub domains like:

    ルートビア.vørterøl.no

    ?

    #IDN #unicode #rfc5890 #rfc5891 #rfc5892 #rfc5893 #rfc5894

  7. When a top domain only allow a certain set of characters, like #Norid for .no-domain norid.no/en/om-domenenavn/rege allowing only:

    á
    à
    ä
    č
    ç
    đ
    é
    è
    ê
    ï
    ŋ
    ń
    ñ
    ó
    ò
    ô
    ö
    š
    ŧ
    ü
    ž
    æ
    ø
    å

    If there exist a domain `vørterøl.no`, would it then be considered rude (or not allowed) to add non supported characters in sub domains like:

    ルートビア.vørterøl.no

    ?

    #IDN #unicode #rfc5890 #rfc5891 #rfc5892 #rfc5893 #rfc5894

  8. When a top domain only allow a certain set of characters, like #Norid for .no-domain norid.no/en/om-domenenavn/rege allowing only:

    á
    à
    ä
    č
    ç
    đ
    é
    è
    ê
    ï
    ŋ
    ń
    ñ
    ó
    ò
    ô
    ö
    š
    ŧ
    ü
    ž
    æ
    ø
    å

    If there exist a domain `vørterøl.no`, would it then be considered rude (or not allowed) to add non supported characters in sub domains like:

    ルートビア.vørterøl.no

    ?

    #IDN #unicode #rfc5890 #rfc5891 #rfc5892 #rfc5893 #rfc5894

  9. When a top domain only allow a certain set of characters, like #Norid for .no-domain norid.no/en/om-domenenavn/rege allowing only:

    á
    à
    ä
    č
    ç
    đ
    é
    è
    ê
    ï
    ŋ
    ń
    ñ
    ó
    ò
    ô
    ö
    š
    ŧ
    ü
    ž
    æ
    ø
    å

    If there exist a domain `vørterøl.no`, would it then be considered rude (or not allowed) to add non supported characters in sub domains like:

    ルートビア.vørterøl.no

    ?

    #IDN #unicode #rfc5890 #rfc5891 #rfc5892 #rfc5893 #rfc5894

  10. When a top domain only allow a certain set of characters, like #Norid for .no-domain norid.no/en/om-domenenavn/rege allowing only:

    á
    à
    ä
    č
    ç
    đ
    é
    è
    ê
    ï
    ŋ
    ń
    ñ
    ó
    ò
    ô
    ö
    š
    ŧ
    ü
    ž
    æ
    ø
    å

    If there exist a domain `vørterøl.no`, would it then be considered rude (or not allowed) to add non supported characters in sub domains like:

    ルートビア.vørterøl.no

    ?

    #IDN #unicode #rfc5890 #rfc5891 #rfc5892 #rfc5893 #rfc5894

  11. Whatever happened to the . الكويت #IDN #cctld? There were a ton of references to it a couple of years back, but now I can't find any no mater where I look. It's as if it never existed. its not... punny.

    ...

    Okay, I'll get my bisht.

    Seriously, the only references I could find were some stale example in the registrar's official policies. I wonder if there is a way to look up the registration status at ICANN.

    Punycode: xn--mgbg8edvm

    #ICANN #CITRA #Kuwait #kw

  12. Encore un correcteur trop zélé (c'est legarcon.net, pas legarçon.net)

    #IDN #DNS

  13. Encore un correcteur trop zélé (c'est legarcon.net, pas legarçon.net)

    #IDN #DNS

  14. Encore un correcteur trop zélé (c'est legarcon.net, pas legarçon.net)

    #IDN #DNS

  15. Encore un correcteur trop zélé (c'est legarcon.net, pas legarçon.net)

    #IDN #DNS

  16. Encore un correcteur trop zélé (c'est legarcon.net, pas legarçon.net)

    #IDN #DNS

  17. Le dernier numéro du magazine du département fait la pub d’un commerce en donnant l’URL de son site internet, avec un caractère accentué dans le nom de domaine en .fr… sauf que le domaine ne marche pas. Il faut supprimer l’accent pour que ça fonctionne.

    J’ai écrit à la rédactrice en chef pour signaler la coquille et expliquer que accent ou pas d’accent, ça fait deux noms de domaines
    différents.

    #IDN

  18. Le dernier numéro du magazine du département fait la pub d’un commerce en donnant l’URL de son site internet, avec un caractère accentué dans le nom de domaine en .fr… sauf que le domaine ne marche pas. Il faut supprimer l’accent pour que ça fonctionne.

    J’ai écrit à la rédactrice en chef pour signaler la coquille et expliquer que accent ou pas d’accent, ça fait deux noms de domaines
    différents.

    #IDN

  19. Le dernier numéro du magazine du département fait la pub d’un commerce en donnant l’URL de son site internet, avec un caractère accentué dans le nom de domaine en .fr… sauf que le domaine ne marche pas. Il faut supprimer l’accent pour que ça fonctionne.

    J’ai écrit à la rédactrice en chef pour signaler la coquille et expliquer que accent ou pas d’accent, ça fait deux noms de domaines
    différents.

    #IDN

  20. Le dernier numéro du magazine du département fait la pub d’un commerce en donnant l’URL de son site internet, avec un caractère accentué dans le nom de domaine en .fr… sauf que le domaine ne marche pas. Il faut supprimer l’accent pour que ça fonctionne.

    J’ai écrit à la rédactrice en chef pour signaler la coquille et expliquer que accent ou pas d’accent, ça fait deux noms de domaines
    différents.

    #IDN

  21. Le dernier numéro du magazine du département fait la pub d’un commerce en donnant l’URL de son site internet, avec un caractère accentué dans le nom de domaine en .fr… sauf que le domaine ne marche pas. Il faut supprimer l’accent pour que ça fonctionne.

    J’ai écrit à la rédactrice en chef pour signaler la coquille et expliquer que accent ou pas d’accent, ça fait deux noms de domaines
    différents.

    #IDN

  22. I think developers doing somthing that communicates with hosts or displays host name should have access to a internationalized domain name (IDN) en.wikipedia.org/wiki/Internat

    #IDN #InternationalizedDomainName

  23. I think developers doing somthing that communicates with hosts or displays host name should have access to a internationalized domain name (IDN) en.wikipedia.org/wiki/Internat

    #IDN #InternationalizedDomainName

  24. I think developers doing somthing that communicates with hosts or displays host name should have access to a internationalized domain name (IDN) en.wikipedia.org/wiki/Internat

    #IDN #InternationalizedDomainName

  25. I think developers doing somthing that communicates with hosts or displays host name should have access to a internationalized domain name (IDN) en.wikipedia.org/wiki/Internat

    #IDN #InternationalizedDomainName

  26. I think developers doing somthing that communicates with hosts or displays host name should have access to a internationalized domain name (IDN) en.wikipedia.org/wiki/Internat

    #IDN #InternationalizedDomainName

  27. WEBINAR MAR 26 – APRALO Policy Forum Webinar Series on A Multilingual Internet #2: IDN Policies and Implementation

    REGISTER | ADD TO CALENDAR | PERMALINK

    On Thursday 26 March 2026, at 06:00-07:15 UTC, the APRALO Policy Forum will host 'IDN Policies and Implementation',the second of the series of 3 webinars to introduce ICANN’s goal for a “Multilingual Internet” and its engagement of relevant stakeholders to deliv

    isoc.live/20386/

    #post #APRALO #ICANN #idn #multilingual

  28. WEBINAR MAR 26 – APRALO Policy Forum Webinar Series on A Multilingual Internet #2: IDN Policies and Implementation

    REGISTER | ADD TO CALENDAR | PERMALINK

    On Thursday 26 March 2026, at 06:00-07:15 UTC, the APRALO Policy Forum will host 'IDN Policies and Implementation',the second of the series of 3 webinars to introduce ICANN’s goal for a “Multilingual Internet” and its engagement of relevant stakeholders to deliv

    isoc.live/20386/

    #post #APRALO #ICANN #idn #multilingual

  29. WEBINAR MAR 26 – APRALO Policy Forum Webinar Series on A Multilingual Internet #2: IDN Policies and Implementation

    REGISTER | ADD TO CALENDAR | PERMALINK

    On Thursday 26 March 2026, at 06:00-07:15 UTC, the APRALO Policy Forum will host 'IDN Policies and Implementation',the second of the series of 3 webinars to introduce ICANN’s goal for a “Multilingual Internet” and its engagement of relevant stakeholders to deliv

    isoc.live/20386/

    #post #APRALO #ICANN #idn #multilingual

  30. WEBINAR MAR 26 – APRALO Policy Forum Webinar Series on A Multilingual Internet #2: IDN Policies and Implementation

    REGISTER | ADD TO CALENDAR | PERMALINK

    On Thursday 26 March 2026, at 06:00-07:15 UTC, the APRALO Policy Forum will host 'IDN Policies and Implementation',the second of the series of 3 webinars to introduce ICANN’s goal for a “Multilingual Internet” and its engagement of relevant stakeholders to deliv

    isoc.live/20386/

    #post #APRALO #ICANN #idn #multilingual

  31. WEBINAR MAR 26 – APRALO Policy Forum Webinar Series on A Multilingual Internet #2: IDN Policies and Implementation

    REGISTER | ADD TO CALENDAR | PERMALINK

    On Thursday 26 March 2026, at 06:00-07:15 UTC, the APRALO Policy Forum will host 'IDN Policies and Implementation',the second of the series of 3 webinars to introduce ICANN’s goal for a “Multilingual Internet” and its engagement of relevant stakeholders to deliv

    isoc.live/20386/

    #post #APRALO #ICANN #idn #multilingual

  32. FEB 26 2026 – APRALO Policy Forum – Multilingual Domain Names

    VIDEO | AUDIO | RECAP |  ARCHIVE | PERMALINK

    On 26 February 2026 the APRALO Policy Forum hosted 'Multilingual Domain Names', ,the first of the series of 3 webinars to introduce ICANN’s goal for a “Multilingual Internet” and its engagement of relevant stakeholders to deliver this goal. Pitinan Kooarmornpatana provided an introduction to Internationalized Doma

    isoc.live/20262/

    #post #2026 #APRALO #ICANN #idn

  33. FEB 26 2026 – APRALO Policy Forum – Multilingual Domain Names

    VIDEO | AUDIO | RECAP |  ARCHIVE | PERMALINK

    On 26 February 2026 the APRALO Policy Forum hosted 'Multilingual Domain Names', ,the first of the series of 3 webinars to introduce ICANN’s goal for a “Multilingual Internet” and its engagement of relevant stakeholders to deliver this goal. Pitinan Kooarmornpatana provided an introduction to Internationalized Doma

    isoc.live/20262/

    #post #2026 #APRALO #ICANN #idn

  34. FEB 26 2026 – APRALO Policy Forum – Multilingual Domain Names

    VIDEO | AUDIO | RECAP |  ARCHIVE | PERMALINK

    On 26 February 2026 the APRALO Policy Forum hosted 'Multilingual Domain Names', ,the first of the series of 3 webinars to introduce ICANN’s goal for a “Multilingual Internet” and its engagement of relevant stakeholders to deliver this goal. Pitinan Kooarmornpatana provided an introduction to Internationalized Doma

    isoc.live/20262/

    #post #2026 #APRALO #ICANN #idn

  35. FEB 26 2026 – APRALO Policy Forum – Multilingual Domain Names

    VIDEO | AUDIO | RECAP |  ARCHIVE | PERMALINK

    On 26 February 2026 the APRALO Policy Forum hosted 'Multilingual Domain Names', ,the first of the series of 3 webinars to introduce ICANN’s goal for a “Multilingual Internet” and its engagement of relevant stakeholders to deliver this goal. Pitinan Kooarmornpatana provided an introduction to Internationalized Doma

    isoc.live/20262/

    #post #2026 #APRALO #ICANN #idn

  36. FEB 26 2026 – APRALO Policy Forum – Multilingual Domain Names

    VIDEO | AUDIO | RECAP |  ARCHIVE | PERMALINK

    On 26 February 2026 the APRALO Policy Forum hosted 'Multilingual Domain Names', ,the first of the series of 3 webinars to introduce ICANN’s goal for a “Multilingual Internet” and its engagement of relevant stakeholders to deliver this goal. Pitinan Kooarmornpatana provided an introduction to Internationalized Doma

    isoc.live/20262/

    #post #2026 #APRALO #ICANN #idn

  37. > […] In their encoded form, IDNs [Internationalized Domain Names] are already valid hostnames, and thus valid handles. […] Applications may, optionally, parse and display IDN handles as Unicode. atproto.com/specs/handle... #punycode #handles #IDN #atproto

    Handle - AT Protocol

  38. > […] In their encoded form, IDNs [Internationalized Domain Names] are already valid hostnames, and thus valid handles. […] Applications may, optionally, parse and display IDN handles as Unicode. atproto.com/specs/handle... #punycode #handles #IDN #atproto

    Handle - AT Protocol

  39. > […] In their encoded form, IDNs [Internationalized Domain Names] are already valid hostnames, and thus valid handles. […] Applications may, optionally, parse and display IDN handles as Unicode. atproto.com/specs/handle... #punycode #handles #IDN #atproto

    Handle - AT Protocol

  40. > […] In their encoded form, IDNs [Internationalized Domain Names] are already valid hostnames, and thus valid handles. […] Applications may, optionally, parse and display IDN handles as Unicode. atproto.com/specs/handle... #punycode #handles #IDN #atproto

    Handle - AT Protocol

  41. > […] In their encoded form, IDNs [Internationalized Domain Names] are already valid hostnames, and thus valid handles. […] Applications may, optionally, parse and display IDN handles as Unicode. atproto.com/specs/handle... #punycode #handles #IDN #atproto

    Handle - AT Protocol

  42. Puisque je suis occupé à transférer beaucoup de #nomDeDomaine vers un autre Bureau d'Enregistrement (BE), c'est l'occasion de se demander « et si c'est un nom de domaine internationalisé, que se passe-t-il ? ».

    bortzmeyer.org/transfert-idn.h

    #IDN

  43. Puisque je suis occupé à transférer beaucoup de #nomDeDomaine vers un autre Bureau d'Enregistrement (BE), c'est l'occasion de se demander « et si c'est un nom de domaine internationalisé, que se passe-t-il ? ».

    bortzmeyer.org/transfert-idn.h

    #IDN

  44. Puisque je suis occupé à transférer beaucoup de #nomDeDomaine vers un autre Bureau d'Enregistrement (BE), c'est l'occasion de se demander « et si c'est un nom de domaine internationalisé, que se passe-t-il ? ».

    bortzmeyer.org/transfert-idn.h

    #IDN

  45. Puisque je suis occupé à transférer beaucoup de #nomDeDomaine vers un autre Bureau d'Enregistrement (BE), c'est l'occasion de se demander « et si c'est un nom de domaine internationalisé, que se passe-t-il ? ».

    bortzmeyer.org/transfert-idn.h

    #IDN