6 ms·
The problem is we've all seen this pattern before. Push the disabled by default, opt-in only version. Face only small backlash because it's opt-in. Then in a l
by greenhexagon 3y ago
The problem is we've all seen this pattern before.
Push the disabled by default, opt-in only version. Face only small backlash because it's opt-in. Then in a later update, switch it to on by default but with an easy opt-out. Then make the opt-out harder or disable other functionality unless users opt-in.
This general pattern happens for all sorts of privacy-invading data collection, advertisements, etc. Companies release a good product, then the enshittification slowly happens over multiple updates, each of which is only a small enough step to not cause too much outrage, until the end product is completely user-hostile.
- djur 3y agoWhen have we seen that pattern before?
- kayodelycaon 3y agoFacebook and Microsoft Windows come to mind. Also, companies making opt-in features silently into opt-out ones.
- MikusR 3y agoFeatures that require quite sizeable server resources?
- dixie_land 3y agoMicrosoft Edge comes to mind
- johnnyanmac 3y agoAmazon Prime and any other service that went from "free with ads" and "paid ad-free" to adding a "paid with ads" and "pay even more to remove the ads you used to have removed". This includes Windows as a whole. It's almost incredible how many different settings you have to dig into to get most of them out.