<![CDATA[Has anyone else had trouble with the #pixelfed shared inbox?]]>Has anyone else had trouble with the 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 go to the user inbox, Boosts and Comments go to the shared one.

I disable shared inbox in pixelfed .env and Mastodon still sends to /f/inbox even after refreshing the cached pixelfed profile.

At least I know why it's happening now!

]]>https://bb.devnull.land/topic/9beebdfd-8c58-442d-8b57-b4c179cbb20f/has-anyone-else-had-trouble-with-the-pixelfed-shared-inboxRSS for NodeTue, 21 Jul 2026 03:13:34 GMTMon, 24 Nov 2025 00:10:02 GMT60<![CDATA[Reply to Has anyone else had trouble with the #pixelfed shared inbox? on Mon, 24 Nov 2025 14:17:53 GMT]]>@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.

]]>https://bb.devnull.land/post/https://mastodon.social/users/heathenstorm/statuses/115605102507745035https://bb.devnull.land/post/https://mastodon.social/users/heathenstorm/statuses/115605102507745035Mon, 24 Nov 2025 14:17:53 GMT<![CDATA[Reply to Has anyone else had trouble with the #pixelfed shared inbox? on Mon, 24 Nov 2025 02:57:14 GMT]]>@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?

]]>https://bb.devnull.land/post/https://activitypub.space/post/642https://bb.devnull.land/post/https://activitypub.space/post/642Mon, 24 Nov 2025 02:57:14 GMT