14700+ entries in 0.137s
phf:
http://btcbase.org/log/2018-05-22#1816718 << hah, i originally watched it for the same reason, and the only thing i even remember is burroughs sitting in the chair, and spitting the "narcotics" prediction in his famous squeaky voice
☝︎☟︎ mircea_popescu:
http://btcbase.org/log/2018-05-22#1816908 << i'll point something out, in the vein of the previous "tripartite idiocy" discussion : law enforcement consists of very minimal work, and even less useful work these days. you know those century-old complicated "murder investigations", with barry fitzgerald going "tis a heavy case" and so on ? NONE of that still exist ; the line-ups to pick up suspects are mostly gone, etcetera. la
☝︎ mircea_popescu: the trucks dun move until the money is in, definitely. and so that's the point here, peeling more and ever more layers off. when we send bitcoin, we're sending something > trucks of lcd panels, not something
< vogue magazine.
trinque: "(b) la infracción a los derechos de propiedad intelectual e industrial"
<< so no seedboxen eh?
☟︎ deedbot: Invoiced ben_vulpes 0.36662881
<< May 2018 refueling: 36 w.u. fee from BB refuel ( omitted from prev inv ) + 2934.06 latech co. + 50 wr.fee
spyked:
http://btcbase.org/log/2018-05-22#1816456 <-- hey, neat archeologgy! may I persuade you to reflow the preformatted content somehow (replace pre with blockquote or something else)? it's a pita to read long log lines on 80 column setups.
☝︎ deedbot: asciilifeform rated Mocky 1
<< 'why ada'
a111: Logged on 2018-05-21 16:55 phf:
http://btcbase.org/log/2018-05-20#1815927 << i'll take a look, i had further comments about diana_coman's original spec and the responses, but does this new spec replaces the other one entirely?
lobbesbot: ben_vulpes: Sent 22 hours and 13 minutes ago:
<asciilifeform> is there a problem with the invoice ? ( aside from the fact that i forgot the 36 usd fee , in it ) ? how come i'm still waiting ?
a111: Logged on 2018-01-09 18:56 a111: Logged on 2017-01-15 23:05 a111: Logged on 2017-01-15 21:47 indiancandy: !!register
<だ댧卾ᅟ룱ࢤ�ᫎ䂳䯫证慢ቊ콥贐较本덁㡚࠘譂ꘪ蜈出ᜄ粘锝⛥箥戴ᷜꔐ俟组․ഒ㻒㌕낌ᥥ款ړ忲䧚뾨շ脵됾쓰娊嫥៏䙿槥晥获᷑룜巵歛踈>
a111: Logged on 2018-01-09 20:29 asciilifeform: in other oldies, seiko's 'DPU414' thermal printer, can be had for
<fiddybux, and not only prints 80cols x infinity (continuous tape) but knows how to eat rs232 and... print hexdump (up to 19200 baud)
BingoBoingo:
<asciilifeform> 'AmRRON Dark Labs, a type of Skunk Works for the Patriot community, has built a machine...' blah
<< LOL, FBI-otron in the wild!
a111: Logged on 2018-05-21 16:34 phf:
http://btcbase.org/log/2018-05-21#1816308 << is there any need for that alternative? from my research static inline is one of the few behavioral commonalities between c99 and pre-c99. it also supposedly works across different compilers, etc.
spyked:
http://btcbase.org/log/2018-05-21#1816325 <-- it's not needed, at least not in the case of vtools. it may have been worth it if it had reduced binary size, but from my experiment it makes no difference. gcc seems to remove the definitions of static-inlined functions (after inlining them), but I don't really know if it does that in general.
☝︎ phf:
http://btcbase.org/log/2018-05-21#1816308 << is there any need for that alternative? from my research static inline is one of the few behavioral commonalities between c99 and pre-c99. it also supposedly works across different compilers, etc.
☝︎☟︎ spyked: it might also in a way be interesting to report how I stumbled upon this: I tried to recompile gnupg-1.4.10 on my broken debian system and got the same "multiple definition" linking errors as in vtools' case (though I *did* use gcc
<5). so I dug and found the usual kochs "fixing" things to compile gnupg on newer gccs.
☟︎ deedbot: mircea_popescu rated Mocky 2 at 2018/05/03 19:07:05
<< remarkably mentally organized eulora noob.
mircea_popescu:
http://btcbase.org/log/2018-05-20#1816079 << i expect. you should see these idiots, biking with no lights, dressed in camuflage gear (srsly dorky, black shit because white's too hard to wash, still see no reason you shouldn't be out at night ?) on the side of the fucking highway. what, problem ?
☝︎ lobbes:
http://btcbase.org/log/2018-05-20#1815918 << It actually never occured to me to use the "many OTPs stored for later use" trick that trinque mentioned, which is pretty spiffy indeed (I may start doing just this). But to answer your question: lobbesbot's only involvement in my archive process is to listen to irc and insert urls it comes across into a sqlite3 db. That database is then 'shipped off' to separ
☝︎ danielpbarron: i think the only change i made there is
<code> to
<pre> on the gpg thing
mircea_popescu:
http://btcbase.org/log/2018-05-20#1815997 << that's the whole point ; ~however~ the thinking is that the user should be warned (and pressing should stop) if there are invalid signatures in his .seals dir, ~because~ it is not expected he'd have put them there, so something needs humnan eyes.
☝︎ scriba: Logged on 2016-10-24: [16:27:02]
<mircea_popescu> these and other tips and tricks brought to you by red hat entreprise security department.
a111: Logged on 2016-10-24 19:19 hanbot:
http://log.mkj.lt/trilema/20161024/#103 << i was actually gonna check out some "linux chix" meeting at the local red hat hole when i noticed 'pre-registration with documento' was required, you know, for 'security'.