This approach is fine, I just wouldn't push it to production. The draft nip I wrote helped me think through what I wanted. I have already implemented nip 87, but in doing so found some problems. It's on ice until NIP 44 gets merged, at which point I want to fix the issues I found, and maybe walk things back to trusting relays to do some auth.
There isn't a NIP yet.
My methodology is to get UX right first, the implementation can be changed later. The problem with writing a NIP up front is that the design was changing during our implementation. Reviewing a NIP without real software to try out slows the whole community down. Writing a NIP after implementation also means now we understand much deeper about the problem. The NIP later on will be better quality.
nostr:nprofile1qqsverg89m7ucem0ewkpfakddqj7ms6hde27k7r292t4acp556szdjcpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqscamnwvaz7tmzwf3zu6t0g2ep0q will write a NIP or at least that's what she proposed during the meeting LOL.
nostr:nprofile1qqs2mvf775w8q882vwuza4ql22yr387yq50ppvfup0l6wlnav8yed0gpr4mhxue69uhhyetvv9ujumn0wd68ytnhd9ex2erwv46zu6nsqyxhwumn8ghj7mn0wvhxcmmvqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsxwfdau still needs to finish up some UI. But the logic is already in the production, we just hide the UI.
The plan is to release this feature for testing by the end of Friday and then Sherry or I will draft a NIP.
If we are productive, we can release it on Wednsday.
Discussion
No replies yet.