So I was listening to @Gigi and @hzrd149 talk about replicating content across relays this morning, and so I wrote replicatr:

GitHub

GitHub - coracle-social/replicatr: A daemon that monitors nostr relay selections and replicates user events based on the outbox model

A daemon that monitors nostr relay selections and replicates user events based on the outbox model - coracle-social/replicatr

Replicatr is a daemon which listens to one or more indexer relays for `kind 10002` events. When it detects a change in any user's relay selections, it uses negentropy to sync that user's notes to their new relays based on the outbox model. The neat thing is you don't have to run one. I deployed one this morning which points to indexer.coracle.social, so if your metadata gets published there (or to any of the relays that it mirrors), you're already covered (unless your new outbox relay rejects replicatr's publishes).