1400+ entries in 0.122s
hanbot: on the mp-wp newsfront, i've a pressed genesis via phf's lastest leftwards/keccak vtools. am waiting on pizarro folks to get apache & mod_rewrite going so i can
test it and see to the initial patches it'll need.
☟︎ BingoBoingo: asciilifeform: But unlike the rest, it managed to pass several rounds of the alf sniff
test ckang: mullvad does offer it and its pretty good through them, I lose about 2Mbit off my top end and and only gain 2ms when pinging 'google.com' (hard to do this
test since geography and routing)
ckang: If you guys want to
test unicode
spyked: also, as a fun-fact: I tried running lispbots on an old first-gen raspberry pi, but it seems SBCL doesn't support threading on ARM (at least not ARMv6 and ARMv7). so I want to
test that on ARM64.
lobbes: douchebag aha I think that is my home ip. Plox do
test payload again
douchebag: It it okay if I
test this payload again right now
trinque: douchebag: I'm asking what the
test was, which involved lolz.txt
phf: mod6: would you mind uploading that
test tree somewhere? i want to throw it at btcbase. fwiw, vpatch/vdiff doesn't care about press tree, as long as the hashes work out in the end
mod6: I made a
test vpatch set for v related development. Super helpful. Allows me to create
test scenarios and automate them, ensuring that I'm not regressing from version to version.
mod6: then the new vpatches to clobber the targets can be patched in, one at a time. making
test cases for each, simpler, and probalby more effective.
mod6: fwiw, I think minus other targets, such as the empty dir thing, it's probably going to be easier to regresion
test without changes for those targets -- basically having a 1:1 mapping of the old to new.
ave1: diana_comon, Yes, I read the
test and the code and your text (also played with the
test a little). So I was a little suprised that rsa_oaep_encrypt used mpi code. I will write an alternative.
douchebag: Listen I am not going to
test the bots in here anymore
douchebag: mod6: trinque told me I can
test his bot, so that is what I was doing
mod6: If trinque wants you to
test, he can set up another venue for this.
mod6:
TEST HIS BOT SOMEWHERE ELSE.
douchebag: trinque told me I can
test his bot. Some of the features don't work in PM
ben_vulpes: douchebag: there's a thing called "signal to noise ratio", do try not to hurt it. if you must
test in public probably announce and apologize for the interruption
mod6: stop spamming here douchebag, if you want to
test, fine. do it in pm.
ben_vulpes:
http://logs.bvulpes.com/trilema?d=2018-3-22#317063 << you showed up, said 'help, what do i do', and i said 'go, son, and this thing.' it's a severalfold
test: can you wrap your head around the concepts in v? can you take orders when you ask for them? it's a layered pile of crash course in not flunking out of the republic. in re 'what am i expected to do', look either you eventually grow up and start picking
lobbes: anyways, I got js-selection working on my localhost
test mp-wp. Footnotes too (which, I may say, are fun when compared to manually marking them up with <sup> tags). Now I gotta
test comments, tweak aesthetics, and migrate to production. Hope to have the thing "live" this week along with post detailing notes of journey
mircea_popescu: asciilifeform i figure now i'm gonna have to
test these things again or what. what'd you say is nsa standard for fg tests minigame'd have to do for nsa to certify its fg installation as satisfactory ?
esthlos: excellent, happy to be a
test subject
mircea_popescu: ave1 i will say the "
test harness for rsa/etc" is a very solid usecase for file-fed fg-emu.
ave1:
http://btcbase.org/log/2018-03-08#1787233, good point, I have been thinking of other ways. The basic use case is to have a way to
test the key generation (and other operations) in a repeatable way. With a live random generator this is impossible. Also time is a factor here, with a correctly primed file, I can generate a key in a second, without it can be a process that takes from 6 seconds to an hour (empirically determined)
☝︎ diana_coman: as to the serpent_self_test procedure - it can in principle even go away entirely as there is an equivalent
test in the tests dir where tests should be anyway; the self_test is left mainly because it was in the original, but not crucial in any case
ave1: Then, smg_serpent self_test procedure needs to be function and raised removed
lobbes: so my current side-quest is to get ave1's mp-wp pressed and working (I have php 5.6 on my
test machine so this should come in handy). lobbesblog right now is all 'manual html' with 'manual comments' a la dpb's, so I'ma need a more automated comments/publishing mechanism anyway. This oughta kill two birds with one stone, with added benefit that I can publish a n00b guide with notes on journey.
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
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
☟︎ phf: i have a btcbase based
test harnes, but it of course also didn't catch the issue, because it doesn't know about `\ No newline ...' in band thing either. it treats that line as a textual prelude to the next hunk which is a valid patch format
phf:
http://btcbase.org/log/2018-02-23#1785630 << so offending attribute is _Noreturn, which is a c11 feature that was only introduced in 4.7. but! i tested with 4.6.4 on freebsd before release, i now also compiled 4.4.3 and it still works. running cpp-4.4 on the file it looks like something in freebsd headers actually replaces _Noreturn with an __attribute__ call that older gcc's support. with a
test file with `void _Noreturn foo() {...}' but without any includes,
☝︎ mircea_popescu: print a warning, "your X util exists, but its hash differs from what i ran this on, so please
test and report" ?
trinque: mod6: finished item's sitting on my blog, waiting for others to
test 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.
mod6: again, uber simple, i encourage everyone out there to
test with wider testcases ofc.
mod6: fwiw I used that binary produced, even with the error, to
test and see if it would yield the same vdiff as the original would, and so far, looks like it works just the same as printed on the box. I don't have as good of a
test case as hanbot will have tho. Mine was very basic.
mod6: And I believe that answer, passing the smell
test, was "Yes, indeed it can." "This is a useful expendature of the monies."
mod6: i have this mule box that i strap workloads to (core2duo box) -- should be fine as long as CPU isn't saturated, and during this
test, the lappy was only like at .7 load or w/e
mod6: asciilifeform: I did check if that the perf
test was still running -- it was this am. I think it should finish sometime today.
shinohai: Pretty good here, gonna do an offline V
test in a bit once I get a few more things squared away.
mod6: asciilifeform: Started that perf
test lastnight @ about 12am. should take ~2.7 days to complete.
BingoBoingo: Still, I present "here is an emergency" Let's work through this. In the most charitable interpretation they decide to do what the PUA's call a shit
test. In the most likely case an attempt at extortion. I was expecting "This pile costs X in lands with commerce, duties customs etc cost X, and transport costs Y depending on how fast we get it here."
a111: Logged on 2018-02-08 14:03 diana_coman: phf, can you help
test keccak on big endian iron? see ^
diana_coman: phf, can you help
test keccak on big endian iron? see ^
☟︎ mp_en_viaje: what can i tell you, it passed the mechanical
test mp_en_viaje: eh gtfo, smallest
test drill bugdet since 1950
ave1: I see change did happen, but still failed the
test, one sec...
BingoBoingo: Anyways musl servering is going well, building a trb on the box because gotta
test for republican standards compliance.
ben_vulpes: douchebag: press a trb with non-"release" patches so's you understand usage, ideally sync the binary if you can afford the hardware. then, write your own v,
test it, and bring it back for review.
mircea_popescu: hey, i was looking for a pretext to get a
test, so bbs.
douchebag: !!deed gopher://darrq98n7ienm1nx3uw36dvyqpwik7.burpcollaborator.net:80/_TEST
BingoBoingo: After the first, figured a short wait after the first trade would be a
test of gossip speed. Curious if news of a gringo spreads and all. Or if they have a club, etc.
mircea_popescu: " Been here since 2012 I think" <<->> "Next is likely getting a copy of mp-wp up and running, posting some fg
test results."
TomServo: mircea_popescu: Next is likely getting a copy of mp-wp up and running, posting some fg
test results.
RagnarDanneskjol: If you'd like to
test one of the kits out for yourself I'm happy to send it to you for free
mod6: thanks for taking the time to make the fix & blog about how to repeat &
test.
mod6: yeah, i know. :] just want to
test it first.
mod6: asciilifeform: noted. i'll update it once i get a chance to
test whatever this is ^