Define the problem, first.

I doubt most of the people getting excited about this even bothered to read how it works. It's a software quality nightmare, in my opinion, as it adds asynchronous transactions, architectural and code complexity, an entire network of servers with redundant (but potentially inconsistent) data, etc.

Relays on top of mints on top of lightning nodes on top of Bitcoin nodes, and always tied to your npub. (Theoretically, you could tie it to a different npub, but that would be completely retarded, as the whole idea is that people are zapping your npub. And forget trying to use the same zap wallet with multiple different npubs.)

Even worse than e-cash wallets on top of mints on top of lightning nodes on top of Bitcoin nodes, which is already a transaction maze that takes occasional money-loss for granted.

1. Relays can't even get follow-lists right, as they are only eventually consistent.

2. Mints can just walk off with the money. They are wildcat banks that can disappear from one moment to the next.

3. Your financial information gets passed around to wallets from developers you might not trust to deliver the quality required for banking services. As far as I can tell, you get auto-logged into their wallet, as soon as you make the mistake of trying out their app.

Every time people around here try to obfuscate novel architecture too hard, rather than putting the effort into making the connections smoother and explaining/guiding better with something like a wizard, it ends up looking like something that's a preface to the next edition of "Software Disasters".

Hard pass.

Nothing is fixed until the state is unable to tax its citizens.

Yes. Its 2 reproductive strategies a male could make.

Essentially Andrew Tate V.S. a Amish Chad.

What is better? To be rich and have many babies with many young women (all under 25)? But you cant give much focus to each child. Or be slightly above average in wealth, have a ton of babies with one woman (from age 20 to 45), where you can give each one lots of attention?

There will be steins

Tell me blunt truths. Hurt me. Destroy me. Make me look in the mirror with horror upon myself.

If what you say is true, I can be rebuilt, anew, better, bulletproof. With hard truths as my base layer rather than comfortable lies.

The question is, are you worthy of being believed?

If he can fix some of the obesity that would be great

Took a year and cost 450k.

What the hell is this in my kitchen 😳

Anyone?

What the hell is this in my kitchen 😳

Anyone?

GM! Do you believe it's a risk factor?

#bitcoin #mstr #memes

Be yourself even if you are different 🫂

If your email has been widely shared, it's likely already available on the dark web. The real security risk isn't just email exposure and spam—it's the common practice of reusing the same email-password combination across multiple services.

When a single service is breached (like a retailer or streaming platform), threat actors combine your exposed credentials with other leaked data, creating comprehensive profiles. One breach now compromises all accounts sharing those credentials.

Best practice is maintaining dedicated front-facing emails for official business (some sites don't allow alias emails), while using unique email aliases and high-entropy passwords for every other service. Services like SimpleLogin (included with Proton) allow you to easily generate a unique email alias for each individual account.

This compartmentalizes risk—if one service is compromised, others remain secure, and if an alias service fails, your primary email remains functional for critical communications. All of this can be stored in an open-source, independently security audited password manager that is either local on an air-gapped device (one that never connects to the Internet) like KeePass, or that uses cloud sync for greater convenience like Proton Pass/Bitwarden.