Honestly jb, I’m going to declare independence from fiatjaf’s madness soon.
I’ve been interested in @elsat nostrability for maintaining compatibility across clients, as I’m sure you’re aware.
I’m working on a clear standard (list of cleaned up NIPs etc) that others can follow if they don’t want to try to sift through fiatjaf’s madness.
It will avoid relay hints for discovering missing content, and other bad/messy ideas (like NIP04) — distilling the best of #nostr.
Most of it aligns with Damus etc, but I’ve got a new outbox method that I’m eager to share soon. It doesn’t rely on the blockchain at all… it’s free and fast.
You all can be the judge of it soon.
Nostr is not what fiatjaf says it is. He helped start it, but I suspect the people are going to be the ones to scale it. People like us. Personally, I see fiatjaf almost always arguing in a disingenuous way — then he blames others for not knowing what to do.
As long as we create a standard that many clients can follow in a compatible way, we don’t need his mad king behavior.
What do you mean "It doesn't rely on the blockchain at all" ?
Who is building anything here that relies on the blockchain?
An old spec of mine tried to solve the consistency problem of Nostr by putting merkle roots of profiles on-chain. It was just too expensive for users & totally not scalable. Back when I first joined Nostr two years ago. I can admit when I was wrong. Have iterated since then.
Hmm.. We need to have the right incentives for more and better event transmissions to relays? Goal could be broader event distribution among the network of relays.
Oddbean new post about login | logout