Replying to Avatar Luxas

Some valid claims here. Thanks for sharing. I do know that they briefly touch on eventually encrypting the notes, listed at the bottom of NIP-57 spec: https://github.com/nostr-protocol/nips/blob/master/57.md

I'm sure it will happen eventually, for some of the reasons you've outlined. For now, I think the easiest solution here is practicing good OpSec hygiene and limiting your exposure by using LN wallets that only hold a small amount for zapping.

And maybe look at expanding on NIP-57 by submitting a PR to add the encryption of zap request notes?

If I step foot into the world of GitHub again. It would be going against my core beliefs. Which is something I wont do. Otherwise I could not forgive myself for contributing to their success.

If Nostr developers ever move away from github. Start acting ethically responsible and move over to codeburg, notabug, or literally almost anywhere else. I would be all over it like white on rice on a paper plate in a snow storm.

Also, I do not have the time and dedication required to personally take on this epic huge responsibility. Too many projects going on right now to claw my way out of personal poverty. As well as many demanding responsibilities. I am simply stretched way too thin right now. Just trying to survive without a stable income.

When I asked the nostr community if I should expose a dire privacy and security flaw in the protocol. The people said yes. So I needed to do a brain dump that motivated developers blessed with passion, free time, and the ability to save nostr. Thus the nip 80085 proposal was literally born from a hold my beer moment.

The best I can do is create awareness. Hoping for another true hero to come to our aid. To save nostr by finishing the work I started.

Many people are either lazy fucks, and/or have short attention spans. They always seem interested, but when I show them. I either get no response, or a TLDR. So sincerely I am appreciative that you actually read it. Then took the time to give a thoughtful response.

Reply to this note

Please Login to reply.

Discussion

No replies yet.