{ "@context":[ "https://www.w3.org/ns/activitystreams", {"Hashtag":"as:Hashtag"} ], "published":"2023-08-02T09:09:18.215Z", "attributedTo":"https://social.jayvii.de/actors/jayvii", "inReplyTo":"https://toot.wales/users/jtb/statuses/110819164312854215", "to":["https://www.w3.org/ns/activitystreams#Public","https://toot.wales/users/jtb"], "cc":["https://social.jayvii.de/actors/jayvii/followers"], "content":"

@jtb I believe it does make a difference as it lowers barriers for websites and webapps to use such schemes. Of course there are already sites that block access if you disallow trackers or use adblock or which are entirely built with JS (so obviously they won't work if you turn it off entirely).

However there is no standard API or protocol (yet) that enables sites to define specific browser configurations and lock everyone else out. Be it a different browser, OS, disallowing JS, blocking trackers or certain domains, fonts, etc. It manifests those abusive practices that you just mentioned. It sets a standard for exactly that behavior. So in my opinion it does make a difference.

Granted: Neither of us knows for sure what it will turn out to be, but with Google some healthy scepticisms and critique historically has always been warranted.

firefox on android is an awkward situation indeed. There are a bunch of proprietary blobs in there, which is (one of the reasons) why f-droid lists fennec & mull instead. I am not an expert on that matter, so I don't want to dive into that too much here.

", "mediaType":"text/html", "attachment":[], "tag":[ {"type":"Mention","name":"@jtb@toot.wales","href":"https://toot.wales/users/jtb"} ], "type":"Note", "id":"https://social.jayvii.de/objects/6tHwco3-EWw" }