mircea_popescu: http://trilema.com/2016/the-necessary-prerequisite-for-any-change-to-the-bitcoin-protocol/#comment-116390 << incredibly enough everyone thinks this is a really original and interesting idea.

mircea_popescu: "all 1 comments - sorted by: best there doesn't seem to be anything here" << lol reddit.

mircea_popescu: funkenstein_ <-- afaik the only ways are 1) require coinbase receiver's signature in block header << this is rank nonsense. i'm not signing to receive bitcoin.

mircea_popescu: polarbeard http://104.131.72.249/patches/polarbeard_better_log_messages#selection-8295.32-8295.60 < plox no ' in loglines so people don't have to escape the shit out of parsing.

mircea_popescu: anyway, dbenv.set_lg_max(1000000); < wut ?

mircea_popescu: http://log.bitcoin-assets.com/?date=01-02-2016#1392451 << it's readable in the sense every other contemporary industrial process is "machineable" or "approachable" or whatever. with heavy equipment, not with bare hands and eyes. ☝︎

mircea_popescu: http://log.bitcoin-assets.com/?date=01-02-2016#1392335 << poverty limit. ask the world bank :D ☝︎☟︎☟︎

mircea_popescu: http://log.bitcoin-assets.com/?date=01-02-2016#1392316 << i do. ☝︎

mircea_popescu: http://log.bitcoin-assets.com/?date=01-02-2016#1392285 << i should hope these were the same "trained specialists" that started the wholly hallucinated "family abuse" moral panic of the 90s. ☝︎

mircea_popescu: <felipelalli> mircea_popescu, I know that you think expire a key is a bad idea. I saw you saying that in MPEx FAQ. But why? Could you elaborate more about that? Isn't that useful in case someone dies or lost the control over the key? << how is a bitfield in the gpg key help you in case you die ? or lose control of the key ? neither of these are time-able events.

mircea_popescu: phf> doing by the book kahn topo sort on my graph results in topo a b c d e so pressing to c drops the whole d e subgraph << this is correct.

mircea_popescu: ben_vulpes https://archive.is/TtMr6#selection-83.9-83.27 < what's this select ?

mircea_popescu: "riously, so the girl won't fuck because she figures you don't value her if she" << on my system

mircea_popescu: mod6 weather it is `high' or `low'. <

mircea_popescu: ``heathen command'' << am i the only one seeing a weird set of unmatching quotes here ?

mircea_popescu: http://log.bitcoin-assets.com/?date=31-01-2016#1391802 << thinking about it i think you';re right actually. ☝︎

mircea_popescu: http://log.bitcoin-assets.com/?date=31-01-2016#1391794 << yeah but i meant, before it goes in, not after. after yes it does, and it's very nice. ☝︎

mircea_popescu: http://log.bitcoin-assets.com/?date=31-01-2016#1391760 << if your sig expired it may be that deedbot will still see the expired one until it updates. if it ever does. ☝︎

mircea_popescu: http://log.bitcoin-assets.com/?date=31-01-2016#1391737 <<< aaaahahahaha ☝︎

mircea_popescu: http://log.bitcoin-assets.com/?date=31-01-2016#1391704 << yeah that's the idea, but we specifically dun want to say "trust x thing" in the imperative. ☝︎

mircea_popescu: http://104.131.72.249/patches/mod6_fix_dumpblock_params << this is rapidly becoming very sweet. mind adding the select javascript too ? :D

mircea_popescu: <adlai> if "standards" is plural, it's already noncompliant <<< for the record, the reason the enemy uses the plural there isn't that the enemy is this stupid, but that it believes in patchwork. ie, standards : one for this, one for that, together they make up a complete thing.

mircea_popescu: http://log.bitcoin-assets.com/?date=31-01-2016#1391311 << word eh. ☝︎

mircea_popescu: http://104.131.72.249/patches/asciilifeform-programmable-versionstring-fix << really should include a "touched signatures : " list

mircea_popescu: http://log.bitcoin-assets.com/?date=31-01-2016#1391302 <<< dawg simmer down, it's not like jurov wrote it with the express purpose of aggravating you. ☝︎

mircea_popescu: <mod6> or 3 << asciilifeform 3