3 ms·
That's why for that type of 'semi-white-label' thing, since the main risk is one of impersonating the platform owner (like the billing.my-thing.example) or poss
by xp84 2mo ago
That's why for that type of 'semi-white-label' thing, since the main risk is one of impersonating the platform owner (like the billing.my-thing.example) or possibly lending the credibility of "our" brand to some rando UGC, I always push for the most boring and generic second-level domain, like if it's the travel business, 'travel-systems dot us' or in edtech, mylearningplatform dot net... Then push all customers who know what they're doing into 'BYO DNS name' anyway.
I also like how sites like github use githubusercontent.com or something like that when linking to UGC assets directly, to avoid someone direct linking to something with the implication that it's coming from GitHub.
- chuckadams 2mo agoIt's mostly about not sharing a security context with github.com.
- cwillu 2mo agoYes, but github.cc or whatever would have sufficed for that; there's a reason the string they chose to register for prominent public use contains “usercontent”
- inigyou 2mo agoliterally github.io though
- notpushkin 1mo agoAnd before that one, user content was hosted on *.github.com! Wild times.
- inigyou 2mo agoThat's actually to prevent cookie stealing.
- lozenge 1mo agoYes, involving the Public Suffix List. It's quite ridiculous you need to register your domain on a list of you want to offer subdomains.