Conversation

Notices

1. Embed this notice
   @reiver ⊼ (Charles) :batman: (reiver@mastodon.social)'s status on Friday, 20-Oct-2023 15:50:04 JST @reiver ⊼ (Charles) :batman:

   There are a lot of different types in the ActivityStreams Vocabulary.

   https://www.w3.org/TR/activitystreams-vocabulary/

   But because Mastodon only supports 8 of them (with only 2 of them being supported properly), there is "pressure" on other Fediverse software to restrict themselves to these 8.

   https://docs.joinmastodon.org/spec/activitypub/#payloads

   Because they want to be compatible with Mastodon.

   #ActivityPub #ActivityStreams #Fediverse #Mastodon

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Friday, 20-Oct-2023 15:50:04 JST Evan Prodromou

     in reply to

     @reiver this is weird, because we specifically built in fallback representations into the base Activity and Object classes. With icon, summary, image, name, and so on, software that doesn't understand what's going on has a way to show some sort of representation to the user.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Friday, 20-Oct-2023 20:56:18 JST Evan Prodromou

     in reply to

     • feb

     @feb @reiver it doesn't implement the whole spec, so no, I don't think it should be the reference implementation.

   • Embed this notice
     feb (feb@loma.ml)'s status on Friday, 20-Oct-2023 20:56:25 JST feb

     in reply to

     • Evan Prodromou
     @evan @reiver
     Shouldn't Mastodon be the reference implementation of AP? If it only represents a part, then perhaps one should look at which project does it better.
     Evan Prodromou repeated this.
   • Embed this notice
     Martin Atkins (apparentlymart@mastodon.online)'s status on Saturday, 21-Oct-2023 08:36:27 JST Martin Atkins

     in reply to

     • Evan Prodromou
     • feb

     @feb @reiver @evan

     It's funny that when I was originally thinking about Activity Streams, around 2008 or so, it seemed very clear to me that the application for "reading your friends" and the application(s) for creating content would be two different things, with the former being a largely-read-only (aside from likes/comments, perhaps) generic thing that supported many object types.

     Of course, that's because I was still "RSS/Atom-brained" at that time, thinking of enriching feeds.