[At-Large] At-Large Digest, Vol 181, Issue 2

Shadrach Ankrah ankrah960 at gmail.com
Thu Sep 14 11:19:08 UTC 2023


Thank you Dev for sharing this post.

I am excited to know this issue and will read more on this to learn more.

On Tue, 12 Sep 2023, 3:17 pm , <at-large-request at atlarge-lists.icann.org>
wrote:

> Send At-Large mailing list submissions to
>         at-large at atlarge-lists.icann.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://atlarge-lists.icann.org/mailman/listinfo/at-large
> or, via email, send a message with subject or body 'help' to
>         at-large-request at atlarge-lists.icann.org
>
> You can reach the person managing the list at
>         at-large-owner at atlarge-lists.icann.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of At-Large digest..."
> Today's Topics:
>
>    1. DomainIncite : Is this why WhatsApp hates some TLDs but   not
>       others? (Dev Anand Teelucksingh)
>    2. Re: DomainIncite : Is this why WhatsApp hates some TLDs but
>       not others? (BF)
>    3. Re: DomainIncite : Is this why WhatsApp hates some TLDs but
>       not others? (Bill Jouris)
>
>
>
> ---------- Forwarded message ----------
> From: Dev Anand Teelucksingh <devtee at gmail.com>
> To: At-Large Worldwide <at-large at atlarge-lists.icann.org>
> Cc:
> Bcc:
> Date: Tue, 12 Sep 2023 10:42:09 -0400
> Subject: [At-Large] DomainIncite : Is this why WhatsApp hates some TLDs
> but not others?
> "*Developers of major pieces of internet software, including the world’s
> most-popular messaging app, may be relying on seriously outdated lists of
> top-level domains.*
>
> That’s the picture that seems to be emerging from one new gTLD operator’s
> quest to discover why WhatsApp doesn’t recognize its TLD, and many others
> including major dot-brands, as valid."
> ....When most social media apps detect the user has inputted a URL or
> domain name, they automatically “linkify” it so it can be easily clicked or
> tapped without the need for copy/paste.
>
> But when Rami Schwartz of new gTLD .tube discovered that .tube URLs sent
> via WhatsApp, said to have two billion users, were not being linkified,
> despite the TLD being delegated by ICANN almost eight years ago, he set out
> to find out why.
>
> Schwartz compiled a spreadsheet (.xlsx) listing which gTLDs are recognized
> by WhatsApp and which are not and discovered a rough cut-off point in
> November 2015. TLDs delegated before then are linkified, those delegated
> after were not......This means that, for example, .microsoft domains
> linkify but .amazon and .apple domains do not; .asia domains linkify but
> .africa and .arab domains do not; .london works but .abudhabi doesn’t. Even
> .verisign missed the cut-off.
>
> If WhatsApp users include a “www.” or “http://” then the app will linkify
> the domain, even if the specified TLD does not exist.
>
> .....During the course of a discussion
> <https://github.com/publicsuffix/list/issues/1807> on the web site of the
> Public Suffix List — which maintains an open-source list of all TLDs and
> the levels at which names may be registered — it was discovered that the
> problem may be deeper rooted than the WhatsApp app.
>
> It turns out a library in the Android operating system
> <https://cs.android.com/android/platform/superproject/main/+/main:frameworks/base/core/java/android/util/Patterns.java;l=114>
> contains a hard-coded list of valid TLDs which hasn’t been updated since
> November 24, 2015"
> Read full article :
>
> https://domainincite.com/29054-is-this-why-whatsapp-hates-some-tlds-but-not-others
>
>
> Regards,
>
> Dev Anand Teelucksingh
>
>
>
> ---------- Forwarded message ----------
> From: BF <betty at ipeos.com>
> To: Dev Anand Teelucksingh <devtee at gmail.com>
> Cc: At-Large Worldwide <at-large at atlarge-lists.icann.org>
> Bcc:
> Date: Tue, 12 Sep 2023 10:59:13 -0400
> Subject: Re: [At-Large] DomainIncite : Is this why WhatsApp hates some
> TLDs but  not others?
> Since 2015!
> Geez!
>
> Sent from Android device
>
> Le 12 sept. 2023 10:42, Dev Anand Teelucksingh via At-Large <
> at-large at atlarge-lists.icann.org> a écrit :
>
> "*Developers of major pieces of internet software, including the world’s
> most-popular messaging app, may be relying on seriously outdated lists of
> top-level domains.*
>
> That’s the picture that seems to be emerging from one new gTLD operator’s
> quest to discover why WhatsApp doesn’t recognize its TLD, and many others
> including major dot-brands, as valid."
> ....When most social media apps detect the user has inputted a URL or
> domain name, they automatically “linkify” it so it can be easily clicked or
> tapped without the need for copy/paste.
>
> But when Rami Schwartz of new gTLD .tube discovered that .tube URLs sent
> via WhatsApp, said to have two billion users, were not being linkified,
> despite the TLD being delegated by ICANN almost eight years ago, he set out
> to find out why.
>
> Schwartz compiled a spreadsheet (.xlsx) listing which gTLDs are recognized
> by WhatsApp and which are not and discovered a rough cut-off point in
> November 2015. TLDs delegated before then are linkified, those delegated
> after were not......This means that, for example, .microsoft domains
> linkify but .amazon and .apple domains do not; .asia domains linkify but
> .africa and .arab domains do not; .london works but .abudhabi doesn’t. Even
> .verisign missed the cut-off.
>
> If WhatsApp users include a “www.” or “http://” then the app will linkify
> the domain, even if the specified TLD does not exist.
>
> .....During the course of a discussion
> <https://github.com/publicsuffix/list/issues/1807> on the web site of the
> Public Suffix List — which maintains an open-source list of all TLDs and
> the levels at which names may be registered — it was discovered that the
> problem may be deeper rooted than the WhatsApp app.
>
> It turns out a library in the Android operating system
> <https://cs.android.com/android/platform/superproject/main/+/main:frameworks/base/core/java/android/util/Patterns.java;l=114>
> contains a hard-coded list of valid TLDs which hasn’t been updated since
> November 24, 2015"
> Read full article :
>
> https://domainincite.com/29054-is-this-why-whatsapp-hates-some-tlds-but-not-others
>
>
> Regards,
>
> Dev Anand Teelucksingh
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Bill Jouris <b_jouris at yahoo.com>
> To: ICANN At-Large List <at-large at atlarge-lists.icann.org>
> Cc:
> Bcc:
> Date: Tue, 12 Sep 2023 15:17:16 +0000 (UTC)
> Subject: Re: [At-Large] DomainIncite : Is this why WhatsApp hates some
> TLDs but  not others?
> He complains that he couldn't get ICANN interested in the problem. It
> would be interesting to know just who at ICANN he was talking to.
>
> Bill Jouris
>
>
> Sent from Yahoo Mail on Android
> <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature>
>
> On Tue, Sep 12, 2023 at 7:43 AM, Dev Anand Teelucksingh via At-Large
> <at-large at atlarge-lists.icann.org> wrote:
> "*Developers of major pieces of internet software, including the world’s
> most-popular messaging app, may be relying on seriously outdated lists of
> top-level domains.*
>
> That’s the picture that seems to be emerging from one new gTLD operator’s
> quest to discover why WhatsApp doesn’t recognize its TLD, and many others
> including major dot-brands, as valid."
> ....When most social media apps detect the user has inputted a URL or
> domain name, they automatically “linkify” it so it can be easily clicked or
> tapped without the need for copy/paste.
>
> But when Rami Schwartz of new gTLD .tube discovered that .tube URLs sent
> via WhatsApp, said to have two billion users, were not being linkified,
> despite the TLD being delegated by ICANN almost eight years ago, he set out
> to find out why.
>
> Schwartz compiled a spreadsheet (.xlsx) listing which gTLDs are recognized
> by WhatsApp and which are not and discovered a rough cut-off point in
> November 2015. TLDs delegated before then are linkified, those delegated
> after were not......This means that, for example, .microsoft domains
> linkify but .amazon and .apple domains do not; .asia domains linkify but
> .africa and .arab domains do not; .london works but .abudhabi doesn’t. Even
> .verisign missed the cut-off.
>
> If WhatsApp users include a “www.” or “http://” then the app will linkify
> the domain, even if the specified TLD does not exist.
>
> .....During the course of a discussion
> <https://github.com/publicsuffix/list/issues/1807> on the web site of the
> Public Suffix List — which maintains an open-source list of all TLDs and
> the levels at which names may be registered — it was discovered that the
> problem may be deeper rooted than the WhatsApp app.
>
> It turns out a library in the Android operating system
> <https://cs.android.com/android/platform/superproject/main/+/main:frameworks/base/core/java/android/util/Patterns.java;l=114>
> contains a hard-coded list of valid TLDs which hasn’t been updated since
> November 24, 2015"
> Read full article :
>
> https://domainincite.com/29054-is-this-why-whatsapp-hates-some-tlds-but-not-others
>
>
> Regards,
>
> Dev Anand Teelucksingh
> _______________________________________________
> At-Large mailing list
> At-Large at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/at-large
>
> At-Large Official Site: http://atlarge.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.
>
> _______________________________________________
> At-Large mailing list
> At-Large at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/at-large
> _______________________________________________
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://atlarge-lists.icann.org/pipermail/at-large/attachments/20230914/6d465c85/attachment-0001.html>


More information about the At-Large mailing list