Set up a new zap instance last night on a URL that I don’t believe I used in previous installs.. and STILL mastodon isn’t federating with it.. all other platforms appear to be..
Also, the zap codeberg page doesn’t have issues enabled… Eh?
Set up a new zap instance last night on a URL that I don’t believe I used in previous installs.. and STILL mastodon isn’t federating with it.. all other platforms appear to be..
Also, the zap codeberg page doesn’t have issues enabled… Eh?
Alternatively, if you do not have a webmentions enabled website then you can leave a message using the comment parade form below.
Please copy the following and paste into the URL field below: https://jk.nipponalba.scot/note/5f97d27b/
All going well, interactions will take a few minutes to appear, possibly longer due to .. gremlins.
Weirdly mastodon accounts are appearing in the directory.. if someone from another platform shares or interacts with a mastodon toot then it appears.. but requests to follow mastodon users appear to be failing and being perpetually re-requested.
so OLD mastodon instances will federate but not up-to-date ones..
@jk I seeing something about Gruppe Groups not working for newer Mastodon instances if they had a “security” feature enabled. Something about more in depth signature checking? So… sounds plausible to me!
@kensanata yeah, it's tricky to troubleshoot at this end but I've now followed accounts on 5 or 6 different mastodon instances.. v2.1.3 works, octodon.social on v3.2.0 works but another on that version doesn't.. none of the v3.2.1 work.. so I guess, as you say it's potentially an optional "security" feature
@trumpet hello,
as per below, in one of your recent instance updates did you enable (or possibly auto-enabled) a new "security" feature? If you don't mind me asking.
Just trying to understand a curious federation issue happening with up-to-date mastodon instances.. and whether there is something I can do as an admin or the application dev needs to look at.
@kensanata