log☇︎
600+ entries in 0.019s
phf: http://btcbase.org/log/2018-10-05#1858751 << my preferred method is to `ssh -D 8080 host` which sets up a socks proxy with port 8080 on your local machine and outbound on the `host`. you can then configure e.g. firefox to send everything through that proxy ☝︎
phf: asciilifeform: i have a ksum PoC for you, http://btcbase.org/patches/vtools_ksum signed but it's from workbench, potentially buggy. "ksum foo bar qux" gives you shasum style <hash> foo\n<hash> bar\n<hash> qux\n
phf: ^ http://p.bvulpes.com/pastes/M42gA/?raw=true
phf: mircea_popescu, ave1 http://p.bvulpes.com/pastes/QtjVR/?raw=true this was the log from the last invocation, but i'm not sure if it's representative of an issue. this was downstream from a handful of hacks and manual invocations
phf: ave1: i'm getting the following error http://p.bvulpes.com/pastes/49Tie/?raw=true when building ada-musl-cross-2018-06-01. i feel like it came up before, but i'm having hard time finding the thread ☟︎
phf: ave1: i missed your zfp_4 but added http://btcbase.org/patches/zfp_4_assert
phf: asciilifeform: http://btcbase.org/patches?patchset=udp and http://btcbase.org/patches/udp_genesis
phf: diana_coman: http://btcbase.org/patches?patchset=smg-comms and http://btcbase.org/patches/smg_comms_genesis (i found the sig in /vpatches/)
phf: http://btcbase.org/log/2018-09-08#1848612 << was at sea, but i was also keeping up with the logs (much better in flight entertainment!), i'll take the pill, but not sure i'll have the immediate use for it beyond ogling. i'm having a hard time recreating even the max-heathen environment that will simply reproduce the google stack as is ☝︎
phf: http://btcbase.org/log/2018-08-20#1843300 << little known fact: slime's architecture was originally implemented in a similar project for erlang called distel, by the same author luke gorrie. lukego also wrote an emacs clone in erlang and tcp/ip stack in cmucl. ☝︎☟︎
phf: http://btcbase.org/log/2016-04-12#1450437 http://btcbase.org/log/2016-04-11#1450068 ☝︎☝︎
phf: to close upstack before it gets lost, you need http://ave1.org/2018/gnat-zero-foot-print-take-4-introduction-of-the-platform/ and http://ave1.org/2018/gnat-zero-foot-print-take-3-regrind/ the later is a full regrind (which i also didn't notice until btcbase failed to link 4 to rest)
phf: http://btcbase.org/log/2018-08-10#1840849 << these are not stories of abuse, these are war stories "what i do matters". it's such a huge part of the lore that i wouldn't be surprised if the hotel mgmt does it to attract more of an attention to the event. you mean i get to hang out with dangerous hackers?? ☝︎☟︎
phf: http://btcbase.org/log/2018-08-08#1840391 << you're confusing homebrew with fink (which i believe is now mostly dead). homebrew is closer to gentoo's portage: it's written from scratch in ruby and so are the port descriptions ☝︎
phf: (^ http://phrack.org/./issues/2/3.html#article) ☟︎
phf: http://btcbase.org/log/2018-08-06#1840047 << i believe item in question started as "lulz what else can we print wit dis thing" kind of like at a house party at 4am one tries to figure out what else can be used as a vodka mixer, but the government ban turned it into "i do what i want mom!1" ☝︎☟︎☟︎
phf: (in related lulz, https://github.com/AdaCore/gsh)
phf: btcbase shasum for reference http://p.bvulpes.com/pastes/ijInK/?raw=true
phf: according to `mkdir t; cd t; wget --quiet http://ave1.org/code/zfp/v/patches/{zfp_1_examples,zfp_2_noc,zfp_genesis}.vpatch; for i in *.vpatch; do cmp $i ../$i || echo fail; done ` everything's fine
phf: http://btcbase.org/log/2018-08-05#1839743 << probably a multiroot situation. otherwise btcbase does sound alarm (e.g. the "deprecated" patchset has some examples). ftr btcbase is a visualizer of extant patches, it is to some extent more permissive by design than production vtron ☝︎
phf: http://btcbase.org/log/2018-07-31#1838315 << of course vtools sha branch vdiff produces correct output... ☝︎
phf: in fact particular line http://btcbase.org/log/2016-03-28#1440677 has been changed in kako's log, hxxp://log.bitcoin-assets.com/?date=28-03-2016#1440677 spot the difference! ☝︎
phf: ^ https://www.youtube.com/watch?v=bh9ijtC8LLk
phf: http://btcbase.org/log/2018-07-10#1833262 << i traced the problem to wear and tear of one of the wires that runs from motherboard to the screen around the hinge area on the power plug side. the wire coating was damaged, and the wire would get in contact with the frame. it's the kind of issue you'd see on an old laptop after a decade of use, but i guess in this case chineseum ☝︎
phf: https://dl.bintray.com/xquartz/downloads/XQuartz-2.7.11.dmg
phf: http://btcbase.org/log/2018-07-19#1836372 << fyi, i appreciate the hackery, but the relevant code is already in the vtools http://btcbase.org/patches/vtools_vdiff_sha/tree/vtools/src/system.h#L145 as I mentioned in logs http://btcbase.org/log/2018-06-27#1830179 the problem is that byteswapping is non-standard. each libc implements its own. more importantly __bswap64 that PeterL is using is an internal inline function, that exists in ☝︎☝︎
phf: http://btcbase.org/log/2018-07-18#1836056 << i also don't have means of reproducing the majority of physical objects i use, including the machine my tools run on. i have to ask is that a hypothetical roomfull or we're talking #trilema specifically? ☝︎
phf: http://btcbase.org/log/2018-07-18#1835974 ☝︎
phf: well, so it goes back to http://btcbase.org/log/2018-07-18#1835969 their fault is for being born and staying a particular kind of american ☝︎
phf: ah, that explains the misunderstandings. ave1's no-c compiler has a completely custom ada runtime library, which is a tiny subset of the whole standard. http://btcbase.org/patches/zfp_2_noc/tree/ the adainclude part
phf: asciilifeform: if you haven't looked, ave1's item is a significantly cut subset of ada's standard, where, e.g. http://btcbase.org/patches/zfp_2_noc/tree/adainclude/a-textio.ads is text_io (compare to real text_io)
phf: http://btcbase.org/log/2018-07-18#1835681 << in allegro's case the model was (is?) a vendor partnership, they don't sell to all comers. you have to have a sit down where you essentially pitch your project to them and work out a payment structure, some combination of buy in, royalties, etc. similar to some of the banking vendors i worked with, like kx ☝︎
phf: http://btcbase.org/log/2018-07-18#1835696 << i believe at least in the case of allegro the ownership is the dks/symbolics model (or perhaps soekris model), guy who made it sells it and there's enough sales money to periodically fund developers, add new features, etc (considering that some of the contracts are finance and gov) ☝︎☟︎
phf: http://btcbase.org/log/2018-07-11#1833362 << oh i see, your flow command outputs an impossible ordering, but press-path gives a correct press order, so i was wrong, sorry about the fud ☝︎
phf: also http://btcbase.org/graph.svg?patchset=stable&type=transition vs http://btcbase.org/graph.svg?patchset=stable&type=ad
phf: http://btcbase.org/graph.svg?patchset=vtools&type=transition vs. http://btcbase.org/graph.svg?patchset=vtools&type=ad
phf: ave1: ty, you've been placed http://btcbase.org/patches/tmsr-pgp-genesis
phf: esthlos: your v_genesis patch is broken, http://btcbase.org/patches/v_genesis/file "contact" etc. ☟︎
phf: http://btcbase.org/log/2018-07-07#1832417 << so far only one patch is using keccak, the new patches that came out are all sha512 and none of the existing projects attempted a regrind ☝︎
phf: http://btcbase.org/log/2018-07-02#1831298 << unless you have particular preferences, i'm going to throw it into the same patchset as ircbot. it'll follow the grand ircbot tradition of a genesis that never the less relies on the adjacent patches ☝︎☟︎
phf: ave1: http://ave1.org/tarpit/tmsr-pgp-genesis.ave1.sig is missing
phf: http://btcbase.org/log/2018-07-06#1832312 << there's no reason, i literally just returned from the walk where i remembered some outstanding things i need to do, that was one of them. ☝︎
phf: http://btcbase.org/log/2018-07-03#1831431 << looks like it indeed was a loose screw. reassembling the thing fixed the issue ☝︎☟︎
phf: http://btcbase.org/log/2018-07-02#1831410 << his work in progress parser doesn't handle end of file, so as of right now the error is normal ☝︎☟︎
phf: did you use the vmlinux.kpart from http://os.archlinuxarm.org/os/ArchLinuxARM-veyron-latest.tar.gz by any chance?
phf: asciilifeform: oh yeah, we've definitely had conversations on subj; also a thread where old unix heads rant and rave on subj https://minnie.tuhs.org/pipermail/tuhs/2018-June/014141.html
phf: https://queue.acm.org/detail.cfm?id=3212479 "C Is Not a Low-level Language: Your computer is not a fast PDP-11." ☟︎
phf: http://btcbase.org/log/2018-06-28#1830593 << famous incident with kuchma, when he called gas burner "газова горілка" ☝︎
phf: https://hope.net//schedule.html for expert entomologists ☟︎
phf: http://btcbase.org/log/2018-06-28#1830577 << in 2005 or so shmoocon still had vestiges of phrack culture, as has been discussed plenty on here it all finally died sometime 2010 ☝︎
phf: asciilifeform: since you're a fan of these kind of homepages, here's one i found today http://www.quadibloc.com
phf: PeterL: the approach that we've been taking with legacy C code is pulling out autotools, and replacing with a single #ifdef/.. configuration header. outside of linux/bsd code is probably not going to work, and the approach is to look at the configuration header file (http://btcbase.org/patches/vdiff_sha_static/tree/vtools/src/system.h#L145 in case of vtools) and patch it for your system ☟︎
phf: not sure if you saw the thread, http://btcbase.org/log/2018-06-15#1825784 ☝︎
phf: relatedly, an amusing post re clemacs, https://www.xach.com/naggum/articles/3115132473442167@naggum.no.html
phf: http://btcbase.org/log/2018-05-31#1820078 << tracked it down https://web.archive.org/web/19990221231608/http://sourcery.naggum.no/emacs/ ☝︎
phf: asciilifeform: https://www.youtube.com/watch?v=SPu8iRwZBZU
phf: mircea_popescu: keybase can also be used to store private keys, it's my understanding that the person in question put his private key on keybase http://btcbase.org/log/2018-06-22#1828688 ☝︎
phf: http://btcbase.org/log/2018-06-22#1828521 << https://dspace.mit.edu/handle/1721.1/6438 john c mallery (for log readers, current symbolics copyright hoarder) and his main contribution to ai memos ☝︎
phf: http://btcbase.org/log/2018-06-21#1828378 << distinctions like that are often subtle and a matter of taste, but as long as the overal approach is informed now might be a good time to paste what you have. ☝︎☟︎☟︎
phf: http://btcbase.org/log/2018-06-21#1828088 << ah ty, i didn't realize that was done on top of shiva ☝︎
phf: http://btcbase.org/log/2018-06-21#1827972 << i was trying to figure out how that would happen on same machine between invocations until i realized that's neither the issue nor what is going on ☝︎
phf: http://btcbase.org/log/2018-06-21#1828005 << the closest we got to a replacement i believe was asciilifeform's shiva, i.e. a tinyscheme embedded into trb runtime. it was suggested as a useful exercise for novices to attempt to expose existing, useful rpc function using it, but there were no takers. at some point the idea of using shiva in prod also went away, because tinyscheme is not necessarily production ready (primarily because of C-ism issues). as ☝︎☟︎
phf: further kommunity conversation on reproducible builds https://lwn.net/SubscriberLink/757118/f2f894279576c348/
phf: honestly half of the ones i saw, from a totally different range of companies, look familiar, but i suspect that at least moscovites got the ussr version, probably something like this http://scaletrainsclub.com/portal/images/portal_files/vasily/istoriya_proizvodstva/ov_05.jpg
phf: http://scaletrainsclub.com/portal/images/portal_files/vasily/istoriya_proizvodstva/ov_02.jpg
phf: oh lol apparently they made them in ussr also http://scaletrainsclub.com/portal/our-library/2008-05-07-13-48-02/117-2008-07-23-17-21-55
phf: mircea_popescu: but no check out liliput, https://www.modellbahnwelt24.de/Liliput-3
phf: huh i don't remember that style at all. looks like metal too, the ones that i had were plastic, kind of like https://hattonsimages.blob.core.windows.net/products/L350032-LN_3314489_Qty1_1.jpg
phf: traditionally in ru we had https://www.fleischmann.de/en/productsearch/0-0-0-0-0-0-0-001001-0/products.html which was powered from outlet and down converted. trains would go, when place on conductive tracks and you controlled the speed with a potentiometer, so there's some fucking montesori going on
phf: https://www.mprove.de/diplom/gui/Kay72a.pdf
phf: helpful pbf illustration, http://3.bp.blogspot.com/_T792V0_uoCw/R6T6hAIArPI/AAAAAAAAAWk/8zJzYpskpNA/s1600-h/PBF244-Preach_Skate.jpg
phf: mircea_popescu: not only is it their order, there's barely anything else mentioned in there https://www.gnu.org/software/emacs/index.html#Releases
phf: http://btcbase.org/log/2018-06-15#1825808 << slow progress, snake soldered but untested. i realized last night that i don't have any linux devices, and was too tired to figure out how to do usb-serial/../new_id equivalent on a bsd. ☝︎
phf: http://btcbase.org/log/2018-06-15#1825631 << updated, but it's a novel way of using manifest though: normally it requires a regrind where manifest is built up as you go, so the press order is enforced through graph. right now your manifest gives a press order, that's not enforced by anything ☝︎☟︎
phf: http://btcbase.org/log/2018-06-15#1825742 << that's beautiful, ought to be distributed in major american cities ☝︎
phf: http://btcbase.org/log/2018-06-13#1825027 << traditionally chifir is made with http://fb.ru/misc/i/gallery/44825/1701533.jpg ☝︎
phf: http://btcbase.org/log/2018-06-13#1824947 << heh, of course i just received mine today. ☝︎
phf: http://btcbase.org/log/2018-06-13#1824917 << https://www.youtube.com/watch?v=nlTnKsekQMs ☝︎
phf: http://btcbase.org/log/2018-06-13#1824502 << right. it's also not a good idea for an arbiter to sign someone else's exam, as if it's anything but. i've offered to run the proposed experiments without arbitrating, but that's not what ascii wants. ☝︎
phf: asciilifeform: so i was going by http://btcbase.org/log/2018-06-12#1823998 to http://btcbase.org/log/2018-06-12#1824022 where you lay out your requirements for "successful crack", which make sense ☝︎☝︎
phf: http://btcbase.org/log/2018-06-12#1824041 << if you decide that the effort is worth the while, i'll referee ☝︎
phf: http://btcbase.org/log/2018-06-11#1822354 << updated, but mp-wp_comments-fix also requires an updated. right now it's showing missing antecedents.. ☝︎
phf: http://btcbase.org/log/2018-06-08#1821714 << will do, i've had all the parts shipped at this point, but i won't be back until monday.. ☝︎☟︎
phf: heh they are also using gentoo for their stuff.. https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/master/chromeos-base/chromeos-cr50-scripts/
phf: http://btcbase.org/log/2018-06-08#1821658 << they could also bring back 701c butterfly keyboard design, but i guess that's too gimicky. ☝︎☟︎
phf: http://btcbase.org/log/2018-06-07#1821289 << https://lkml.org/lkml/2016/7/19/957 https://lkml.org/lkml/2016/7/27/523 (i'm sure ascii saw already, adding for logs) ☝︎
phf: http://btcbase.org/log/2018-06-07#1821267 << right about. i was mostly just embarrassed for him when i read his blog.. ☝︎
phf: http://btcbase.org/log/2018-06-07#1821238 << crafty little strategy "we built a device with an open EC" "..." "we now have a sikrit cheap making sure our EC is not too open" ☝︎
phf: mostly a convenience since <patch name>/hunk/<path of hunk> works for all patches now, e.g. http://btcbase.org/patches/genesis/hunk/bitcoin/src/init.cpp
phf: i added a link on patch pages to "split hunks", which allows to render any patch the way mp-wp genesis is being rendered, e.g. http://btcbase.org/patches/genesis?inlinep=false
phf: i ended up adding windows newline rendering support, which i'm rather pleased with, e.g. http://btcbase.org/patches/mp-wp_genesis/hunk/blog/.htaccess though the pressed version is still broken.. http://btcbase.org/patches/mp-wp_genesis/tree/blog/.htaccess
phf: on the other hand http://btcbase.org/patches/mp-wp_comments-fix is still rendered the usual way
phf: http://btcbase.org/patches/mp-wp_genesis so here's one possible solution, for mp-wp genesis instead of listing hunks inline, i link them to separate pages: http://btcbase.org/patches/mp-wp_genesis/hunk/blog/.htaccess http://btcbase.org/patches/mp-wp_genesis/hunk/blog/default_avatar.png.svg etc. ☟︎
phf: http://btcbase.org/log/2018-06-03#1820367 << there isn't one, there is a peculiar bug that seems to only manifest in my lispworks dev environment. things actually work on production, though the patch page is 20mb ☝︎
phf: http://btcbase.org/log/2018-06-02#1820273 << hanbot's mp-wp genesis is 5.8 mb, i haven't yet figured out yet how to make btcbase not fall under the size. at the very least i need to add a caching layer, so that i'm not regenerating 5.8*n for the generated html every time ☝︎
phf: http://btcbase.org/log/2018-06-02#1820260 << this was before, http://barksinthewind.com/2018/vtools-keccak-regrind/#selection-11.0-37.1 ☝︎
phf: https://www.xach.com/naggum/articles/notes.html
phf: http://data.xach.com.s3.amazonaws.com/cll.txt.gz http://data.xach.com.s3.amazonaws.com/naggum-articles.tgz
phf: there are bits and pieces of code in the usenet, i actually use one of naggum's functions extensively: https://www.xach.com/naggum/articles/3115568738543631@naggum.no.html
phf: http://btcbase.org/log/2018-05-29#1819488 << i vaguelly suspect that's something i need to do, but i don't know if i'm willing to go through the whole song and dance with american medical professionals (tm) to extract the medication out of them. might be easier to wait till my next trip to russia.. ☝︎☟︎