Once a while i was wondering if #ActivityPub could replace #smtp mail where i was answered that i was different and seem to surprise people.
Now i'm reading this https://bifurcation.github.io/mimi-aim/draft-barnes-mimi-aim.html and it seems to confort me in my stubborness.
Now i'm reading this https://bifurcation.github.io/mimi-aim/draft-barnes-mimi-aim.html and it seems to confort me in my stubborness.
A quote :
At a very high level, #ActivityPub is similar to SMTP with JSON messages and delivery over HTTP. An ActivityPub server forwards messages from local clients to their intended recipients, and receives messages from other servers intended for its local clients.
At a very high level, #ActivityPub is similar to SMTP with JSON messages and delivery over HTTP. An ActivityPub server forwards messages from local clients to their intended recipients, and receives messages from other servers intended for its local clients.
Follow
I'd say a difference is that ActivityPub encompass quite a lot of the stack and centralizes a lot of functionality to instances while SMTP simply (ha) focuses on transport.
That difference is not trivial!
From questions of efficiency through user responsiveness and application flexibility, it pushes towards one-size-fits-all centralization.
Really, it might be the difference between http and the old platforms like AOL.
