Conversation

Notices

1. Embed this notice
   FinchHaven (finchhaven@sfba.social)'s status on Thursday, 21-Dec-2023 22:49:04 JST FinchHaven

   in reply to

   • Tokyo Outsider (337ppm)
   • misfit loser zealot patatas

   @smallpatatas @tokyo_0

   And yet, almost as I posted that, this appears on Github:

   "Enable authorized fetch for individual users who block remote domains #28457"

   Here: https://github.com/mastodon/mastodon/pull/28457

   So, enable AUTHORIZED_FETCH on a user-by-user basis?

   ClearlyClaire is cool people

   Be interesting to watch how far this gets

   • Embed this notice
     FinchHaven (finchhaven@sfba.social)'s status on Thursday, 21-Dec-2023 22:49:05 JST FinchHaven

     • Tokyo Outsider (337ppm)
     • misfit loser zealot patatas

     cc @smallpatatas

     "@Gargron:

     Bit of a technical question here - maybe you misspoke, but when you say around 25:00 that if you block threads.net at the user level, that your posts won't be delivered there, is that strictly true, if your server admin hasn't enabled authorized fetch?"

     cc @tokyo_0:

     "When you block an instance, your posts will no longer be "delivered" but they may be "retrieved", says Gargron."

     Gargron:

     "There is delivery and there is retrieval. Delivery is real-time distribution, the other is on-demand retrieval of public resources ... but retrieval of public resources cannot be prevented unless authorized fetch mode is enabled, which comes with certain drawbacks"

     In which Gargron lets the cat out of the semantics bag

     He has no intention of enabling Authorized_fetch on Mastodon dot Social

     So "retrieval of public resources" will not "be prevented" on Mas dot Soc

     "certain drawbacks" is a smokescreen for an instance with the processing horsepower of Mas dot Soc

     IMO only, of course

     Tokyo Outsider (337ppm) repeated this.