3 ms·
I would fix the order of URLs instead of http://news.ycombinator.com/item http://news.ycombinator.com/item it would be https:com/ycombninator/news/item
by asciimov 5y ago
I would fix the order of URLs instead of http://news.ycombinator.com/item http://news.ycombinator.com/item it would be https:com/ycombninator/news/item
- dane-pgp 5y agoI actually really like this idea (and once created a browser extension to at least make URLs look like that in the address bar), but I still think there is a benefit to having domain names distinguishable from paths, so it would be: https://com.ycombinator.news/item https://com.ycombinator.news/item Having just checked, I see that ycombinator.news has already been registered, so maybe the lesson is that everyone should register "palindromic" domains, like com.ycombinator.com for example.
- Y_Y 5y agoCan we just do this now anyway? Also I like that ycombinator becomes "ycombninator".
- musicale 5y agoThe hierarchical order and flat namespace is logical, but for privacy reasons you may not wish to make a DNS query on the full path. So we might want to leave it split: com.ycombinator.news/item On the other hand, you could do an incremental query perhaps and cache the path length. But I wonder about having the protocol name in there. Couldn't DNS return the ports for the supported services and then you could pick whichever one you want?