David @mleku - 1y
getting event broadcast working with the #layer2 event store has totally made my day aside from this issue with clients refusing to connect (i have a clue i can fix that too) #replicatr is MVP, release candidate grade actually, i better see if i can fix that other issue, it's not critical for the task as the screencast shows it is more than adequate for demonstrating that i used a shitcoin database as intermediary store for nostr, i want it working for my own reasons, because the next nostrudel doesn't work nor does coracle or others, so i can assume that there is an error in my websocket code somewhere
i just added a default that opens a local port in addition to the configured listener so now when i run the relay i get nostrudel cache relay and a public relay at the same time (means that my relay is constantly being populated by events that match up to what i browse on nostrudel still gonna need to do more debugging to figure out why coracle et al (and next.nostrudel.ninja, and everything) are not talking to #replicatr it's quite odd that it only just popped up recently, it must be related to recent changes in the javascript nostr relay connection libraries
yes, #replicatr can run multiple instances on different network listeners... i just disabled the main configuration feature because for some reason the CLI args library i'm using stopped working with string arrays, will work on this later, but for now it by default listens on localhost this should be no problem for any production deployment and means anyone can run replicatr on their machine and hook it up to nostrudel's cache relay WHEN i get the damn connection working again it will work on others
