Plebs with MacBooks.
People talk about "noncustodial" and "open source" but they love to use these hosted Docker images they didn't build or verify.
How long do these trips last? Can you talk to each other comfortably while up in the air?
If your censorship-resistance model involves asking everybody in the world to migrate from client A that is blocking someone to client B that isn't blocking then Nostr hasn't given you anything Twitter/Facebook/Substack/YouTube/Rumble/Mastodon were not giving you.
I would say it is ok to have a trusted and centralized server making recommendations, displaying lists of interesting content and curated home feeds, but the actual act of fetching the data from people you follow must be done on the client-side and using something like the outbox-(gossip)-model thought, otherwise there is no censorship resistance at all.
Yes, I know that. nostr.band is not advertising itself as a "client" though.
The line is subtle, but if you don't care about that then you are wrong. If most people don't care then Nostr is dead and we're just wasting our times.
I think NIP-26 is a bad idea that will eventually destroy Nostr and that you NIP-26 enthusiasts are not thinking correctly and you should stop a little. Should I still merge your PR?
Why these people make very high-quality music production and publish on YouTube but then either prefix or suffix the actual song with some musical intro or ending that destroys the entire production?
I hate the new https://coracle.social/ home page, it forces me to click on a button to go the actual app every time!
Unfortunately it is just a closed thing that only talks to its own backend, so it negates all the censorship-resistance properties that Nostr was supposed to have.
Compiling to every platform in one second from anywhere with Go.
Good points. What is a good way to present the test vectors so it's easy for people to check their implementations?
Hard to know. I think my notes always have relay hints and that should help. Have you followed those?
wss://nos.lol/ is what it says.
But people are using these evil clients that do not include hints, like Iris, which is awful and breaks threads for me too sometimes.
Now what do we do with the money?
introducing the worlds first Nostr Signing Device!
🗝️Protect those keys🗝️
https://www.youtube.com/watch?v=SD6OQPoNlzA
Huge props to #[0], Stepan Snigrev, Vlad Stan
How much does the device cost?
I didn't try this time, but yes, they just don't seem to care about any of the things that are relevant.
Were these notes about zaps in Mostr supposed to be reference each other?
I am hoping Bitcoiners will stop pushing and defending stablecoins "for the poor" after this. If they continue it's because they fell they're part of the annointed class of "non-poor". Or whatever the crap they say, "global south".
This is somewhat of a relay policy, I think, it doesn't harm the protocol itself, but I would personally like to block these too.
I agree they should not. The untethr relay does not, same for strfry, I think. I'm not sure about nostr-rs-relay and Nostream.
Please do not accept invalid events in your client. Do not accept non-integer "created_at" values, do not accept non-string-array on "tags", do not accept bech32-encoded keys as tag values. Every time you do that, Nostr dies a little.
For more information on how this kills Nostr, read https://fiatjaf.com/27598e6f.html
For all the people who are eager to reply that Nostr should be able to handle bad practices otherwise it is already dead, or to say that "please" won't work, or these sort of comments, I must tell you that Nostr is not "antifragile", it is indeed very fragile, as all open protocols (including Bitcoin).
Although Nostr is much more fragile than Bitcoin, specially while it is small. Hopefully, while it is small, I do expect that "please" and civil discussions will work, as most people here want Nostr to succeed, and keeping it simple will increase these chances.
Please do not accept invalid events in your client. Do not accept non-integer "created_at" values, do not accept non-string-array on "tags", do not accept bech32-encoded keys as tag values. Every time you do that, Nostr dies a little.
For more information on how this kills Nostr, read https://fiatjaf.com/27598e6f.html
Did you know you can compile Go programs for MacOS (or for any other OS) from any other OS?
Go > Rust
What about GitHub Actions? They have MacOS there.
Announcement of an announcement.
What will that be?