bluesky-overhaul VS list

Bluesky Social

bluesky is attempting it. We'll see how it goes.

It helps, but no. Go to https://bsky.app/ and click the link to join the wait list. Some people got in within a few days, some it took months.

And fresh out the door, now also bsky.app!

Bluesky Social if you know someone with an invite. https://bsky.app/

Sign up for beta at https://bsky.app/. 🌐💬💙

For those not getting the context(like me), this seems to be about the Bluesky Social(https://bsky.app/), a twitter alternative.

>Jay Graber currently serves as the company's CEO, while co-founder Jack Dorsey sits on its board of directors.

perfect use case for the public suffix list (https://github.com/publicsuffix/list)

I just made up `blogger.com` as an example. I probably could have picked a better one. `blogspot.com` & its many TLD variations are on the list.

It looks like the repo where the list is maintained [1] is pretty active. YMMV, I'm not a maintainer or anything..

[1] https://github.com/publicsuffix/list

There's the Public Suffix List https://publicsuffix.org/ but it's limited to domain names, so your github.com/rails example isn't covered. I'm pretty sure HN simply has a manually coded list of URL patterns for popular domains.

Browsers use the public suffix list to determine cookie scope. You can even get your own domains added to it.

https://publicsuffix.org/

Are you sure? Looking at their website[1] I see:

> Highlight the most important part of a domain name in the user interface

Which is my suggestion above.

> If you are using it for something else, you are encouraged to tell us, because it helps us to assess the potential impact of changes

Which sounds cautiously supportive of additional use cases.

[1] https://publicsuffix.org/

Sounds like Bluesky screwed up by not implementing the https://publicsuffix.org/ list

Furthermore, what constitutes a "Site" will also change henceforth. You can only add a primary domain (such as example.com) and the subdomains which are listed on the public suffix list (such as github.io, blogspot.com, etc.). Thus, your own subdomains (such as xyz.example.com or www.example.com) won't be allowed in Adsense.

> In fact I think Firefox would have to implement a similar approach if it were popular enough

They implement an omnibox that works well. Why would they need to do this if they were more popular? I suppose they use the domain suffix list for this. It's probably not bulletproof, but it works well enough and doesn't hammer the root DNS servers.

https://publicsuffix.org/