You are still lovely
It is a problem. As a developer who mostly focusing on DM, the problem is more than metadata leakage.
It's a square of
security & privacy
engineering complexity
user friendliness
decentralization
Some solutions solve No.1, keeps No.4 with a huge cost to No.2 & No.3
But I want to balance these 4.
Engineering Complexity is overlooked often but it is very important. Complex solution is hard to iterate/fix later on. It's harder to implement so that fewer developers implement it so it further harms decentralization.
Profile Search now supports pagination
NIP-42 is on roadmap. But I do have a question. Why don't we have stateless auth that authentication is embeded in each REQ? like
["REQ", "sub-id", "auth string", filter1, filter2]
NIP-42 is stateful
Build & Win
https://world.hey.com/dhh/developers-are-on-edge-4dfcf9c1
Here in Nostr, I am not worried. Sovereignty Engineering.
I just want to have wife and kids
NIP-07 is added back. If you are on mobile web, sorry that I am not focusing on mobile at the moment. In fact, I have to admit that my lack of mobile knowledge.
nostr:npub1dww6jgxykmkt7tqjqx985tg58dxlm7v83sa743578xa4j7zpe3hql6pdnf Can I only log in to blowater.app using my nsec? π€
Yes, it's a disappointing problem right now. I removed NIP-07 in the last release. I will add it back. The problem is that right now, all NIP-07 extensions that I am aware of does not support NIP-44 yet.
Actually, just checked, https://github.com/vitorpamplona/nips/blob/sealed-dms/07.md, NIP-07 should support NIP-44 now.
I will add it back in 3 hours.
Replace NIPS with smart-contract-like code valled validators
https://nomad.lacrypta.ar/documentation/validators
https://podtail.com/en/podcast/nostrovia-the-nostr-podcast/scripting-on-nostr-with-nomad/
Nostr FOMO is real
How is Coracle's NIP-44 implemented? Is it wrapped? Blowater is using NIP-44 without wrapping. Now no DMs are compatible beyond NIP-4. I don't know which way I should go.
I am currently leaning towards having dedicated relays to serve DMs so that meta data is not leaked just to unlock feature development.
Wrapping still feels kind of over engineered.
Nostr relay devs, I wish there is a set of standardized
["OK"] and ["NOTICE"] messages so that clients can show user proper error prompts when things go wrong
NIP-07 sign-in was removed due to some extensions hasn't implemented NIP-44 encryption yet.
Blowater now still decrypts NIP-4 events, but will encrypt all DMs with NIP-44.
Therefore, using a NIP-07 extension effectively breaks DM, at least for now.
This is a trade off that's painful to make.
Not much love is put into encrypted events in the community as a whole so that I decided to break some patterns to just unblock the product development.
A more secure design is welcome and I will work on it.