hodlbod's avatar
hodlbod hodlbod@coracle.social 6 months ago
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).

Replies (22)

RedTailHawk's avatar
RedTailHawk redtailhawk@nostrplebs.com 6 months ago
I consider it a minor miracle that I'm even using NOSTR as my relatively very limited coding background is mostly irrelevant. With that in mind, I would not hesitate to call myself a NOSTR noob even though I've been here for a while, simply because I don't understand a lot of the super technical stuff. Frankly, I won't even use Github because I don't know how to navigate it. That said, is this relay thing you made going to make my life easier as a NOSTR noob in terms of relay management? Right now I kind of just hope it works and don't manage anything.
1 replies ↓
RedTailHawk's avatar
RedTailHawk redtailhawk@nostrplebs.com 6 months ago
Thank you. NOSTR needs stuff like this. I would zap you but I’m having an electrical issue and my node is down and I am too much of a noob to work around it.
hodlbod's avatar
hodlbod hodlbod@coracle.social 6 months ago
Well, that's sort of orthogonal to this problem, since the point of indexers is to have a copy of 10002s. But I agree that bootstrapping isn't really solved. Not all clients post relay selections to indexers, and even if they did indexers are sort of centralized right now. There should probably also be a service that scans the entire network and replicates relay selections to known indexers.
1 replies ↓
hodlbod's avatar
hodlbod hodlbod@coracle.social 6 months ago
I don't think it would be bad to just add a `path` tag to that event, but I'm not really sure how people are currently using it, or how bad not having a path would be.
hodlbod's avatar
hodlbod hodlbod@coracle.social 6 months ago
Yep, I use it to sync my indexer with a few others. Outbox model is somewhat more complex though, replicatr is intended to help fix missing note parents and stuff like that (although I can't help wondering if it's a band-aid solution).
↑