TIL hardware RNG works by edging the circuit millions of times per second and then checking whether or not it goons.

Don't bite the hand that eats you.

I have been forced to finally master Nostr SQLite. I started on SQLite, hit walls, moved to Postgres, hit further walls, and finally landed on ElasticSearch/OpenSearch with infinite scalability. But now I am forced to finally master SQLite for local database on Android/iOS. I've built 4 different variations of Nostr SQLite and I'm benchmarking them against each other. The current fastest implementation (for reads) stores tags in an FTS table like "t:hello e:abc123..." The naive way is to keep a separate nostr_tags table and JOIN it, but then the query planner behaves wrong. This way has 25x read performance for 100k+ datasets.

No imagination, you've completely missed the point

New client trends just dropped

Selling all my Bitcoin to buy Pokemon cards. It's an investment.

I'm building a Nostr-based operating system. Yes, like one you install on your whole computer. :trillian-drunk:

On mostr.pub you can claim a username now. Then your Nostr account will show up as @mostr.pub on Mastadon.

I downloaded the Claude models in Shakespeare AI to 4.x because the newer models are trying way too hard. I want to replace these with open source models once I have time to test them with Shakespeare.

Groundbreaking

Ditto Relay lets you AUTH as either the sender or receiver to view. But to delete you have to be the receiver. This is the biggest source of dissonance in the theory, I think. But it's not too bad. It's a weird triangle shape of requirements.

Ahhh yeah... okay I do see it contradicts my position. We AUTH from the sender. It's not perfect.

But yes you just AUTH with the Concord key to get the Concord stream.

>but relays that already protected DMs, have to turn that off or they can't serve concord groups. This is not true. relay.ditto.pub gates giftwraps and nip04 DMs with AUTH. If you're in a Concord channel you hold the private key to the channel, so you just AUTH to it. It already works. Concord is perfectly compatible with NIP-17 relays except that NIP-17 doesn't explicitly state that the author shouldn't be allowed to delete. But it does say that the author should essentially throw away the key and that the recipient should be allowed to delete, so it's easy to argue that compliant NIP-17 relays _should_ prevent deletion by the author.