Need help implementing ActivityPub - getting inconsistent results across platforms

[madiator2011@lm.madiator.cloud]

My friend is working on adding ActivityPub support to his blog platform (BDServer) so people can follow/comment from Mastodon, Lemmy, etc.

Current status: Lemmy and Misskey can find and follow his account (@blenderdumbass@blenderdumbass.org), but Mastodon can't find it at all, even though he sees proper ActivityPub requests hitting his server.

The technical details are pretty gnarly - RSA signature verification, HTTP header recreation, multi-threading issues. He wrote up the full journey here: Please Help Me With Activity Pub

If anyone has ActivityPub experience or wants to take a look at the code (Python), we have a Matrix room for BDServer development. Any insights on why different platforms behave differently would be super helpful.

You're invited to talk on Matrix

You're invited to talk on Matrix

(matrix.to)

Source code: ActivityPub.py

[irelephant@lemmy.dbzer0.com]

Did something change since this was posted?
I can look it up properly on mastodon.
You have to be signed in to fetch accounts on mastodon, is that the problem?

Are you using any framework to build the site? There's a few libraries for activitypub.
These links could be helpful: https://codeberg.org/fediverse/delightful-activitypub-development/

[flamingos@feddit.uk]

I'm not the most knowledgeable about Mastodon's APub implementation, but having a look at the Actor of that profile, it might be because it's invalid JSON-LD. Now, Mastodon doesn't actually do proper JSON-LD checks, you can follow PieFed profiles from Mastodon and they don't produce proper JSON-LD, but they do include "https://w3id.org/security/v1" in their @context, and doing a code search of Mastodon's source code does show some checks for if that's included.

Lemmy's I am familiar with and irrc it doesn't even check if @context is present.

[blenderdumbass@lm.madiator.cloud]

Seems like somebody mentioned the account on the fediverse that started a chain reaction of various instances requesting a bunch of stuff. Which made it to Mastodon.social too. It still doesn't work though.

The server is written in python and the idea is to make it deploy-able without needing to install anything extra. So I'm trying to implement my own activity pub.

[madiator2011@lm.madiator.cloud]

I would say for now the most issue is about acually pulling posts.

[irelephant@lemmy.dbzer0.com]

Running curl https://blenderdumbass.org/activitypub/account/blenderdumbass -H "Accept: application/activity+json" twice in a row outputs some bunkerweb anti-spam stuff.

[madiator2011@lm.madiator.cloud]

Disabled bunker for now.

[rglullis@communick.news]

It's for django, but take a look into my ActivityPub Toolkit. It is designed to be compliant with ActivityPub and not with any particular implementation, so it should be easy for you to adapt to your own needs.

[rglullis@communick.news]

Maybe this kind of discussion will get more interested people on !activitypub@programming.dev .

[irelephant@lemmy.dbzer0.com]

Also: bunker blocks me 100% of the time on individual articles.

[madiator2011@lm.madiator.cloud]

Should not too I removed all blocks.

[blenderdumbass@lm.madiator.cloud]

This doesn't have any link to code. And all the other buttons say that the docs are not implemented yet.

[blenderdumbass@lm.madiator.cloud]

try spoofing a user-agent or torifying it maybe

[rglullis@communick.news]

The menu has a link to the repository.

[irelephant@lemmy.dbzer0.com]

While I'm sure that would let me see the article, mastodon probably wouldn't handle it well.

[julian@community.nodebb.org]

For what it's worth your blog does show up fine in NodeBB as well. Perhaps you are missing the @context property and so Mastodon is refusing to parse it?