@76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa @eris @strypey @5be6446aa8a31c11b3b453bf8dafc9b346ff328d1fa11a0fa02a1e6461f6a9b1 > a way to have multiple mostr instances.

So, here's my recent discovery on that: https://codeberg.org/fediverse/fep/src/branch/main/feps/fep-fffd.md

Currently Mostr publishes kind 1 notes. It contains a tag linking back to the original ActivityPub object like:

["mostr", "https://gleasonator.com/objects/123"]

Technically this is enough for Nostr clients to consolidate multiple ActivityPub events into one. We'd also want relays to let us filter by this tag.

However I'm a big fan of the "proxy objects" concept, which aims to be a way of representing _any_ object on a different decentralized network.

On Nostr we could generalize the tag so it would work with ActivityPub, Bluesky, etc. Clients would have to support it (by treating all events with the same tag as one), and relays should support filtering by the proxy ID for the best UX.

On the ActivityPub side, servers can use the FEP.

The only problem is that if we canonicalize a way to represent people on other networks using any keypair, there needs to be a way to confirm the object isn't forged, which would necessarily require all software to implement all protocols... so that's where I'm stuck.