Need help implementing ActivityPub - getting inconsistent results across platforms
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 (@[email protected]), 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.
https://matrix.to/#/#bdserver:tchncs.de
Source code: ActivityPub.py
https://blenderdumbass.org/articles/please_help_me_with_activity_pubOpen linkView original on lm.madiator.cloud
19 replies
Maybe this kind of discussion will get more interested people on ![email protected] .
Happy cake day! 🎂
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/
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.
For what it's worth your blog does show up fine in NodeBB as well. Perhaps you are missing the
@contextproperty and so Mastodon is refusing to parse it?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.
This doesn't have any link to code. And all the other buttons say that the docs are not implemented yet.
The menu has a link to the repository.
Running
curl https://blenderdumbass.org/activitypub/account/blenderdumbass -H "Accept: application/activity+json"twice in a row outputs some bunkerweb anti-spam stuff.Disabled bunker for now.
Also: bunker blocks me 100% of the time on individual articles.
Should not too I removed all blocks.
try spoofing a user-agent or torifying it maybe
While I'm sure that would let me see the article, mastodon probably wouldn't handle it well.
I would say for now the most issue is about acually pulling posts.
I'm not the most knowledgeable about Mastodon's APub implementation, but having a look at the
Actorof 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
@contextis present.I was trying something on lemmy a while ago and it required an
@context.I don't know if somethings changed, but it actually doesn't. This lines would need to be
WithContext<SharedInboxActivities>>for that to be the case, and just to make sure I tested against a local running main and was able to send activities to it without the@contextjust fine.I just took another look at it,
Comparing it to another random
note, thetoandccfields are supposed to be arrays, rather than just a string.Its also missing a
urlfield, which is supposed to link to the user-facing url of the post.cc: @[email protected]