Gregory's ServerFediverse advice needed:
Does activating authorised fetch / secure mode on Mastodon cause connections with non-Mastodon platforms to break?
Are there other drawbacks of secure mode apart from the increased resources it uses?
 10 comments
 @FediThing I think I saw enabling it creates issues with Kbin interop. I forget where I read that, however.
0
0
20 Jun 2023 at 17:25 | Open on social.gabekangas.com
Yeah, that's why I am considering activating it. I don't feel comfortable having my posts on instances that I've blocked. The Meta/Facebook situation has made this more urgent. (I know they could get round this by scraping and using proxy servers, but them bothering to do so would show what kind of people run them, which in itself would be interesting.)  @FediThing @jacksonchen666 We have authorized fetch enabled on vt.social ourselves, maybe there was some weird interaction? (These posts federated fine here but I don't know why you wouldn't get mine...) @lina@vt.social @FediThing@tech.lgbt @jacksonchen666@micro.jacksonchen666.com oh so if you have authorized fetch enabled, KitsuClub (running Calckey 14.0.0-dev51) is having no issues seeing your posts  @lina no idea what's happening, explicitly putting links into search does get posts, but following users doesn't get posts... (i did get your post but that's about it) following @LunaFoxgirlVT to see if issue is account dependent or something @jacksonchen666 @FediThing Sources: - https://github.com/superseriousbusiness/gotosocial/issues/1468 - @FediThing I mean it prevents posts from being accessible to not-logged in users just trying to read a post. could be good or bad, depending on what you want @FediThing I haven't tried it out myself but my understanding is that requests that don't contain an ActivityPub signature of sorts will be blocked. Many fediverse clients will support that, not just Mastodon but it's true that you might find some exceptions, especially if they're older.  @FediThing It won't affect federation with Pleroma. Pleroma always signs its fetch with its internal.fetch actor.
|