PSA for Akkoma instance ops: we just found out that the internal relay Works and Behaves as Expected with the allowlist. this’ll definitely help with federation and discovery
here’s how to set it up:
Allow Relay in the instance settings (or :instance, allow_relay: true in the config)https://instance.tld/relay, needs to be the “real” URL for split domain setups) in relays, you can refresh the list after a few seconds, if Followed back changes to a ✓, it’s working@adam i am ready 4 relays baby https://bubsy.org/relay #leaguemeta #relayitonme
RE: https://league.adamski2003.lol/objects/fb93cb95-39d5-43f0-925c-6a282e94acc3
@adam specifically, this will help solve the issue of tagged posts not federating to all instances. Once all akkoma instances enable the relay and add all URLs, all tagged (public) posts shared to these instances will federate to all other akkoma instances.
This only works on akkoma, for now – GTS still needs relay support.
#WLMeta #Akkoma@adam fyi, this presents a bot user that allows users to follow all posts from an instance. i recommend turning allow_relay off, for now, until we can sort that out.
@vision update: should be sorted, I got an mrf policy going, update your akkomas from the gitlab or just drop this file in the correct location and then add Pleroma.Web.ActivityPub.MRF.FollowWhitelistPolicy as a policy; I recommend setting the values as suggested (["relay"], ["relay", "relay_follower"])
if an admin is following an instance’s relay account, they’ll have to use relay_follower as the local account name (or relay if available, I guess, but I don’t recommend doing that because possible future expansion)