🫧 socialcoding.. @smallcircles@social.coop
Public

@evanEvan Prodromou @cwebberChristine Lemmer-Webber @steveSteve Bate

So why don't you use the word REST? I never encountered "read-write API". It is an informal term.

But that is not the point. You can have a REST API, fine. But that says nothing in itself. What does it expose? You might say "Duh.. ActivityPub!" but that is not very informative either. There is the notion of message exchange, and of an addressing mechanism, indicating higher level abstractions that conform to well-known architecture patterns, and would allow us to have more productive communication, delve less in implementation details and confusions of protocol behavior with solution design functionality, for starters.

Evan Prodromou @evan@cosocial.ca
Public

@smallcircles🫧 socialcoding.. @cwebberChristine Lemmer-Webber @steveSteve Bate I'm fine with that.

However, I think ActivityPub builds up persistent state on the server side which can be read and used by other processors.

For example, when I `Like` something, it goes into my `liked` collection, and the activity goes into the `likes` for that object. The `Like` activity goes into my `outbox` and others' `inbox`. People can review that information and use it.

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://cosocial.ca/users/evan/statuses/116109954852018473 on your instance and quote it. (Note that quoting is not supported in Mastodon.)