a few months ago my access to the NIPs repo was removed without any notice.

as someone who has been here before the hype and have developed a good amount of the standards and infra here, it’s pretty disheartening to see Nostr turn into the messy “ecosystem” (if you can even call it that anymore) that it is now

I am most likely going to begin making my own group of standards, the “standardize before implementation” approach never works with NIPs anymore with them being stuck in review limbo alongside reviewers trying to impose their extremely narrow views on how they think Nostr should be

Reply to this note

Please Login to reply.

Discussion

Every dev has this thing of building their own standards. Then they realize their stuff doesn't work unless they implement what others do.

That doesn’t mean I have to put my standards in the NIPs repo. Amethyst for example implements several Damus specs that are not NIPs and somehow it still works.

By luck probably. Because I don't follow what happens on Damus specs.

So we just host our own nips repo then? I already run a mirror. I'll merge your patches XD

Yes.

These will contain proposals like my Nostr Login proposal, moderation and translation service interfaces, request cursors and a bunch of other things I will implement on my own Nostr services and that others would benefit from also implementing.

Vendor specific details if they were to exist would be in another folder.

you can write your nip on nostr https://nostrhub.io/

🤞

You can just have your own nips repo 😄

i'm interested in discussing the finer points of any proposals you make. i also have my own designs that i'm working on. you saw my first draft http api, i'm refining it now and will have subscriptions implemented probably eod tomorrow. uses a single listener for the client with a relay assigend ID and then subscribe/unsubscribe methods to activate/deactivate filters on the listener.

i don't really care that much to discuss issues around message types. i think you know i'm opposed to the whole kinds field altogether for the same reason as i oppose the numbered nips. i think document types should follow the HTTP standart.

btw, you posted this note to wss://realy.mleku.dev

i'm pretty sure you are still muting me so whatever.

also, lol. you posted to my relay, while muting me.