It’s much more a Piefed.social problem than a Piefed (all instances) problem.
I agree that in the immediate sense you leaving is related to this change having been implemented on the exact instance that you are using, but overall the outcry on this matter will be much more expansive as a result of the change to the code, rather than just the flagship instance.
That change was implemented at the software level, not as fully mandatory as anything hard-coded, but still as an opt-out rather than opt-in feature. To opt out of something you have to know that it is there, know what it does, know what the different values mean, and know how to disable it (you cannot simply “turn off” this anti-feature, though you can set the environmental variable to a value that effectively equates to that) - in short, forcing every single instance owner to expend TIME and ENERGY and the all-important & valuable ATTENTION to specifically work counter to this offering.
Maybe some instance admins pour through every line of code and do that whole procedure anyway - for all its reputed faults this seems to be what Lemmy.World does. But it’s a LOT to have to stay on top of.
So in the long run, this is going to affect the entire Threadiverse/Fediverse, well beyond a single instance, flagship or no.
I agree that in the immediate sense you leaving is related to this change having been implemented on the exact instance that you are using, but overall the outcry on this matter will be much more expansive as a result of the change to the code, rather than just the flagship instance.
That change was implemented at the software level, not as fully mandatory as anything hard-coded, but still as an opt-out rather than opt-in feature. To opt out of something you have to know that it is there, know what it does, know what the different values mean, and know how to disable it (you cannot simply “turn off” this anti-feature, though you can set the environmental variable to a value that effectively equates to that) - in short, forcing every single instance owner to expend TIME and ENERGY and the all-important & valuable ATTENTION to specifically work counter to this offering.
Maybe some instance admins pour through every line of code and do that whole procedure anyway - for all its reputed faults this seems to be what Lemmy.World does. But it’s a LOT to have to stay on top of.
So in the long run, this is going to affect the entire Threadiverse/Fediverse, well beyond a single instance, flagship or no.