Post B4ORAvGv8Ccq46qPI0 by mczachurski@mastodon.social
(DIR) More posts by mczachurski@mastodon.social
(DIR) Post #B4MHWA5PrJvqEd23SC by wakest@public.mitra.social
2026-03-17T19:26:00.683948Z
0 likes, 0 repeats
Looks like federation between Mitra and Vernissage is currently broken cc @silverpill @mczachurski
(DIR) Post #B4MHWBeu0rub6yduPA by silverpill@mitra.social
2026-03-17T19:40:30.982174Z
0 likes, 0 repeats
@wakest @mczachurskiThe delivery of Follow activity was successful:-> https://vernissage.photos/actors/wakest/inbox, status code 200It appears that vernissage.photos can't discover the actor. Sometimes this happens because Mitra uses unusual media types in JRD:https://codeberg.org/silverpill/mitra/src/branch/main/FEDERATION.md#notable-differences
(DIR) Post #B4ORAvGv8Ccq46qPI0 by mczachurski@mastodon.social
2026-03-18T16:09:16Z
0 likes, 0 repeats
@wakest I found the issue was caused by Mitra not exposing /.well-known/host-meta. In such cases, I implemented a fallback to the default WebFinger endpoint. Account resolution works, and follow/like activities will likely work as well. However, posting statuses and boosts to Mitra will not work, because it does not expose a sharedInbox. As a result, delivery would have to be performed separately for each recipient inbox, which is less efficient and does not scale well. 🤔 @silverpill
(DIR) Post #B4ORAw720SJEfjE1Vw by silverpill@mitra.social
2026-03-18T20:38:12.968644Z
0 likes, 0 repeats
@mczachurski @wakestIt doesn't need to scale because mitra servers are small. Also, ActivityPub requires delivery to personal inbox if shared inbox is not available:Origin servers sending publicly addressed activities to sharedInbox endpoints MUST still deliver to actors and collections otherwise addressed (through to, bto, cc, bcc, and audience) which do not have a sharedInbox and would not otherwise receive the activity through the sharedInbox mechanism.-- https://www.w3.org/TR/activitypub/#shared-inbox-delivery