Why would anyone use something that is supposed to liberalize spec publishing, that is "expert"-gated, just like the GitHub repo is? That was _precisely_ what we were trying to solve for by moving it to Nostr, but you just transferred the same structure to json.
Embrace. Extend. Extinguish.
I can't even manage to make a surprised face about this stuff, anymore.
Whatever, I have my own client and now pollerama also offers a viewer. You do you.
Login to reply
Replies (11)
if theres no gates the elites cant hide behind them from the plebs
thank you for showing up at precisely the time you were expected to show up.
No problem. Next time, just @ me.
Going to just unfollow you. Three years of non stop complaining is exhausting.
I will pay someone 2000 sats to explain just what the hell is going on here.
Angry people that have been butthurt for years because they think they're being excluded, when no one is excluded them. They just like to feel that way to use their own perceived rejections to fuel their own development. It's a terrible way to live and work, but it's what they do. If you think you're the underdog, you'll work harder I guess? But the kicker is that all of us here are the underdogs 😂
Uh……unless nostrhub has completely changed since last fall, the principle behind it is very meta —- effectively Its decentralizing nostr nips across the nostr network
You use nostrhub or any fork of it to publish custom nips across any set of Relays to promote your custom nip. People can up vote your proposal and last i checked Comment or zap a nip proposal
You can also fork it and use it anyway you want.
This is a newer version, with a preset "meritocracy" list filtering the landing page and discussions. Some of the people on the list didn't know they were on the list and some of them are barely active anymore, but they are from the GitHub repo. You can change to your own preferred "experts" or simply delete them all, but changing it only effects what _you_ see. Everyone else unwittingly sees the filtered version. (You also have to manually change the settings to include your own relay list.)
The idea of porting the NIPs to Nostr is largely mine. That's why so many NIPs have been available on the wiki 30818s, since early 2024. Our own specs were stuck in permanent PR on GitHub, so we eventually gave up and moved them over to Nostr, as well. That is why they are listed on the GitHub kind list, but the link goes to wiki events. And that is why they have NKBIP-11 identifiers, instead of NIP-11 identifiers. They told us at the time that the number of NIPs is hard-capped to 2 digits, so that they didn't have any free numbers to give us, but that they could add us to the kind list to prevent kind number collisions. After we gave up and closed our PRs, they merged NIP-A1. Okay.
Then someone (Alex?) came up with a new "wiki spec" kind 30817 and republished them all there. My client has generic cards, for unknown kinds, so I could see the activity and figured out that there was a new wiki kind. I started republishing our specs to that kind and implemented it in my own app. I didn't know about the new filter on their client, at first. I overlooked the change. I was just confused by the stuff I was seeing and not seeing, as it was suddenly less relevant to me, and started fiddling with the settings.
We have lost so many new devs, struggling to publish specs someplace someone might see them and get constructive feedback. This seems like a step backward, to me, and it's a bit depressing to see. But it's not my app. I'm pointing out that there are now alternative apps. I hope the number of apps rendering this kind grows, so that the protocol remains welcoming to independent developers.
affects, not effects
All that text and you grammar nazi'd affect/effect?
I've occasionally been called the Heinrich Himmler of grammar.