4 ms·

Absurdly fascinating. I should probably stop reloading the site now! Also is there a reason why on HN this domain just shows itself as "pages.dev"? That's the

Absurdly fascinating. I should probably stop reloading the site now! Also is there a reason why on HN this domain just shows itself as "pages.dev"? That's the root of Cloudflare Pages, so probably best to also show the subdomain for it like HN does for github.io

8organicbits 3y ago
I wonder if its an out of date public suffix list? Thats how I'd decide when to show a subdomain. pages.dev was added a few years back: https://github.com/publicsuffix/list/pull/1093 https://github.com/publicsuffix/list/pull/1093
- tialaramex 3y ago
  The people responsible for the PSL existing would like everybody to stop inventing more uses for it. That is, this is clearly a terrible idea but it is better than nothing, so here it is, but please invent something that's not a terrible idea.
  - 8organicbits 3y ago
    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/ https://publicsuffix.org/
    - tialaramex 3y ago
      Ryan Sleevi has written about this before on Hacker News and here's his list https://github.com/sleevi/psl-problems https://github.com/sleevi/psl-problems It's definitely possible that Ryan would consider using this for HN a reasonable choice, because it's mostly cosmetic, but in general you should just not add more dependencies.
      - 8organicbits 3y ago
        Thanks, that's an interesting read. It feels pessimistic to me (understandable given all the problems) and I'm not sure it's really offering viable alternatives. For cosmetics the PSL feels like a close enough solution, and it's available today. At the very least, it looks like a good way to bootstrap a list used to decide on cosmetic styling, with manual amendments when PSL has gaps or unneeded entries Cross-thread it looks like dang is building such a list, just without the initial PSL bootstrap to get it started. I wonder if there's anything on the PSL we wouldn't want on the HN list?
dang 3y ago
We have to specifically mark a domain for sharding like that. I've done so for pages.dev now. Thanks!

8organicbits 3y ago

I wonder if its an out of date public suffix list? Thats how I'd decide when to show a subdomain. pages.dev was added a few years back: https://github.com/publicsuffix/list/pull/1093 https://github.com/publicsuffix/list/pull/1093

tialaramex 3y ago
The people responsible for the PSL existing would like everybody to stop inventing more uses for it. That is, this is clearly a terrible idea but it is better than nothing, so here it is, but please invent something that's not a terrible idea.
- 8organicbits 3y ago
  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/ https://publicsuffix.org/
  - tialaramex 3y ago
    Ryan Sleevi has written about this before on Hacker News and here's his list https://github.com/sleevi/psl-problems https://github.com/sleevi/psl-problems It's definitely possible that Ryan would consider using this for HN a reasonable choice, because it's mostly cosmetic, but in general you should just not add more dependencies.
    - 8organicbits 3y ago
      Thanks, that's an interesting read. It feels pessimistic to me (understandable given all the problems) and I'm not sure it's really offering viable alternatives. For cosmetics the PSL feels like a close enough solution, and it's available today. At the very least, it looks like a good way to bootstrap a list used to decide on cosmetic styling, with manual amendments when PSL has gaps or unneeded entries Cross-thread it looks like dang is building such a list, just without the initial PSL bootstrap to get it started. I wonder if there's anything on the PSL we wouldn't want on the HN list?

dang 3y ago

We have to specifically mark a domain for sharding like that. I've done so for pages.dev now. Thanks!