Developer of ActivityPub-based micro-blogging and content subscription platform Mitra. I help maintain the FEP repository and write my own FEPs too. Currently working on ActivityPub Next.
Shoot uses a variant of FEP-1b12 for group chats, it is the same protocol on which Lemmy communities are built.
However, chats typically require a more fine-grained permission system than Lemmy currently offers. This is what I am working on: FEP-5219: Groups and permissions
>end-to-end-encryption
Not a thing yet.
It’s not vibe-coded and the developer published several FEPs to help others implement same features (e.g. FEP-bebd: Follow Invites)
https://fedilist.com/ is a good alternative
There is already a chat system based on ActivityPub: https://shoot.pub/
We haven’t decided yet what DID method to use. In my opinion, did:webvh is the most promising candidate - it is self-certifying (like did:key) and supports key rotation
How do you explain this? https://github.com/bonfire-networks/bonfire-app/blob/main/AGENTS.md
I mean event kinds: https://github.com/nostr-protocol/nips?tab=readme-ov-file#event-kinds
ActivityPub has Note and Follow, Nostr has 1 and 3.
I don’t know much about recent developments, but the early version of the protocol had several major flaws:
- Identity is based on a non-rotatable key, other types of identity are not supported.
- No privacy without encryption.
- Media attachments are not supported, all images are stored on a single server.
- Servers only store data and don’t do anything else, so they get abstracted away and everyone uses the same 5 relays (in Fediverse each server has a personality, and that creates a strong incentive to self-host).
There are also many minor things that I dislike, for example the use of numbers instead of human-readable names, unusual cryptography and so on.
@doesnm @hendrik @fediverse I am not that much against AI but 99.9% of slopware is garbage, and a developer needs to do something extraordinary to prove that their thing is worth my attention.