Conversation

Notices

1. Embed this notice
   @reiver ⊼ (Charles) :batman: (reiver@mastodon.social)'s status on Monday, 24-Mar-2025 06:42:49 JST @reiver ⊼ (Charles) :batman:

   • Darius Kazemi

   . @darius :

   One problem with ActivityPub is that — it doesn't actually say anything about federation.

   And, different Fediverse software does it differently.

   #ATmosphereConf

   • Embed this notice
     Evan Prodromou 🎏 (evan@cosocial.ca)'s status on Monday, 24-Mar-2025 06:42:49 JST Evan Prodromou 🎏

     in reply to

     • Darius Kazemi

     @reiver @darius

     Section 1, first sentence.

   • Embed this notice
     Evan Prodromou 🎏 (evan@cosocial.ca)'s status on Monday, 24-Mar-2025 07:03:05 JST Evan Prodromou 🎏

     in reply to

     • Darius Kazemi

     @darius @reiver I guess I don't understand your point.

     The spec mentions federation a few times, but mostly it is in fact describing how to implement federation, so most of the text is talking about lower-level objects.

     Anyway, sounds like a great conference. Say hi to Blaine and Boris for me.

   • Embed this notice
     Darius Kazemi (darius@friend.camp)'s status on Monday, 24-Mar-2025 07:03:06 JST Darius Kazemi

     in reply to

     • Evan Prodromou 🎏

     @evan @reiver okay correction: doesn't say anything substantive about federation! Completely useless to me as an implementer!

   • Embed this notice
     Darius Kazemi (darius@friend.camp)'s status on Monday, 24-Mar-2025 07:42:09 JST Darius Kazemi

     in reply to

     • Evan Prodromou 🎏

     @evan my point is there are no rules of the road for how content should be sent around the network. It's how you get phenomena like "boost leaking" that can get around blocks

   • Embed this notice
     Evan Prodromou 🎏 (evan@cosocial.ca)'s status on Monday, 24-Mar-2025 07:42:09 JST Evan Prodromou 🎏

     in reply to

     • Darius Kazemi

     @darius I think the current best practice is to only use inclusion by ID for the `Announce` activity, for this very reason.

     But I agree that the public-except-unpublished-denylist access mode is really hard to make work right.

     I also think there are trade-offs between the efficiency of sending activities with lots of data, and the level of control when sending minimal activities. I have a long section about this in my book, but it might be good to include guidance in the Primer or the next AP.