This is why developer awareness is a cornerstone of UA
I was coding together with ChatGPT 4o today. *It suggested me the following (in Lua)*: -- Extract the TLD extension (e.g., 'com' from 'example.com') local tldExtension = tldName:match("%.([a-zA-Z0-9]+)$") *To which I replied*: "This is not IDN-compliant." *To which ChatGPT replied*: "You're absolutely right! The pattern |%.([a-zA-Z0-9]+)$| is not IDN-compliant because it does not account for Unicode characters in internationalized domain names (IDNs)." And ChatGPT proceeded to suggest a list of several more UA-Ready approaches. *WHAT I TOOK AWAY FROM THIS*: We need to continue making as many developers as possible aware that relying on these old RegEx is a bad idea. That way, even when LLMs insert the RegEx into the code, all it takes is one warning for the developer to be pointed in the right direction... but they need to know that this is a problem in the first place! Best, -- Mark W. Datysgeld Director at Governance Primer [governanceprimer.com <https://governanceprimer.com>] Project Lead Developer at ICANNWiki [icannwiki.org <https://icannwiki.org/>]
Thanks for sharing this! It highlights why Universal Acceptance (UA) awareness is crucial in the developer community. Many still rely on outdated regex patterns that don’t support IDNs and EAI, and as you've pointed out, even AI-generated code can reinforce these issues if developers aren’t aware. Through my ongoing training efforts in UA, I’ve seen firsthand how essential it is to equip developers with the right knowledge and tools to build truly inclusive and UA-ready applications. Conversations like this help push the movement forward—let’s keep raising awareness! Mutegeki Cliff Agaba Digital Adoption Consultant Internet Society MidCareer Fellow, Member Internet Society, AFRALO, ICANN, UASG and IGF - WGWSP +256 701 800 679 +256 776 800 679 www.mutegekicliff.com [image: facebook icon] <http://www.facebook.com/mutegekicliffagaba> [image: linkedin icon] <https://www.linkedin.com/in/mutegekicliff/> [image: instagram icon] <http://www.instagram.com/mutegekicliff> On Sat, 8 Feb 2025 at 03:59, Mark W. Datysgeld via UA-discuss < ua-discuss@icann.org> wrote:
I was coding together with ChatGPT 4o today. *It suggested me the following (in Lua)*:
-- Extract the TLD extension (e.g., 'com' from 'example.com')
local tldExtension = tldName:match("%.([a-zA-Z0-9]+)$")
*To which I replied*: "This is not IDN-compliant."
*To which ChatGPT replied*: "You're absolutely right! The pattern %.([a-zA-Z0-9]+)$ is not IDN-compliant because it does not account for Unicode characters in internationalized domain names (IDNs)."
And ChatGPT proceeded to suggest a list of several more UA-Ready approaches.
*WHAT I TOOK AWAY FROM THIS*: We need to continue making as many developers as possible aware that relying on these old RegEx is a bad idea. That way, even when LLMs insert the RegEx into the code, all it takes is one warning for the developer to be pointed in the right direction... but they need to know that this is a problem in the first place!
Best, -- Mark W. Datysgeld Director at Governance Primer [governanceprimer.com] Project Lead Developer at ICANNWiki [icannwiki.org] _______________________________________________ UA-discuss mailing list -- ua-discuss@icann.org To unsubscribe send an email to ua-discuss-leave@icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
participants (2)
-
Mark W. Datysgeld -
Mutegeki Cliff