Still a lot of work to do to make it anywhere remotely as functional as the major clients, but that's not entirely the goal. This will be pretty minimalist. I'll release the full code after the next post, which won't take nearly as much work!
After a long, busy summer, I finally got around to wrapping this post up.
"Building a nostr client [1]"
This kind of functionality is absolutely necessary if we want relays focused around specific communities. Please make relays a focus in clients!
“What are the biggest obstacles for NOSTRs success?” h/t #[0] https://twitter.com/ck_snarks/status/1652661119650000896
It's amazing to me how people make assumptions about how nostr works as if they didn't spend < 10 minutes reading the protocol doc.
I'll always agree execution matters more than the idea. No arguments there. I think we also agree that at the end of the day, the relay operator (and client to some extent) can always accept or deny whatever content they choose.
I think what I'm trying to get at is: classification does not mean censorship. None of the NIPs related to reporting (self or otherwise) suggest relays or clients should act one way or the other. So that's why I don't see what all the fuss is about.
With regards to incorrect self-tagging, yeah that sucks. Some people will get that wrong. I don't think removing all options for self-tagging is a good idea though. And that's where a common language goes a long way to helping relays and clients know what they are dealing with.
As for gaming the reporting, that will always be a risk, for sure. But it's not intractable. Reputation goes a long way, operators and moderators can be weary of reports from pub keys that have no history on their relay, etc. Tooling is key here.
When you say "you can even moderate, and censor your community with your own rules" and then say "it doesn't belong [...] arbitrary moderators making decisions", how are you reconciling those two ideas?
I don't understand. Hasn't the argument for these classifications always been that they are optional to enforce? I don't see why having common language to describe the problem is an issue. Relay operators are always free to use or ignore them.
Due to the heavy solar flare that came towards Earth this weekend, I was able to see aurora borealis tonight as far south as Iowa! I had never seen them before. They were pretty mild I'm sure compared to what is possible but damn, what a cool experience.
This is the kind of stuff I love to see in the nostr ecosystem.
These kinds of "meta" tools will develop far faster and with more innovation than any centralized platform could provide.
#[0]
Where are we at with relay design? Is anybody working on the deployment that can serve 1 million users?
Maybe it's "easy" enough to just split the write and read paths as long as we're willing to accept some eventual consistency.
Bookmarked. Thank you
I don't think so but definitely worth getting it going
Published a post about setting up NIP05 DNS verification using the zola static site generator: https://nickmonad.blog/2023/nostr-verification/
hello, nostr