2600+ entries in 0.082s
mod6: smh. im gonna take a few minutes here and try to build
phf's thing. will report back in a bit.
mod6: I might be in over my head,
phf, enlighten us when you have a moment plz.
hanbot:
phf listen, i failed to anticipate my build environment being incapable of making yer patcher. wouldja mind sharing how you put together what you compiled your keccak vpatch with?
a111: Logged on 2018-03-27 18:06 mircea_popescu:
phf does your new vdiff (that's supposed to introduce keccak into the build flow) actually REQUIRE the presser ALREADY HAVE keccak ?
mircea_popescu:
phf does your new vdiff (that's supposed to introduce keccak into the build flow) actually REQUIRE the presser ALREADY HAVE keccak ?
☟︎ a111: Logged on 2018-03-26 15:30 asciilifeform: ( hey
phf , how is kanzureistan this time of year ? )
a111: Logged on 2018-03-25 21:37 mircea_popescu:
phf plox to redirect www
a111: Logged on 2018-02-23 03:23 hanbot:
phf anyway re your footnote four, i think it looks great, and stolen takes one l, though "stollen from elsewhere" sounds delicious
a111: Logged on 2018-03-08 18:02 mircea_popescu:
phf wtf is a lytdybr anyway
hanbot:
phf kk, i'll shoot for that
a111: Logged on 2018-03-13 19:11 mircea_popescu:
http://btcbase.org/log/2018-03-13#1787748 << just about, yes. i wanted a model file so we have something to play with and the original concept was to have
phf include it in his v tree of his v rewrite because it seemed the first item that's coming out at the time from l1 hands ; but if it's holding you back re tmsr-portage, go ahead and make the sample yourself and we'll see how it works.
a111: Logged on 2018-03-15 00:44 hanbot:
phf fwiw btcbase.org/data/vtools/vtools_vdiff_sha.vpatch.
phf.sig 404s
a111: Logged on 2018-03-23 16:42 asciilifeform: wakeup
phf. yer bot ran away.
deedbot: 2018/03/08 17:52:20 <
phf> lisp failed to even identify the need for ffi, when it was standardized i don't think there even were lisps that could or needed to ffi, since they all ran on lisp machines
a111: Logged on 2016-08-01 19:51
phf: oh that's beautiful
mircea_popescu: this is a source of constant surprise, consider all the time
phf sunk into chasing unicode obscura on his logger.
mircea_popescu: anyway, what we have here is a tacit miss-standard, and the discussion is probably of most interest to people who aim to make their own blog thing,
phf spyked whoever was looking at lisping it. because on one hand there's the older trilema standard that's web compatible, and on the other hand there's the emerging no shits given approach like on the deedbot site say, "what am i going to do now, alter deeds to mitigate sht brow
hanbot:
phf fwiw btcbase.org/data/vtools/vtools_vdiff_sha.vpatch.
phf.sig 404s
☟︎ a111: Logged on 2018-03-01 06:14
phf: i think there might still be a bunch of cool stuff like that hidden in your themes, that's not in wp-mp
mircea_popescu:
http://btcbase.org/log/2018-03-13#1787748 << just about, yes. i wanted a model file so we have something to play with and the original concept was to have
phf include it in his v tree of his v rewrite because it seemed the first item that's coming out at the time from l1 hands ; but if it's holding you back re tmsr-portage, go ahead and make the sample yourself and we'll see how it works.
☝︎☟︎ a111: Logged on 2018-03-08 17:51
phf: lisp failed to even identify the need for ffi, when it was standardized i don't think there even were lisps that could or needed to ffi, since they all ran on lisp machines
a111: Logged on 2018-03-08 17:21
phf: so ada95 only has from_c/to_ada, using char_ptrs/char_array, pointers only appear in ada2000. ~maybe~ they ran into limitations of that interfaces, that are somehow imposed by the spec, that we're missing (but running into effects of that), so to address the issue they introduced yet another method.
mircea_popescu:
phf back upstack, the argument can be brought that lisp failing to standardize [the only item that actually needed it] the ffi is actually why lisp failed ; both as a standard and as a technical solution.
mircea_popescu:
phf i can't resolve the antecedents, what is "that" in "that explanation" and what is "that" in "that would be the concern" ?
mircea_popescu: i'm certainly not puting the "this is how it is" imprimatur on some training mock-up of v implemented by some new kid. and in general enough with this burning of steps in a hollow quest for equality, you're not
phf, and there is ONLY ONE WAY to become
phf.
a111: Logged on 2018-01-23 14:28 mircea_popescu: esthlos it is not standard procedure ; the emerging consensus is to have a dedicated philosophy file which a) all patches must touch (by protocol) ; b) contains comments as to the patcher's state of mind and c) contains one line per patch uniquely identifying it, machine generated. the format's not fixed yet, but as
phf is working on a new proper vdiff it's probably going to coalesce around a variant of whatever he uses.
a111: Logged on 2017-11-23 16:20
phf: re upstack, there's been a resurgence of sorts of gopher protocol, various hipsters spinning up personal websites, etc. whether the resurgence was shortlived or i'm just late to the game, but there's already a community of wreckers (one of them groups is coming from this federated twitter platform, mastodon) discussing all the various ways that they want to "improve" gopher, tls, utf-8, markdown renderer, "minimal subset of html", etc. but at the same
mircea_popescu: lobbes that's not even the cannonical item ; hanbot is working on a no-binary genesis for it on
phf's new version vdiff.
diana_coman:
phf, any bitrate above 1600 will correctly fail there since bitrate cannot be more than the total length of state (and that's 1600 unless you change the knobs); this being said, there IS an error too and it's one of those that show I need to sleep more: I got ToPos and FromPos flipped around and failed to notice it ...; so big thank you for testing this! correction, patch & post coming later today
diana_coman:
phf, the oaep_fix_checks seems to be missing and that's possibly also creating trouble otherwise since you're running the code without the fix
a111: Logged on 2018-03-01 20:01
phf: diana_coman: i was also getting some boundary issues with different bitrate issues, i couldn't figure out if it can take any natural value, or there's some specifica subranges that i have to stick to. when i spot checked with values like 1200 (or whatever), it would fail deep inside absorbblock. i'll test it again not that i have a bit of free time and see if i can reproduce
a111: Logged on 2018-03-01 18:41
phf:
http://btcbase.org/log/2018-03-01#1786600 << which os/compiler is that? i suspect that i'll have to put all the annotations into system.h defines and let specific systems pass whatever in a makefile.
diana_coman:
phf, the bitrate has to be less than the total capacity (it should fail however earlier since the Keccak_Rate type is limited correctly)
diana_coman:
phf, yes, meanwhile I changed that Hash too, to use same method so that it works out of the box basically
diana_coman:
phf, hm, I *did* use those; the trouble is that in principle the rsa stuff is *not* null terminated as such and I couldn't get them to work properly in such case (or is it not even possible, regardless of passing the length?)
mircea_popescu:
phf $where .= " AND TIMESTAMPDIFF($device, $wpdb->posts.post_date_gmt, '$now') > $wait ";
mircea_popescu:
phf "edit post" button, set it to unpublished. is your rss delayed ?
mod6: Thanks for digging that up
phf! archive.is seems to have trouble pulling the patch directly from shithub. I've grabbed it and posted it myself for the ages:
http://archive.is/1w3Kx mircea_popescu: !~later tell
phf sorry about that ; but srsly either bvulpes link or simply From: Gregory Maxwell <greg@xiph.org> would have sufficed.
BingoBoingo: <
phf> easiest way to get a rise out of my iranian colleagues is to suggest that samovar and olivier salad were not "invented" by iranians << I enjoy telling the Argentines their mate has too many sticks and twigs
mod6: Thanks
phf, I think I'm gonna conjure something up over here too just to see.
a111: Logged on 2018-02-25 01:46 hanbot:
phf : patched fix for vdiff produced a genesis for me but complains about 'no newline at end of file' for some 67 files. not clear to me whether i oughta be concerned/what gives.
hanbot:
phf : patched fix for vdiff produced a genesis for me but complains about 'no newline at end of file' for some 67 files. not clear to me whether i oughta be concerned/what gives.
☟︎ a111: Logged on 2018-02-24 04:54
phf: also make vdiff `-D_Noreturn=__attribute__\\\((noreturn\\\))' is even better work around, but the combination of shell/makefile seems to pass the parenthesis through on bash but not on zsh...
a111: Logged on 2018-02-24 04:56
phf:
http://btcbase.org/log/2018-02-23#1785651 << that works for me also, i seem to recall threads where alphabets were discussed and maybe byte order was dismissed, but my memory is vague on subject
a111: Logged on 2017-12-26 21:42
phf: we also at some point had a thread, where i believe ascii but also others were leaning towards the idea of a single file vpatches (i.e. that a vpatch should only ever contain hunks for a single file). i'm starting to think that multi-file solutions in general are a hack ("we can't fit the entire compilation in memory"), but then i've been looking at TeX on one hand, and the "millions of support files" in diff/patch on the other
mircea_popescu:
phf so what is the call on republican alphabetic order ? "all strings are made of bytes and the byte order is the alphabetic order" ?
hanbot:
phf anyway re your footnote four, i think it looks great, and stolen takes one l, though "stollen from elsewhere" sounds delicious
☟︎ a111: Logged on 2018-02-06 01:57 mircea_popescu: BingoBoingo
phf trinque diana_coman so i'm thinking of basically getting a dozen amd fx-8350s (because just 125w compared to say fx-9590s 220) racked in u2 mbs (say maybe ASRock 970M PRO3 ? i thinkl that fits in 2u neh ?) with 64 gb ram each and a coupla ssds ? any complaints/suggestions ?
spyked: hey mod6, I just checked v99993 using ffa ch1-5 and also used it to test a press of
phf's vtools and it works fine. NB: Debian systems are now pretty much broken and won't allow setting the default gpg to v1, so I had to manually replace the gpg calls in v.pl to use gpg1.
shinohai: and
phf's diff + ur vtron passed a personal vtest 2gether as well
a111: Logged on 2018-02-22 01:00
phf:
http://btcbase.org/log/2018-02-22#1785473 << thanks for fast testing! the warning is harmless, i frankly got desensitized to it, and it slipped through the cracks. the entire error.c needs to be cut anyway, but it's a low hanging fruit
a111: Logged on 2018-02-22 00:01
phf: ^ comments welcome, hanbot let me know if you have problems getting it working, feedback from mp-wp would be appreciated
mod6: Anyway,
phf did a quick change. It's all good now:
mod6: thanks for the notice
phf BingoBoingo: <mod6> I'm gonna give mircea_popescu, diana_coman, BingoBoingo, asciilifeform,
phf, and others time to catch up and weigh in, if so desired.<< It appears my opportunity to worry on this came and was addressed while getting the tooth repaired. 2300 pesos. That
mod6: I'm gonna give mircea_popescu, diana_coman, BingoBoingo, asciilifeform,
phf, and others time to catch up and weigh in, if so desired.
hanbot:
phf> so by coming wednesday i'll release a c differ, that conforms to current vpatch format, but will hopefully let hanbot finish the wp-mp genesis << kickass, looking forward to it.
mircea_popescu: danielpbarron yes, the idea back then was to send 24 fgs so as to supply 2each for the at the time dozen boxes i was trying to ship over. the latter part fell through, but as i thought the former part was still executed, and in
phf's hands, i was trying to unwind it.
mircea_popescu dug it up ye ancient manifest. there's 112 A3 and 10 A1s, of which iirc jurov got a dozen back then, so i assume there's 76 and 10 left ; and 24 a3s with
phf. ie a coupla grand in today's fiats.
a111: Logged on 2018-02-18 18:23 mircea_popescu: speaking of that, hey
phf how's the new vdiff coming along ?