Oddbean new post about login | logout Who's gonna build the relays? (Joke aside, I've heard that the post popular relay software is unmaintained. That's really bad. 🚨)
Strfry? It's open source so should be simple enough to address issues if they're needed and people want it done.
Last PR is 6 months, that's not a good sign.
Looks like a new maintainer with the necessary C++ experience needs to fork it. Probably a case for @OpenSats to support? Also, a bus factor of 1 is not great for the software that powers most nostr relays. A fork should probably go to a community namespace/repo to begin with.
Chorus by nostr:nprofile1qqswuyd9ml6qcxd92h6pleptfrcqucvvjy39vg4wx7mv9wm8kakyujgpypmhxue69uhkx6r0wf6hxtndd94k2erfd3nk2u3wvdhk6w35xs6z7qgwwaehxw309ahx7uewd3hkctcpypmhxue69uhkummnw3ezuetfde6kuer6wasku7nfvuh8xurpvdjj7a0nq40 looks pretty promising https://github.com/mikedilger/chorus
Chorus is maintained. And I think it is pretty fast.
"Relays are not hot product" - Someone probably. I think it is probably due to main focus development in Nostr is frontend Nostr clients and some other stuffs. 😅
There is zero support for the relays from the nostr elites. Relays operators are continually leaving. It's a double loss, because you lose the infrastructure, and also a talented developer that was interested in the project. Nostr has a king maker problem.
There are a lot of relay implementations and yes some aren't being maintained. @fiatjaf has four! khatru, pyramid, relay29, relayer. @Alex Gleason 🐍 ditto, My chorus @mleku replicatr @scsibug nostr-rs-relay @Doug Hoyte strfry @Cameri's nostream