Nostr Web Client

Interesting write up

Agreed. Though if I'm being perfectly honest, the approach of "everything is insecure, so I should build my own tools - they'll be more secure!" can be an anti-pattern in the wrong hands. I don't know enough about nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 or his work to say, but it's a very minor alarm bell.

Sometimes the whole ecosystem is improved more by talented and motivated individuals contributing to exiting projects that need help in the areas those individuals identify as weak points.

Reply to this note

Please Login to reply.

Discussion

The Fishcake (nostr.build) 2mo ago

I tried to find clean and compliant libs for swift, just to end up writing my own on top of the standard libsecp256k1 instead of gluing together all the slop

ChipTuner 2mo ago 💬 1

This project doesn't already exist. Noscrypt was built so that others (including myself) are re-rolling their own nip44 crypto every time they want to create a messaging app. In the case of noscrypt the goal is to be as ubiquitous as openssl. Which btw, noscrypt is not hand-rolled, have a look.

Yes there is a judgement cast on "Im smarter and I can build it better" I don't have a good argument to that, it is what it is. My attempt was naivley was to help prevent that. Noscrypt is an "old" project relatively speaking, it is the existing project.

ChipTuner 2mo ago 💬 1

I'll spare my soapbox of a the mono-language/high-level culture language speech, but there is a reason noscrypt is written in a systems language and believe this is the only correct way to be implemented.

vinney...axkl 2mo ago

I totally agree with you.