Re: [whatwg/url] Public Suffix API (#528)

At Discord we are interested in following best practices when displaying URLs to users to ensure they can understand the implications of a navigation and decide with confidence. eTLD+1 falls into these best practices, but it is not practical to ship the entire public suffix list in our web app.

Also I'm not entirely sure that an API on `URL` is exactly what we would want in this case. A separate API specifically designed for displaying URLs may be more suitable (maybe something like a URL segmenter?). Either way, eTLD+1 functionality would be great to have.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/528#issuecomment-1492215104
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/528/1492215104@github.com>