New version. Got #pomegranate login to work, so you can now use those bunkers with my app, along with standard bunkers and Amber. https://zapstore.dev/apps/naddr1qqgk2afwd9khwctvvshxzmnywfhkjeqprpmhxue69uhhyetvv9uju7npwpehgmmjv5hxgetkqgs06gywary09qmcp2249ztwfq3ue8wxhl2yyp3c39thzp55plvj0sgrqsqqqlstude5pk

Okay, this is genuinely good. So smooth and intuitive. So happy to use it. Yes, I spent another entire day working on a client only I use and it was wonderful. 🥰 https://zapstore.dev/apps/naddr1qqgk2afwd9khwctvvshxzmnywfhkjeqprpmhxue69uhhyetvv9uju7npwpehgmmjv5hxgetkqgs06gywary09qmcp2249ztwfq3ue8wxhl2yyp3c39thzp55plvj0sgrqsqqqlstude5pk

Abandon MLS at your own peril. Now, you can't say nobody ever warned you. I just warned you.

Anyone keeping track of Black Forest Labs #AI project?

Bro, everyone blocks me.

Which attacks? Did I miss some news?

My main problem with hardware wallets is the social risk. If you order one, everyone knows you have put crypto on it. An old laptop, tablet, or cell phone is just an old, general-purpose computer. Biggest risk is that someone throws it away.

I think anyone suing Cold Card has a good case, even merely based on the audits that have already been performed. There is nothing at all normal about how this stuff was built. Outrageous, irresponsible behavior and open contempt for the customers, IMO. Their best bet is probably to claim that they were all taking hallucinogenic drugs while working; _it is that bad_. And it just keeps getting worse. Every time there is a scandal like this, I am left staring in shock at how bad it all is, as I can't imagine anyone actually being this grotesquely bad. It's completely outside my frame of reference. **This is the shit you get when developers don't stay humble. This is the shit you get when nepotism is rife.**

The keygen for all of the libraries I have used draw full 256-bit values from OS CSPRNGs. Code audited: # JavaScript / TypeScript * nostr-tools (versions 2.15 – 2.23.5) * @nostr/tools 2.20.0 (the JSR-published variant of nostr-tools) * @nostr-dev-kit/ndk 2.14.35 (+ ndk-cache-dexie) * @contextvm/sdk —(ContextVM signer, wraps nostr-tools) # Go * go-nostr (nbd-wtf) (v0.27.0, notably older) # Kotlin / JVM * no Nostr library; direct implementation on top of ACINQ secp256k1-kmp 0.17.3 (plus BouncyCastle in the Android app) # Elixir * no Nostr library; implements on top of lib_secp256k1 0.7.1 # PHP * swentel/nostr-php 1.9.4 (server side; pulls in elliptic-php) # Python * python-nostr

Looks like it's getting gamed pretty hard

I can't stop thinking about the fact that I could have vibe-coded the firmware with my Cursor ultra account in a couple of days. And it would have been more secure. And it would have been written in C. And the tests would have prevented this error. *This was human slop.*

I could run one, yeah. More than one would be a bad idea, as it would recentralize the shards.

I use Python for parsers. 😐

You mean the git? Here is a mirror: https://git.imwald.eu/silberengel/pomegranate

The relay is shutting down, not the app.

I'm adding support for this and will launch a coordinator. I was about to add a #cordn coordinator, so I'll just do both at once. I already support bunker, but my app is specialized in flaky Internet connections, so what I need to do is add queued signing to the queued publishing, since the signers are all online. Shouldn't be too bad.

Have you seen this, ? Bunker sharding. Interesting concept.

https://cordn.net/