Post B6CqxNPfApNsPz6rZo by thepi@urusai.social
 (DIR) More posts by thepi@urusai.social
 (DIR) Post #B6CqxMgzqtegBSDBxI by whitequark@social.treehouse.systems
       0 likes, 0 repeats
       
       @arcterus c.make
       
 (DIR) Post #B6CqxMwwtaPoyvfvou by whitequark@social.treehouse.systems
       0 likes, 0 repeats
       
       @arcterus actually there's no reason you can't serve HTTP from a TLD
       
 (DIR) Post #B6CqxNPfApNsPz6rZo by thepi@urusai.social
       0 likes, 1 repeats
       
       @whitequark @arcterus I looked it up once and it turns out the reason you can't do this (in practice) is Microsoft Windows. Windows clients will always try to resolve tld to tld.internal. (or whatever your connection's DNS suffix is) first. And now it's too late to change it.On the bright side this does mean Microsoft can't ask you to go to https://microsoft.. So I'm not mad about it. That's pretty funny.