Repeat after me:

"I'm not a Formula1 driver, I don't need a tacky racing chair. I promise to get a proper office chair with lumbar support and adjustable head & arm rests. I will save some money and will also look less ridiculous in front of my PC."

See, it wasn't that hard!

This is a really good (and entirely non-technical, for those who glaze over at equations) summary of a very thorny issue: repudiability in digital communications (it's technically only about DKIM, but the points made apply to other protocols than email).

I think I do agree with the conclusions, but it's something that isn't always so clear (how useful *in reality* are protocols like OTR, for example?)



Is it just me or are golang interfaces really confusing? I get it that it's low ceremony not having to declare the interface a type is using, but when reading code that is not your own (or that's old enough to be forgotten about entirely) it's just a pain in the butt. I'm constantly off on little puzzle tours finding interfaces that may or may not satisfy a signature.

Mind blown, I never realized this coincidence:

You can use the next number in the Fibonacci sequence (1 1 2 3 5 8 13 21 34) to convert from miles to kilometers.

For example, 13 miles is 21 kilometers.


I wrote a post on my debugging setup for LND.

Interested in how other people did this. I couldn't find much about this, so I had to figure most of this stuff out by myself.

@fribbledom You are my 1st follower! To what do I owe that pleasure?
En spreek je echt Nederlands?

"We didn't call it fuzzing back in the 1950s, but it was our standard practice to test programs by inputting decks of punch cards taken from the trash.

We also used decks of random number punch cards. We weren't networked in those days, so we weren't much worried about security, but our random/trash decks often turned up undesirable behavior.

Every programmer I knew used the trash-deck technique."

-- Gerald M. Weinberg

Bitcoin Mastodon

Bitcoin Maston Instance