Late night #activitypub interop hacking.
-
Late night #activitypub interop hacking. Again.
Has anyone else had trouble with the #pixelfed shared inbox?
Seems hits to /f/inbox don't send a username. Worker gives the error: "ActivityHandler: No username provided, skipping job"
Likes from self-hosted #mastodon go to the user inbox, Boosts and Comments go to the shared one.
I disable shared inbox in settings and Mastodon still sends to /f/inbox even though I've refreshed the pixelfed profile.
At least I know why it's happening now!
-
Late night #activitypub interop hacking. Again.
Has anyone else had trouble with the #pixelfed shared inbox?
Seems hits to /f/inbox don't send a username. Worker gives the error: "ActivityHandler: No username provided, skipping job"
Likes from self-hosted #mastodon go to the user inbox, Boosts and Comments go to the shared one.
I disable shared inbox in settings and Mastodon still sends to /f/inbox even though I've refreshed the pixelfed profile.
At least I know why it's happening now!
heathenstorm@mastodon.social I don't think it's wise to disable the shared inbox... I imagine it's just cached at the domain level once it is discovered (though that can differ between implementations of course.)
You mean that when you receive activities from Mastodon to Pixelfed's shared inbox, there is no username?
-
Late night #activitypub interop hacking. Again.
Has anyone else had trouble with the #pixelfed shared inbox?
Seems hits to /f/inbox don't send a username. Worker gives the error: "ActivityHandler: No username provided, skipping job"
Likes from self-hosted #mastodon go to the user inbox, Boosts and Comments go to the shared one.
I disable shared inbox in settings and Mastodon still sends to /f/inbox even though I've refreshed the pixelfed profile.
At least I know why it's happening now!
@heathenstorm mastodon is probably caching the actor and doesn't realise that it's changed on the pixelfed side.
So you likely need to dispatch for each actor on the pixelfed server an update to the actor to all servers.
-
@heathenstorm mastodon is probably caching the actor and doesn't realise that it's changed on the pixelfed side.
So you likely need to dispatch for each actor on the pixelfed server an update to the actor to all servers.
@heathenstorm that is, configuration changes like that only change what pixelfed serves / pushes from that point in time onwards, but other software may be caching actors, in order to let them know the actor has changed, you need to publish an Update activity on the Actor.
So just setting that configuration value to false does nothing as far as anyone else is concerned, because they've already a copy of your actor document, and they haven't been told it's been changed.
-
@heathenstorm that is, configuration changes like that only change what pixelfed serves / pushes from that point in time onwards, but other software may be caching actors, in order to let them know the actor has changed, you need to publish an Update activity on the Actor.
So just setting that configuration value to false does nothing as far as anyone else is concerned, because they've already a copy of your actor document, and they haven't been told it's been changed.
@heathenstorm why you're getting "No username provided" on the shared inbox though, I've no idea.
-
heathenstorm@mastodon.social I don't think it's wise to disable the shared inbox... I imagine it's just cached at the domain level once it is discovered (though that can differ between implementations of course.)
You mean that when you receive activities from Mastodon to Pixelfed's shared inbox, there is no username?
@julian That seems to be the case.
It could very well be the docker stack I'm using (elestio/pixelfed behind traefik) where something important gets stripped, but that's guesswork for now until I can effectively log what's being POSTed to the inbox.
Just weird that Likes go to the user inbox and boosts / comments don't.