The below is an off-site archive of all tweets posted by @lopp ever

August 20th, 2015

@mikestable The highly endangered native Durham straightened weave.

via Twitter for Android in reply to mikestable

@mikestable Found some roadkill today in my neighborhood pic.twitter.com/vPiSe8ILdf

via Twitter for Android

@EdmundCMoy Agreed: “Bitcoin will still exist no matter what happens”

via Twitter Web Client in reply to EdmundCMoy

@MortuusBestia @sneakdotberlin @jonmatonis @robustus @oleganza Hear him out, maybe he knows how to fix that problem in humans.

via Twitter Web Client in reply to MortuusBestia

@jonmatonis @sneakdotberlin @robustus @oleganza *shrugs* you say “coup,” I say “competition in the marketplace of ideas.”

via Twitter Web Client in reply to jonmatonis

@jonmatonis @sneakdotberlin @robustus @oleganza IMO HODLing is the safest action in the event of a fork since your coins are on both chains.

via Twitter Web Client in reply to jonmatonis

@sneakdotberlin @robustus @oleganza It may very well fail to trigger. Though I seriously doubt it will be the last attempt at a fork, ever.

via Twitter Web Client in reply to sneakdotberlin

@sneakdotberlin @robustus @oleganza Seems like a “freedom vs safety” trade-off to me. You can’t stop people from trying in a free market.

via Twitter Web Client in reply to sneakdotberlin

@sneakdotberlin @robustus @oleganza I don’t see how that can be the case when anyone can fork the code and propose their own improvements.

via Twitter Web Client in reply to sneakdotberlin

@sneakdotberlin @robustus @oleganza No one holds a monopoly on development of the Bitcoin protocol; at best one can BDFL an implementation.

via Twitter Web Client in reply to sneakdotberlin

@robustus @sneakdotberlin @oleganza Yes, there’s even a config switch for it that requires no code changes: “disableippro”

via Twitter Web Client in reply to robustus

@muneeb It’s tricky because Bitcoin at its core is ideology - we’re just trying to represent it with computer code.

via Twitter Web Client in reply to muneeb

One interesting facet of the block size / fork debate is the revealing of which well respected developers resort to character assassination.

via Twitter Web Client

@oleganza To be clear, this doesn’t actually track both chains yet, right?

via Twitter Web Client in reply to oleganza

@oleganza If you’re vehemently against the resource prioritization code, you can disable it with the “disableippro” switch.

via Twitter Web Client in reply to oleganza

@sneakdotberlin @oleganza If you want to be accurate, link to the full code. It only executes if node is attacked. github.com/bitcoinxt/bitc…

via Twitter Web Client in reply to sneakdotberlin

@btcdrak Yes, thank you for contributing to proving my statement. Slush miners get to choose which block version to mine.

via Twitter Web Client in reply to btcdrak

The power to arbitrarily regulate is also the power to sell exemptions from the harm resulting from said regulations.

via Twitter for Android

Someone needs a better fact checker. Slush is operating 2 pools; second BIP101 block is blockchain.info/block/00000000… twitter.com/btcdrak/status…

via Twitter Web Client

spair We support the adoption of BIP 101 for increasing ’s limit @BitPay medium.com/@spair/increas…

via Twitter Web Client (retweeted on 7:36 AM, Aug 20th, 2015 via Twitter Web Client)

@Datavetaren *waves magic wand* LIGHTNING NETWORK - ALAKAZAAM!

via Twitter Web Client in reply to Datavetaren