ANNOUNCEMENT: New Relay Software called Chorus

"Here ye, here ye, the herald hath proclaimed that a wizened old mage from the beige tower to the South hath bestoweth upon our land yet another relay implementation of potential great import and with great anticipation. And the people rose up in song and in praise of this new relay software. And the people called it "Chorus" for it had inspired them to sing." - 1st Abominations 13:37

Chorus is a new nostr relay software implementation, brought to you by the same guy that brought you the Gossip client.

Interviewer: Why did you write chorus?

Me: I don't know.

Interviewer: Why should somebody run chorus as opposed to another relay implementation?

Me: I don't know.

Interviewer: Have you even thoroughly tested this relay yet before announcing it?

Me: Um....

Interviewer: Do you even use it yourself?

Me: Not as such. Well, not yet. I think I should test it first.

There you have it folks! Pay no attention to the fine print below.

I've been thinking about distributed, rag tag tech solutions for decades, but theyve been in sharp focus the past few weeks and days in particular.

I'm imagining a community of people who each run some services which will be down some of the time, but you always want everyone to be able to use everything all the time.

At first I was thinking load balancers, round robin DNS, failover... you know, the tried and true solutions. But those all have huge problems in this type of environment.

Then it hit me. Go back to computing in the 80s and 90s, where it was expected that people and even servers would be offline regularly. Take inspiration from BBSes, email, and the more modern systems like git, RSS (with auto-downloading).

#Nostr is designed along these same lines too. Nostr clients don't let you post while offline like you can send an email while offline, but that's just a client implementation decision.

Effectively, the point is to make things work well offline.

This strategy doesn't work well for some things like real time communications (video teleconferencing, voice calls, etc.) or when multiple people make changes to the same file at the same time. So we need different solutions there.

⚡️Breez SDK with Jesse de Wit

Live streaming on YouTube and Zap.Stream