3 ms·
Fixed article title: Here is a topic that will impact you for 20 seconds until you google the problem and switch your browser to developer mode here are some wo
by batoure 13y ago
Fixed article title: Here is a topic that will impact you for 20 seconds until you google the problem and switch your browser to developer mode here are some words that will draw you in; Google!! Chrome!! Doom!!
- eterm 13y agoDon't be an ass, defaults matter.
- ehutch79 13y agothey do, but this is a good one. If you don't know how to switch to developer mode, you probably should not be running random extensions.
- eterm 13y agoWhat about extensions that I've had installed for a long time, installed from the webstore but have since been removed or updated to versions I don't want? It's not about not knowing how to switch to developer mode, it's about the fact that everywhere is putting up higher and higher walled gardens. Sure, it makes sense for most people, but it's not the direction I like to see the internet go in.
- andybak 13y agoThen switch on developer mode?
- maxerickson 13y agoIf local extension adoption is already low, the safer default is probably the better choice.
- batoure 13y agoYou are over assuming the point of the comment. I find article titles to be incredibly misleading at times and it is frustrating and this was as good an opportunity as any to vent. I believe that segmenting extensions in this way is excellent with the primary added element of stopping installers from adding something to your browser in the first place that you may not want. I feel like "Google encapsulating extensions to protect entry level users" would have been a much more honest title for this article instead it uses words like "block" to make it feel like something is being taken away when really this is probably how it should have been setup in the first place.