Conversation

Notices

1. Embed this notice
   feld (feld@bikeshed.party)'s status on Wednesday, 27-Dec-2023 05:20:26 JST feld
   Can someone with insight into Mastodon tell me if a domain is blocked by a user does the authorized_fetch return a 403 or is that only when the whole instance blocks it?
   • Embed this notice
     feld (feld@bikeshed.party)'s status on Wednesday, 27-Dec-2023 05:24:15 JST feld

     in reply to

     • Frost「:therian:｜霜の狼｜人面獣心」
     @frost ahh you're right someone opened a bug about this last week
     
     https://github.com/mastodon/mastodon/issues/28397
   • Embed this notice
     Frost「:therian:｜霜の狼｜人面獣心」 (frost@chitter.xyz)'s status on Wednesday, 27-Dec-2023 05:24:17 JST Frost「:therian:｜霜の狼｜人面獣心」

     in reply to

     @feld I'm pretty sure user "domain blocks" are actually just mutes, so they're kind of worthless. But I could be wrong and/or maybe it's changed.

   • Embed this notice
     feld (feld@bikeshed.party)'s status on Wednesday, 27-Dec-2023 05:25:53 JST feld

     in reply to

     • Frost「:therian:｜霜の狼｜人面獣心」
     @frost So the moral of the story is:
     
     If you're on Mastodon.social and they're enforcing Authorized Fetch and you think a domain block you configured for your user is going to protect your posts from being fetched you have been greatly mislead. You must get the instance operator to block the domain for everyone.