I suggest all of you check out the Versia Protocol, it is very interesting and I feel it has a lot of potential to become a standarized protocol.

It is ActivityPub/Fediverse-styled, in the sense that it operates under the idea of small pockets of users and informations that sync up on eachothers' data through simple communication

Some of the stuff I think it does better than ActivityPub:

1. Enforces hard endpoints for data fetching and backfilling
2. Enforces the ability for instances to change domains, as well as users to change handles
3. Has a server-to-server communication protocol for error logging and handling protocol implementation issues
4. Does not use JSON-LD, instead, opts in for a much simpler extension system that simply defines a set of values under an object
5. Implementing it is a very streamlined and straightforward experience, where most of the features you want (such as emoji reactions, likes, replies, etc.) are already part of the core standards as optional extensions.
6. Instead of having several ways to describe an object containing text and media, it simply has all of them under the same umbrella, with a couple of configurable options that serve mostly as tools for figuring out how to display an incoming "Note"
7. Encryption and signing are enforced.

#activityPub #fediverse #protocol #versia

I suggest all of you check out the Versia Protocol, it is very interesting and I feel it has a lot of potential to become a standarized protocol.

It is ActivityPub/Fediverse-styled, in the sense that it operates under the idea of small pockets of users and informations that sync up on eachothers' data through simple communication

Some of the stuff I think it does better than ActivityPub:

1. Enforces hard endpoints for data fetching and backfilling
2. Enforces the ability for instances to change domains, as well as users to change handles
3. Has a server-to-server communication protocol for error logging and handling protocol implementation issues
4. Does not use JSON-LD, instead, opts in for a much simpler extension system that simply defines a set of values under an object
5. Implementing it is a very streamlined and straightforward experience, where most of the features you want (such as emoji reactions, likes, replies, etc.) are already part of the core standards as optional extensions.
6. Instead of having several ways to describe an object containing text and media, it simply has all of them under the same umbrella, with a couple of configurable options that serve mostly as tools for figuring out how to display an incoming "Note"
7. Encryption and signing are enforced.

#activityPub #fediverse #protocol #versia

I suggest all of you check out the Versia Protocol, it is very interesting and I feel it has a lot of potential to become a standarized protocol.

It is ActivityPub/Fediverse-styled, in the sense that it operates under the idea of small pockets of users and informations that sync up on eachothers' data through simple communication

Some of the stuff I think it does better than ActivityPub:

1. Enforces hard endpoints for data fetching and backfilling
2. Enforces the ability for instances to change domains, as well as users to change handles
3. Has a server-to-server communication protocol for error logging and handling protocol implementation issues
4. Does not use JSON-LD, instead, opts in for a much simpler extension system that simply defines a set of values under an object
5. Implementing it is a very streamlined and straightforward experience, where most of the features you want (such as emoji reactions, likes, replies, etc.) are already part of the core standards as optional extensions.
6. Instead of having several ways to describe an object containing text and media, it simply has all of them under the same umbrella, with a couple of configurable options that serve mostly as tools for figuring out how to display an incoming "Note"
7. Encryption and signing are enforced.

#activityPub #fediverse #protocol #versia

@jackwilliambell @neia

Oh, what also just comes to mind is the #Polyproto protocol. I think it may have been created in reaction to ActivityPub's complexity and issues around identity, not sure.

https://polyproto.org

And another protocol in the works, inspired by AP is #Versia.

https://versia.pub