Looks like there are some unexpected knock-on effects from changes to how Chrome 69 handles URLs: https://bugs.chromium.org/p/chromium/issues/detail?id=881410
Another interesting, clearly wrong behaviour: the “m.” prefix is stripped along with “www.” There’s a weaker consensus that “http://m.example.com” is the same thing as “http://example.com”, and obtaining that subdomain on a given site is much easier.
For example, http://m.tumblr.com is a user’s blog. It’s NOT the mobile version of http://tumblr.com. But Chrome displays “http://m.tumblr.com” as “http://tumblr.com”, which could allow that blog’s owner to impersonate the main site.
OK, I think I know why this is now. Jessica pointed out that the main m. domain she goes to is Wikipedia, which is http://en.m.wikipedia.org . Chrome probably intended to strip m. in that case, and overzealously transforms the domain.
Personally, to me, this indicates why this is a problem!! If you’re starting to strip out domains in the middle of a chain you’re setting the stage for Bad Things to happen.
@oolongstains In case you haven't seen it: Google Wants to Kill the URL: https://www.extremetech.com/computing/276454-google-wants-to-kill-the-url
@oolongstains Yeah this strikes me as an all around Bad Idea. I can appreciate the good intentions behind it but at the end of the daya web browser disguising some URLs as other URLs is always going to end poorly.
Just yesterday I tried to send someone a link from the Best Buy site I saw on my phone. I stripped out the "m." and it 404'd. I put it back and it gave me the full desktop site.
The internet isn't as predictable as we'd like to think.
@oolongstains somebody on lobsters pointed out that the owner of www.com could then impersonate any dotcom, which is brutal
ｃｙｂｒｅｓｐａｃｅ: the social hub of the information superhighway
jack in to the mastodon fediverse today and surf the dataflow through our cybrepunk, slightly glitchy web portal