Tweets by @lopp / May 19th, 2016

@mryanbrown @socrates1024 @phonikg It can’t be that bad - there are so many of them! ðŸ˜ https://t.co/lkFG1J61l3

@ollekullberg @twitter Unfortunately my articles tend to end up over 10 pages, so I can’t write that many of them…

“Have fun trying to write 140 character statements that aren’t open to misinterpretation!” - @twitter

@kristovatlas @oxt_btc Consider switching to satoshis / byte for readability?

oxt_btc Do you pay too much for your small transactions ? #StaticFee #Bitcoin pic.twitter.com/YkiKdM3UTK

@TuurDemeester Folks flee safety of BTC for wild west ETH frontier! cryptowat.ch/kraken/ethbtc

We’ll know fee rate calculations are fixed when bytes chart spikes don’t correspond to fee / byte chart crevasses: https://t.co/y4QDDzKpMa

If @projectfi would just adapt @gmail’s spam filter into its voicemail system, it would be a real time saver. I’ll happily report VM spam…

If you liked it then you shoulda put an alert on it.

@kristovatlas Or spell checking in general? Seems like I make a lot of PRs just to fix spelling mistakes… pic.twitter.com/aXO4x1tQUM

@acityinohio For those special occasions when you’re counting atoms or extrapolating a series until the heat death of the universe.

Fun fact: Ethereum Virtual Machine uses 256bit integers & requires 256bit arithmetic. Most CPUs are <= 64 bits. https://t.co/FVJvhndVdv

@kristovatlas I’m thinking if users want the freedom to make dangerous decisions, they should have to acknowledge that they do so knowingly.

@kristovatlas Yeah, there was one who set the fee to 0 long ago and then forgot about it. I think extra safeguards when sending could help.

Wallets should check their default settings. @ElectrumWallet has supported dynamic fees for 9 months - why isn’t it enabled by default?!?

I recommend wallets stop allowing users to shoot themselves in the foot by overriding recommended fees and spending unconfirmed outputs.

Jameson Lopp (@lopp)