cross-posted from: https://lemmy.bestiver.se/post/1210182
Building relationships with customers through support didn’t turn out as hoped
cross-posted from: https://lemmy.bestiver.se/post/1210182
Building relationships with customers through support didn’t turn out as hoped
Telemetry exists to aid enshittification. Widely hated update that has loads of people complaining online but causes no change in usage? Keep it. Update causes dip in usage? Post generic “we hear your concerns” statement, backpedal slightly and try again in 6 months. Beloved feature is only actually utilised by 5% of your users? Get rid of it.
I mean, there is a pretty strong argument that if 95% of users don’t use a function, then it is not actually beloved and just more of a niche thing that the vast majority don’t care about.
Move it out of core and into an optional extention.
Of course if the code base respected user’s software freedom then others can maintain in your place.
Yeah sure I’m not arguing it should be culled, just that calling a feature untouched by the vast majority of users beloved is incorrect.
That 5% is 5% of the users who don’t turn the telemetry off.
And if use of that feature is strongly correlated with the type of person who also turns off telemetry…
– Frost
That would just make it 5% of a vast majority, nearing 100%, so still only a small amount of users.
I get what you’re saying, but when something is only used by the small demographic that is “power users”, it is not a beloved feature of the userbase as a whole.
So 5% of 99%. Still niche.