Conversation

Notices

1. Eugen Rochko (gargron@mastodon.social)'s status on Thursday, 21-Dec-2023 16:24:30 JST Eugen Rochko

   • Mike McCue
   • small patatas #DefederateMeta

   @smallpatatas @mike There is delivery and there is retrieval. Delivery is real-time distribution, the other is on-demand retrieval of public resources. The behaviour of user-level and server-level domain blocks is identical on both axes, but retrieval of public resources cannot be prevented unless authorized fetch mode is enabled, which comes with certain drawbacks.

   • Eugen Rochko (gargron@mastodon.social)'s status on Thursday, 21-Dec-2023 16:27:01 JST Eugen Rochko

     in reply to

     • Mike McCue
     • small patatas #DefederateMeta

     @smallpatatas @mike Ultimately I would not use the words "leak" when talking about data that is being broadcast to the public web. A "leak-proof" Mastodon server would have to go beyond authorized fetch mode, and be effectively unusable by logged-out visitors. On the user level, the most effective way to control where your posts go is to post followers-only.

   • Virtue signal 💉💉💉🇺🇸 🇺🇦 (tasket@mastodon.social)'s status on Friday, 22-Dec-2023 14:44:57 JST Virtue signal 💉💉💉🇺🇸 🇺🇦

     in reply to

     • Mike McCue
     • small patatas #DefederateMeta

     @Gargron @smallpatatas @mike Exposure to a highly exploitative corporation – and by that, I mean all of it including the harassment and the fallout from their automated moderation – should NOT be opt-out.