Avatar
1F52B
1f52b16e5ca201ef2dc030f9b651137672e52de1ab29c0b0f6b72ac80ab23c84
đŸ”« | Shitposting | #Bitcoin

My biggest objection to the new eCash implementations atop of Bitcoin is that they carry *both* self custody risk and second-party custody risk

Lose your eCash wallet or backups, money gone

eCash issuer (bank) decides to run away with actual Bitcoin, also money gone

(Dumb qn) How does that work for sending the right payment amount? If you send an ecash it has a fixed amount right, so do you get a new one back as change?

Or when initially paying the LN invoice do you get a ton of worth-one-request ecash tokens back?

Any Advancing Bitcoin-ers going to the Real Bedford game today?

(Tagging #[0] because the pirates đŸŽâ€â˜ ïž don’t seem to be on Nostr (yet))

Argh, why is setting up LUKS+btrfs such a pain in the ass on Debian but a breeze on Fedora!

Anyone got a good guide for doing it? Seems like you’ve got to manually poke around in the shell or jump around the installer to get it to play ball đŸ˜«

Want to play with #[0] on a spare machine, but IMHO disk encryption is a must and btrfs snapshots make backups easy

If you want shitcoiners to be interested you need a new pointless token to pump 🙄

They genuinely seem to lose interest quickly if there’s not a “how do I get rich quick” angle

I don’t think that’s true, I successfully swept the funds I had in BW’s custodial Lightning yesterday (a whopping 35 sats 😂)

You have to remember to account for a fee, so I had 35 sats but invoiced myself 34, paying a 1sat fee. Annoyingly you can only guess what the fee will actually be and try again if you guessed too low, but 1sat is common.

Potentially they’ve got some channels that need rebalancing before they work properly again, given their flows will now be mostly outbound

Coinbase have been shitcoiners and smoothbrain big-blockers for a while now 😂

Point of Sale UI? (Think it’s great to have in Breez)

Ah actually the higher-end Optiplex Micros (5000 series) do have two M.2 slots for SSDs and still have one SATA, though they’re a bit more expensive

Yes, one SATA port and one M.2 internally. Ideally you’d want matching (like two M.2 drives) but it’ll still work fine in btrfs/RAID

Proof of steak (đŸ‡«đŸ‡· Edition)

I’d also be interested if the thing we’ve ‘discovered’ about segwit and taproot after the fact (inscriptions
) have changed attitudes against ‘cool but very complicated so few understand’ changes in core

IMO it should continuously get harder and harder to change core, to the point that only changes that avoid catastrophic badness can get in (I mean Consensus, Standardness, not QT UI fixes)

Current FUD from MSM about how ‘small number of devs can just change the code’ and presumably they think we’ll all upgrade
 but would be good to have a solid discussion on why that’s not the case, and what core devs can do easily via what’s very hard for them to do without consensus

Don’t treat DMs as particularly secure, they’re pretty simple an don’t have many of the good properties that existing E2EE messaging alternatives like Telegram/Signal/WhatsApp have (ratcheting keys, key exchange between two parties, etc.)

You leak your nsec and all your past DMs are readable and you’re easily impersonated. Also everyone can just see who you’re messaging and when, even if they can’t read it (because the DMs are jus events published to your relays like normal posts)