-
@ mleku
2025-02-25 16:19:02
i see, and where did these documents that get compiled into the collection of specs come from in the first place then?
i already explain it in https://protocol.realy.lol - the apps should contain the spec they are working towards, and if other want to interop with that app (relay or client) they should read that spec, copy it to their repo and implement it
the nips repo is the wrong way to do it, at minimum it should be a wiki, and navigating the "unratified" proposals should be easy
that's not what PRs are for, they are very specific and narrow things and without a welcome mat to point people the way to these proposals nobody is actually joining the discussion, nobody even sees them
the number of times i have had to ask people for the PR link for not yet existing nip numbers i have lost count
if you are serious about making this community work, and you should be, since apparently you are some kind of leader, then you also want it to be easier to discuss new API methods
and that alone is part of the problem, you are in denial about what they are, they are API methods, and this is why nip-11 is a total mess and why almost no clients actually request these, or if they do' they don't seem to understand them, like nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn 's client clearly doesn't comprehend the idea of nip-42 demand to auth for specific reasons but generally not, and nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr his app also doesn't understand auth for specific reasons
reasons like, you know, protecting the fucking users privacy