Replies (40)

KotlinGeek's avatar
KotlinGeek 7 months ago
Please don't. It's now part of my muscle memory to look them up there. Thanks.
I don't think nostr is bootstrapped enough yet. I think once it's got legs, definitely delete it.
My problem is not the centralization, my problem is with the format. It's not good for what it has become. Also the cognitive load and confusion.
It seems much more sensible, since GitHub is still widely viewed, to maintain it as a gateway for those just starting to learn about the Nostr and the Nips. And just add links to the right places.
Just random people writing guides of "how to do whatever on Nostr" in any format they want.
No, they wouldn't. And I'm not sure we need a kind numbers repo, although that sounds like a good, harmless feature to me now.
you should, and then someone else should recreate it, disproving your centralization hypothesis
So the question becomes discovery of the specs? It would be great to have some at least decent solution, otherwise all new devs will hate it.
Some of those issues I can diagnose from this photograph of nostr: 1) Sometimes our wires gets crossed 2) Usually we are not talking from deep down, but that changes when we are at conferences 3) Take care to avoid the triangle hazards 4) Relays will gossip
There are really basic things being discussed, still. It's fine not to have secondary things in the repo, but core stuff should be sorted out and a central repository is especially important for newcomers. Consider how many times the standard for quoting events has changed, drastically. If you had gotten stuff right at first it wouldn't matter as much, but the repo is still serving its goal.
U's avatar
U 7 months ago
I think future devs/maintainers will be happy to find at least some grave yeard archive of sorts, to be able to understand legacy code ๐Ÿ‘ป
โ†‘