Conversation

Notices

1. Embed this notice
   🏴A bas la propriété lucrative (oranadoz@framapiaf.org)'s status on Thursday, 04-Jan-2024 03:07:14 JST 🏴A bas la propriété lucrative

   • marius
   • Risotto Bias
   • Osma A
   • Hrefna (DHC)

   @mariusor I agree this would be great, but this won't happen as long as servers implement only their own interface, and by doing so server implementers don't work on common additional services like searching, but only adds stuff to their proprietary interface to make their life easier (but not clients' life).
   @helge @risottobias @hrefna @osma

   • Embed this notice
     Osma A (osma@mas.to)'s status on Thursday, 04-Jan-2024 03:07:11 JST Osma A

     in reply to

     • marius
     • Risotto Bias
     • Hrefna (DHC)

     @hrefna
     Moreover, if a protocol as all-encompassing as ActivityPub/ActivityStreams would need to first standardize a feature to the protocol foundations before anyone could implement that feature for their service, absolutely nothing could ever be done. It's hard enough today with so much of what has been defined in the protocol being so vague.

     Standards-track RFCs require several implementations for a reason.
     @oranadoz @mariusor @helge @risottobias

   • Embed this notice
     Hrefna (DHC) (hrefna@hachyderm.io)'s status on Thursday, 04-Jan-2024 03:07:11 JST Hrefna (DHC)

     in reply to

     • marius
     • Risotto Bias
     • Osma A

     @osma

     One thing that I think that ATProto is doing interesting things with in this space is separating these concerns. Basically by allowing the definition of applications (some would term them profiles) with dedicated semantics for how to declare them and interface with them. So you can define your own (RPCish) methods for actions on top of the protocol.

     We could do something similar with AP, but it's a really hard thing to do retroactively.

     @oranadoz @mariusor @helge @risottobias

   • Embed this notice
     Hrefna (DHC) (hrefna@hachyderm.io)'s status on Thursday, 04-Jan-2024 03:07:12 JST Hrefna (DHC)

     in reply to

     • marius
     • Risotto Bias
     • Osma A

     @oranadoz

     The challenge is that the baseline features of activitypub are essentially impossible to build an effective client off of.

     It's not just they are defining their own interfaces, it is that they _have_ to define their own interfaces if they want to be even reasonably effective at their chosen tasks at scale because of the limitations on how collections can be dereferenced

     There are ways around this with FEPs and such, but it's not in the protocol

     @mariusor @helge @risottobias @osma

   • Embed this notice
     smallcircles (Humanity Now 🕊) (smallcircles@social.coop)'s status on Thursday, 04-Jan-2024 03:08:42 JST smallcircles (Humanity Now 🕊)

     in reply to

     • marius
     • Risotto Bias
     • Robin Berjon
     • Osma A
     • Hrefna (DHC)

     @hrefna @osma @oranadoz @mariusor @helge @risottobias

     For those interested to ponder #ATProto + #ActivityPub ... at #SocialHub we have a discussion thread about @robin article on the subject:

     https://socialhub.activitypub.rocks/t/robin-berjon-running-activitypub-over-atproto/3707