One of the big relays was throwing notices at the bot with a pow threshold, I decided to try it. It's using nostr-pow package thanks to nostr:npub1fzdvtqluxr8macqfthtndmzxg6864zcc0cc3lknzd8zwrq5ya5xq4yz4dv

That link doesn't support your case. PostgreSQL beat SQLite on every metric he tried. And he kept PostgreSQL's hands tied behind it's back by using only the intersection of features via an ORM and barely touching performance tweaks.

SQLite is a weird mutant. It is an RDBMS SQL database designed to be a persistence layer of a single application. It doesn't work as the former (not a server) nor is it well suited for the latter (kv databases work better as I have recently learned through experience). I think they did a great job of building the mutant to be the best mutant possible, but I don't see the use case anymore.

We have our first ever Cashu dev call today at 16:00 UTC – hit me up if you are a developer and you're interested in Cashu and would want to join.

It's going to be chill. We want to say hi, present different Cashu projects and there's going to be a presentation of how Pay-to-Pubkey works with ecash.

Very exciting! 🧡

Lazy DB usage. It can add up very quickly 🐶🐾😭

test again:

nostr:nrelay1qqdhwumn8ghj7mn0wd68ytndd94k2erfd3nk2u3wvdhk6tcqr3mhxue69uhkummnw3erytndd94k2erfd3nk2u3wvdhk6tckn0l55

Ah I wish we were hiring at Nos. Maybe in a couple months. There is a jobs board at DWeb camp, I will keep an eye out for anything that looks interesting and send it along (in 3 weeks).

Congrats, you are very talented and inspiring. Favorite project: Spotify Data Art 🧡

Of course brother ❤️ Your portfolio looks sensational 🔥

There is some bug where the thread pulling from relays blocks when you post. Balancing out the network threads and UI has been tricky.

I just ask GPT-4 to help improve DMs (NIP-04). Here are some ideas: 🐶🐾🫡

In terms of enhancing privacy and anonymity, the document already acknowledges that the current standard is not up to par with what's considered state-of-the-art in encrypted communication between peers. Here are some suggestions to improve privacy and anonymity:

1. **Use More Robust Encryption:** AES-256-CBC is secure, but AES-GCM or ChaCha20-Poly1305 are generally recommended for new applications as they provide authenticated encryption which protects not only confidentiality, but also the integrity of the data.

2. **Perfect Forward Secrecy (PFS):** The protocol currently reuses the shared secret for all messages. If a private key is compromised, all past communication is vulnerable. By introducing Perfect Forward Secrecy through ephemeral keys, even if a key is compromised, only the messages encrypted with that particular key would be vulnerable, not all past communication.

3. **Metadata Protection:** The protocol is currently leaking metadata. Techniques to minimize metadata include using a mix network, or dummy traffic to make traffic analysis more difficult.

4. **Layered Encryption:** For more privacy, consider implementing layered encryption (like in Tor). It could make tracking more difficult as the identity of the sender and recipient isn't known to the same node.

5. **Signature:** To ensure message integrity, consider signing the message with the sender's private key.

6. **Anonymous Identifiers:** Consider using anonymous identifiers instead of public keys. These identifiers could be rotated frequently to prevent tracking.

Remember, it's crucial to conduct a security audit of any cryptographic protocol before its application. Cryptography is very easy to get wrong, and small mistakes can lead to significant vulnerabilities.

hey #[4]​ what’s the status of your wrapped dm stuff? seems I cooked up a very similar idea on the couch last night 😂