Threads.net federation issue after Follow request

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:

Thanks for your cooperation, let’s put federation into the fediverse!

The post was flagged off-topic and I moved it into its own topic. @mro you might improve title and category to what I made them to be.

3 Likes

I recommend you should not work for Fakebooz and avoid free labor for corporations in general. If their software crashes, it’s their problem, not yours. Look elsewhere, you have a community to nurture outside of surveillance capitalism.

3 Likes