Dear collegues,
in a conversation with Ben and Peter from Threads.net about a federation issue, they forwarded me precisely to this post in case maybe other developers have encountered similar issues and can suggest a path forward.
When developing #Seppo and looking at federating with their service, I found sending a follow request from the seppo.social/demo server sports an ‘Accepted’, while from dev.seppo.social/demo it doesn’t.
The latter makes threads.net return a “500 Internal Server Error”.
Among some commonplace lecturing about signing banalities, Peter says https://dev.seppo.social/2024-03-19/ being in an intranet is not publicly visible and recommends I should go debug the “500 Internal Server Error” from threads.net myself.
My question now is twofold:
- have you encountered similar issues and can you suggest a path forward?
- is @demo@dev.seppo.social and https://dev.seppo.social/2024-03-19/activitypub/actor.jsa#main-key visible for you?
Thanks for your cooperation, let’s put federation into the fediverse!