rich1.0hodlbod (npub1jl…jynqn)https://nostr.ae/npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqnnjumphttps://nostr.aeSo I was listening to nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpz4mhxue69uhkummnw3ezummcw3ezuer9wchszxthwden5te0wpex2mtfw4kjuurjd9kkzmpwdejhgtcprpmhxue69uhhyetvv9ujuer9wfnkjemf9e3k7mf0qyd8wumn8ghj7ur4wfshv6tyvyhxummnw3ezumrpdejz7qpqdergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsce9rzs and nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0qyghwumn8ghj7mn0wd68ytnvv9hxgtcqyqnxs90qeyssm73jf3kt5dtnk997ujw6ggy6j3t0jjzw2yrv6sy22vuwtly talk about replicating content across relays this morning, and so I wrote replicatr: https://github.com/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).