4 ms·
Excellent. Sites shouldn't know what user agent we're using anyway. Pretty much the only thing they use this for is to lock us out when we use "unsupported" bro
by matheusmoreira 3y ago
Excellent. Sites shouldn't know what user agent we're using anyway. Pretty much the only thing they use this for is to lock us out when we use "unsupported" browsers. The less information they get, the better. Hopefully they'll get rid of referrer too and weaken fingerprinting methods.
I have no doubt Google has self-serving motivations here but the result is still a win for us. I wish Firefox had enough leverage to force decisions like this down people's throats whether they like it or not but it just ain't so. Reality is imperfect so I'll take what I can get.
- SoftTalker 3y agoThere are plugins for Firefox that can make the user agent string anything you want.
- matheusmoreira 3y agoIt doesn't matter. Actually those plugins are straight up counterproductive. The best user agent is the one that offers them the fewest identifying bits. In other words, the user agent of the most popular version of Chrome. The ability to set it to "anything we want" is actually a trap. What we really want is for everyone to use the exact same user agent so they can't tell us apart. If everyone has the same user agent, it's nothing but a waste of bandwidth and it should be removed. Google is actually achieving our objective here.
- eru 3y agoFirefox has plugins to set your user agent to Chrome.
- matheusmoreira 3y agoPointless. Firefox should just pretend to be Chrome by default without the user having to install plugins or even do literally anything. As should all the other browsers. Anything that leaks out the fact it's not Chrome should be considered a bug and fixed.
- SoftTalker 3y agoWell yeah, they have a pre-configured set of choices, e.g. "Chrome on Windows" but you can do something custom too, if you want.
- sanderjd 3y agoYeah I tend to agree here... It really seems like none of the server's business what agent I'm using.
- matheusmoreira 3y agoYup. It's none of their business. They can't discriminate against us if they don't know anything about us.
- Fordec 3y agoCan't trust you either. Are you a bot? Well it's good to assume you are by default, since it's the majority of internet traffic anyway. And for your privacy, you're not exactly forthcoming with data to now prove otherwise. So sorry, until you pay with a unique individual bank account to prove identity, you can't post on future social media sites. You are a bot after all.
- matheusmoreira 3y agoEven if I was a bot, what of it? Your site should serve bots just as well as it serves humans. Only people who care about that are those who want to monetize our eyeballs by selling our attention to the highest bidder. If it's costing you money, have your HTTP server return 402 Payment Required instead of the free page. That's how it should be.
- Fordec 3y agoThere are vast reasons to prevent brigading, false information, information manipulation and any other number of malicious inputs that otherwise in a forum for people require trust to maintain community quality. Even for free reasons, especially say nice interest groups like one I used to be on for small satellites that got destroyed by uncontrolled bot spam. I do not agree that every piece of the internet "should be" behind a paywall because bad actors exist. That world is the literal death of the "open" internet, putting everything behind a paywall.
- technion 3y agoI've always advocated for feature detection. If you test for typeof Object.assign !== 'function' you can be sure you have a reasonably recent browser. If you want fetch, test for window.fetch. This sort of thing always feels like it's going against the grain, with someone always asking "why wouldn't you do this properly. You know, build an allow list of user agents and match against them". I fully support people being forced into detecting the features they want and doing away with this nonsense,
- matheusmoreira 3y agoI don't think web developers should be able to detect stuff like that either. Their ability to detect stuff provides identifying bits for fingerprinting. As far as I'm concerned, all the browsers should normalize the return values of those typeofs and all related functions so that Javascript can figure out exactly zero bits of information about the environment it's running on. Just like browsers will lie to Javascript when it tries to figure out your browsing history by checking the color of links. The web platform gave web developers way too much freedom and they're abusing it. God giveth and god taketh away.
- raincole 3y ago> Feature detection is too much power for developers - People on HN.
- matheusmoreira 3y agoYes, it is too much power for them. Power which they abuse by fingerprinting us. Browser vendors agree with me: they reduced the power of developers by lying to Javascript when they tried to check link styles. Do you think otherwise?
- raincole 3y agoA. Test for window.fetch. B. Check if a link is visited. Whether these two even remotely fall into the same category is left as an exercise for readers.