Shout out to the client devs I appreciate all the hard work you put in 🫡
bitcoinplebdev
bitcoinplebdev@bitcoinpleb.dev
npub1s9et...lxzl
voltage.cloud
plebdevs.com
frostr.org
visibible.com
BTW I’ve run multiple relays over the last few years and currently keep one active to help support plebdevs.com
I believe the world where nostr wins is one where there is a robust network of highly available relays that many end users run.
Better incentives are required to reach this world otherwise we will just end up in another highly centralized client/server model system. View quoted note →
Ok so access control, specialized services, access/gateway to exclusive networks, communication efficiency (if I’m understanding correctly?)
These are all interesting possibilities but it feels to be a bit of a stretch still, where are examples of such use cases? Most importantly what is the BASE case for running a relay? View quoted note →
Solid answer
For context I run a relay for plebdevs.com for the reasons of data availability and data backup for my notes. All of my courses and workshops are in notes on my relay (and many others)
STILL I am incentivized to keep this relay private, use it for my own selfish means of backup, and continue to abuse the large relays to take advantage of wider distribution. View quoted note →
1. I don’t understand? My client signs and broadcasts my notes to relays, how does running my own change that?
2. Other relays already store my data?
3. What am I even selling, what benefit would I be selling to others!?!?
4. Education on what? Running a server? View quoted note →
Ok so relay as a service, but why even pay for a relay when I can use the biggest relays for free? What advantage or unlock does running my own relay give me?
View quoted note →
So I should?? Why not use top relays like everyone else?
There are dozens of highly available fast VC funded relays. What is my personal incentive?
View quoted note →
Why run a relay?
Noooooooooo View quoted note →
Notes and other stuff transmitted by retards
TOP OF THE MORNING
Will be working on more documentation. These are the core libraries though:
View quoted note →
GitHub
GitHub - cmdruid/frost: Flexible, round-optimized threshold signature library for BIP340 taproot.
Flexible, round-optimized threshold signature library for BIP340 taproot. - cmdruid/frost
GitHub
GitHub - FROSTR-ORG/bifrost: Core library for implementing the FROSTR signing protocol.
Core library for implementing the FROSTR signing protocol. - FROSTR-ORG/bifrost
GitHub
GitHub - cmdruid/nostr-p2p: Build your own peer-to-peer messaging protocol, transmitted by relays.
Build your own peer-to-peer messaging protocol, transmitted by relays. - cmdruid/nostr-p2p
Nostr is not inevitable, it must be built, and built upon.
Frostr fixes the nostr identity problem
No more single point of failure, same signing UX. View quoted note →
No, you can rotate (effectively revoking old keyset) with EITHER nsec or threshold of shares View quoted note →
Thanks! Frostr supports key rotation today t-of-n thresholds (so you can rotate into the same threshold or even a different threshold) View quoted note →
It removes single point of failure
Allows for flexible quorum of remote signers (while still keeping offline backup) View quoted note →
Correct no revocation needed.
Just rotate and the new keyset will invalidate your old keyset View quoted note →
For the record I agree with Parker
Single point of failure is unacceptable and nostr influencers have oversold the adversarial aspects of nostr
Key management and relay centralization/incentives are the biggest problems in Nostr in my opinion. Frostr helps with key management. Relays will be next. View quoted note →
To rotate simply collect threshold of shares
Or fully regenerate from nsec (effectively a rotation) View quoted note →