@aswath @uriel @m @mistercharlie @fediversenews Facebook isn’t what’s being federated. It’s another social network, still in development, called P92.
Top-level
@aswath @uriel @m @mistercharlie @fediversenews Facebook isn’t what’s being federated. It’s another social network, still in development, called P92. 5 comments
@tezoatlipoca @aswath @uriel @m @mistercharlie @fediversenews It’s already super easy to do this. @atomicpoet @aswath @uriel @m @mistercharlie @fediversenews As in its trivially easy to do already or it would be trivial to implement? Like an instance admin could block all PixelFed content? @tezoatlipoca @aswath @uriel @m @mistercharlie @fediversenews Certain instances immediately block Soapbox. @atomicpoet @uriel @m @mistercharlie @fediversenews Agreed. But their point is that even a fraction of their user base will be a unbearable load. |
@atomicpoet @aswath @uriel @m @mistercharlie @fediversenews Could a future extension to each 'verse platform implementation be a capability to block or filter content by originating platform? like configure a Mastadon instance to not relay content from P92 specifically; or leave that at the user preference level ("I don't want to see content from P92"). We already do that for specific instances, why not the - I don't want to say protocol - platform level? Or does that open more cans o worms?