918 entries in 0.163s
phf: jurov: so
http://www.eulorum.org/OS_X produces a working build, just not something you can upload as an archive, because the links between binaries rely on absolute paths. i think it's possible to go over all of them and replace absolute paths with relative paths using install_name_tool, but i haven't had a chance to try it yet. (just finished moving to DC yesterday, so i've been busy)
phf: oh hey i wrote a poc for pgp filter at toorcon, when that other wifi mitm came out. no need to figure out what's where, just sit on the
http stream, catch text/*, grep it for gpg headers, and then rewrite on the fly
phf: known as блат in russian,
https://en.wikipedia.org/wiki/Blat_(favors). though that word is more often used in context of getting ahead i think it basically applies to overall structure of society. when shit hits the fan you call a your sister's husband's uncle who's a general, "vasily mikhalich, this is such and such..."
☟︎ phf: actually reminds me of this guy, fred reed, from earlier internet,
http://www.fredoneverything.net. he used to be a dc journalist, so he has a lot of candid comments about dc northeast and generally race in america
phf: to misbehave, idle however long and send data as large as they want. what's not implemented: prioritizing trusted nodes over others during node selection: you might still lose connection by natural means, in which case -addnode nodes will be dropped, and a standard node selection mechanism is used. the patch so far is here
http://paste.lisp.org/display/155710. i'm thinking that ultimate vs. trusted distinction might be unnecessary. i would
phf: trinque: re lisp rps, you might want to look at cmucl's WIRE and REMOTE packages,
https://common-lisp.net/project/cmucl/doc/cmu-user/ipc.html. while you can send sexps over the wire and slime/swank do it by sending readable forms in netstring format, you start running into issues when you need to ipc opaque blobs, like lambdas, hashtables or clos instances. cmucl's ipc solves all those issues, unfortunately married to cmucl. i think it woul
phf: i remember that we were actually taught how to properly treat teachers
https://www.youtube.com/watch?v=rcZgoOyalaI amusingly i'd never seen that short on tv, it would always play during "entertainment break" when they would send us to a school movie hall to watch random stuff
phf: asciilifeform: what about something like this
http://paste.lisp.org/display/154647, put a flag on sighup, put a couple of checks (i'm not sure if my guess as far as mainloop is correct) for the flag, do a stop the world snapshot. can have it running normally, periodically send kill -HUP ...
☟︎ phf: ccl for example uses a hacked up version of this ffi generator
http://www.ccs.neu.edu/home/lth/ffigen/, which is in turn a set of intrusive patches against gcc. can be done, but wouldn't go into upstream for political reasons
phf: for example this code
http://paste.lisp.org/display/154625 validates signatures (using ccl's ffi generator and slightly patched gnupg 1.4.19), but on failure verify_signature either prints to stdout, with no notable return code or sometimes exit(...)'s the whole process
phf: <asciilifeform> mircea_popescu et al: dulap rebooted today for no reason known to me. << if you start evaluating new hosting solutions, try these guys
http://www.tummy.com. uptime on my box 529 days
phf: ascii_field: i've tried reproducing the leak, but so far it looks like so according to my small test, mapTransactions.clear() should just work.
http://glyf.org/tmp/foo.cpp.html there's a bunch of copy allocations that get cleaned up, but you'll notice when foo.clear() is called that picks up the leftover objects.
phf: thestringpuller: you should try patching that patch, by adding
http://www.cplusplus.com/reference/map/map/begin/, for(...) { delete iter->second; } for mapTransactions and mapNextTx in the JettisonMempool function. seems like an easy fix, i don't have my env setup at the moment
☟︎ phf: according to bitcoin script documentation "Some of the more complicated opcodes are disabled out of concern that the client might have a bug in their implementation" (
https://en.bitcoin.it/wiki/Script). an example of disabled script OP_CAT, Concatenates two strings
phf: pete_dushenski: fyi, it's available freely on kat.cr, probably can be downloaded at pipe saturation level, rather then pulling it from someone's
http phf: ben_vulpes:
http://dpaste.com/2Q2YKDB << so we were poking at gernika yesterday and it looks like CS didn't fully build. i'll take a look at his "successful" cs build log today, and see what comes up
phf: ben_vulpes:
http://paste.lisp.org/display/152828#1 << read-sequence reads octets (i.e. unsigned bytes) into an array, so you want (make-array size :element-type '(unsigned-byte 8)) and you also want to then explicitly convert an octet array into a string. later is implementation dependent (since concerns encodings, etc.), ccl has DECODE-STRING-FROM-OCTETS and sbcl OCTETS-TO-STRING, both support encodings. since version is ascii, a naive converte
phf: for the record i think a secure and verifiable path for receiving a key of person in wot is to ssl connect to freenode using explicit server key, request !shasum wot from assbot, download
http://files.bitcoin-assets.com/wot/wot_users.sql.gz, verify its shasum, do `zgrep -oE '\([^)]+phf[^)]+\)' wot_users.sql.gz` (or whatever nick), the second number in the grep output is going to be the key fingerprint, next grep --recv-key <fingerprint>
phf: williamdunne: not builtin, but here's a generic object printer,
http://paste.lisp.org/display/153363. if you have an instance of a class, you'll get #<FOO (A . 1) (B . "test") C #x123123> (where C is unbound)
phf: next step in SEO, leaving links on b-a. "hitler lizard diddled singles!
http://..."