I'm not sure that's the best way to go either if the train of thought is: "this new feature breaks a lot of other clients, oh well, let's just make it opt-in, then it's fine."
Discussion
I agree with you. I stil think it has value in beta/test flight for users who understand that they are testing, quite a lot of us here now. But, should never happen with stuff the « common » pleb uses. The reason I mentioned opt in was because of how OnlyZap was rolled out, which caused discussion, but was really only an option for people running the builds from TestFlight.
I don’t like what I am seeing with passive aggressive notes posted by devs. Ego has no room in here. Then, the technical aspects are well past my pay grade…
True, onlyzaps was a perfect opt-in feature. Yeah, I guess all disruptive features like that should be opt-in. And I mean disruptive in the sense that it breaks the patterns of legacy social media.