silverpill

One can also follow hashtags at https://relay.fedi.buzz/

I mean they don’t provide any good examples of how this technology could be used.

There is one real use case for ZKP: private payments. It seems that there is no demand for other applications.

POD enables internet users to store and share data that preserve its integrity.

It’s not clear how this is better than regular signatures

How do you discover Lemmy communities? Federated categories in Discourse work in the same way, so a tool capable of discovering Lemmy communities should also be capable of discovering Discourse forums.

Discourse has an ActivityPub plugin: https://discourse.org/plugins/activitypub

This plugin, for example, is enabled on SocialHub https://socialhub.activitypub.rocks/ap/about (it’s a forum for fediverse developers)

I suggested the following definition for Fediverse Enhancement Proposals:

The Fediverse includes applications, services and communities using the ActivityPub protocol, its predecessors, and other historically related protocols that foster decentralized and diverse social media and culture.

https://codeberg.org/fediverse/fep/pulls/544/files

Under this definition, Hubzilla and Webfinger are parts of Fediverse.

Unfortunately, this PR was bike-shedded into oblivion.

Yes, it is known as “nomadic identity”:

https://codeberg.org/ap-next/ap-next/src/branch/main/nomadpub.md

If you run a small micro-blog instance, you follow some people and maybe some communities. Tagged posts come only through these follows, so you only see a tiny portion of all tagged posts.

A hashtag relay tries to aggregate tagged posts from the whole network. By following a hashtag on such relay you can see more posts on the topic that interests you.

I think it is a useful service, because it helps small instances discover content. However, this idea is not new and another service of that kind, FediBuzz, has been operating for a long time.

Forte and tootik use FEP-ef61 with server-managed keys. I am working on an application where keys are stored on the client side: minimitra. This is probably closer to your idea.

Do you want to use iroh for transport, or for identity?

@robert.meyer86 See also https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md. This is already part of Fediverse and has multiple implementations.

@SorteKanin My server translates Lemmy upvotes into likes and downvotes into dislikes. That blends quite well in the UI with Mastodon’s “favorites” and Pleroma/Misskey emoji reactions, so I think Lemmy’s assumptions are correct

Identity based on a pubic key is already not theoretical, it is supported by services that implement FEP-ef61.

I am not sure whether it makes sense to separate data hosting and feed generation, this will probably require a specific network architecture, similar to Bluesky, which tends to be centralized.

I doubt that it will be implemented in Lemmy, the application architecture needs to be different in order to support cryptographic identities.
But there are other implementations (they are listed near the end of the document).

That’s correct.

did: prefix is used to denote cryptographic identifiers, in theory one could even take a did:plc identifier from Bluesky and then use it as identity for an ActivityPub application:

https://github.com/bluesky-social/atproto/pull/3943

Yes, domain names can be replaced with cryptographic identifiers: https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md

DID-based identity already exists in Fediverse: https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md

We currently use did:key but in theory any DID method can be used, someone even tried to use did:plc: https://github.com/bluesky-social/atproto/pull/3943

Yes, it is feasible and such instances already exist.

For example, you can run a Mitra instance on Tor, I2P or Yggdrasil. It is a lightweight micro-blogging server similar to Mastodon:

https://codeberg.org/silverpill/mitra

Tor / I2P docs:

- https://codeberg.org/silverpill/mitra/src/branch/main/docs/onion.md
- https://codeberg.org/silverpill/mitra/src/branch/main/docs/i2p.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.