LiquidParasyte on Nostr: npub1yamt4…d2l9d npub1m0vcr…ldu9y I think you've touched on what's getting at me ...
npub1yamt4pnum78u4ludkwfttlmcltu5gsygqc8f8e62t4hcv32vvlmq0d2l9d (npub1yam…2l9d) npub1m0vcr0caxjdqex0pk5kpsqlt3emc2mcajvmlzdq0px3rm6v6wjzq8ldu9y (npub1m0v…du9y) I think you've touched on what's getting at me with their content moderation approach.
The base firehose/content stream is the raw experience users will see by default, and is the data Bluesky PBLLC will be hosting/showing/responsible for (unless the new user experience automatically suggests a moderation service, but then is that not just endorsing a third party's decisions/liabilities as your own?) Some content cannot hosted, morally or legally, in any form, which will force Bluesky to act. What will that line be for them?
Also, since third party PDSs (the ATProto equivalent of an instance) are going to be a thing, what will be their protocol for moderating/blocking those? (Stares at defederated ActivityPub instances.)
The base firehose/content stream is the raw experience users will see by default, and is the data Bluesky PBLLC will be hosting/showing/responsible for (unless the new user experience automatically suggests a moderation service, but then is that not just endorsing a third party's decisions/liabilities as your own?) Some content cannot hosted, morally or legally, in any form, which will force Bluesky to act. What will that line be for them?
Also, since third party PDSs (the ATProto equivalent of an instance) are going to be a thing, what will be their protocol for moderating/blocking those? (Stares at defederated ActivityPub instances.)