Gregory's Server
@polotek ... and, if "block bluesky" is *already possible, at an individual level, creating this special featureset for bluesky seems a waste 🤔
A) features need to be mirrored/accomodated in 3rd party apps, and also maintained. Only features that add real value are worth this (mostly volunteer) effort.
B) It seems to creates a sub-class of fedizens with special treatment -- unnecessarily, since a person or an instance can already block. This seems contra to the feel of fedi as it is today.
@polotek ... hmm. I'm reading the thread below. I didn't realise that this "bridge" to bluesky seems to operate differently. If I cannot block the bluesky instance easily*, it definitely needs to be opt-in from the start.
- and even if I can block it, fedi needs to ensure all users are aware in advance so they can block proactively.
So many are hoping fedi will be a safer place than the commercial platforms. Forced bluesky integration threatens that, imo.
https://masto.es/@berniethewordsmith/111924294575286286
@polotek ... hmm. I'm reading the thread below. I didn't realise that this "bridge" to bluesky seems to operate differently. If I cannot block the bluesky instance easily*, it definitely needs to be opt-in from the start.
- and even if I can block it, fedi needs to ensure all users are aware in advance so they can block proactively.