log☇︎
78200+ entries in 0.61s
Framedragger: mircea_popescu: nono - sorry for confusing - "older" as in "previously seen in same logfile", it's for my internal use so i don't go insane. all of this is from single scan even in 13-14 june.
Framedragger: imma dump all this in a nice format now, i'll separate OS string from ssh versionstring i guess
Framedragger: btw i'm going thru those ssh banners from ssh scan logs finally, and there's some inconsistent crap there (thanks openssh): same ip&port may respond with two different banners during same scan (the ssh-keyscan utility may spit banners for same server multiple times). it seems usually the mismatch is in adding a minor version onto ssh server string only (e.g. [SSH-2.0-OpenSSH_5.8] vs. older [SSH-2.0-OpenSSH_5.8p2])
Framedragger: 'tis what i figured :) my christmasy spirit will not be diminished, tho!
mircea_popescu: "but mp, it was simple when i made it" "yes, if i define three letter strings as various pieces of literature, i'll be able to "write" whole books by saying agafufu. so what of it."
mircea_popescu: http://btcbase.org/log/2016-12-12#1581948 << dude what ? link me where you tried it wouldja, i recall it working fine when eg gpg source. ☝︎
ben_vulpes: i also have no suggestions for fixing your problem, asciilifeform
a111: Logged on 2016-12-12 03:46 phf: fwiw that solution works reasonably with btcbase (right now it's not used, but it picks up a README from each patches folder and cats it inline before the graph, so i can add a "here's all the additional stuff that you might need for this v tree")
asciilifeform: i considered making, by hand, a v-able netlist, with component values etc. , in sexpr format, for a nonexistent tmsr cad. the real problem is that everyone, without exception and including myself, will insist on viewing the 'unofficial' pictoral schematic.
asciilifeform: sorta what i tried earlier today...
mircea_popescu: i fear the only way forward is for data to be base64'd, deedbotted, and then referenced as such in code.
asciilifeform: ftr i still have thought of no satisfactory solution.
mircea_popescu: (i've been running into a version fo this in eulora too ; with the art assets)
phf: fwiw that solution works reasonably with btcbase (right now it's not used, but it picks up a README from each patches folder and cats it inline before the graph, so i can add a "here's all the additional stuff that you might need for this v tree") ☟︎
mod6: I support no such futher complixity in V/vdiff to deal with these blobs. No one-offisms, etc.
mod6: That said, I'm not positive what is a favorable solution to this. For me, I guess I would have considered a disjointed genesis. All code in a genesis.vpatch, plus a comment in the code or README.txt file that points to a clearsigned, base64 encoded deed of the (repeatably extractabale) binary (image in this case).
mod6: All in all, I agree that blobs do not belong in a vpatch. As stated, they are for readable, grokable, text only.
a111: Logged on 2016-12-12 02:51 phf: i will flatten this shit, or help me god. so far the solution i figured that doesn't require writing code or using dodgy third party software is to use the video as a material texture inside a sphere in blender. with some 3d space camera shuffling i can produce two separate video streams, one of knuth and one of slides, but the result looks like dog so far.
phf: i will flatten this shit, or help me god. so far the solution i figured that doesn't require writing code or using dodgy third party software is to use the video as a material texture inside a sphere in blender. with some 3d space camera shuffling i can produce two separate video streams, one of knuth and one of slides, but the result looks like dog so far. ☟︎
phf: so stanford release knuth's annual lecture in a "360" video format, and the write up is disgusting "stanford part of the future!!1". basically you get a 7gib video/80mib audio stream, a fraction of which is a distorted slides and knuth, where's the bulk of which is audience and static ceiling. the thing doesn't render on anything but google stack and ipads. i spent about two days jumping through various hoops trying to get it to render
mircea_popescu: i don't specifically care, myself, but i can't seem to bring any argument that'd stand when someone decides "fuck him, he's a microsoft tool".
Framedragger: i guess it's legitimate to bitch about that. i've never been sure. but i did poke at an acquaintance who had plans of working at gchq. to be consistent, i should.. be consistent.
asciilifeform: i was not going to expand on the 'p' thread until the proggy is done, but this is probably a good time to say 1 more ☟︎☟︎
Framedragger: i see what you mean.
asciilifeform: http://btcbase.org/log/2016-12-11#1581840 << i dunno that he even bothers to pretend, he is a confessed recipient of microshit cheques ☝︎
asciilifeform: http://btcbase.org/log/2016-12-11#1581842 << this is entirely so, and iirc i smashed my head into this very wall when jurov made ( per my scheme ) 'turdatron' ml system ☝︎
ben_vulpes: either i remember a decrypted clearsign's hash not matching or am inventing the memory
trinque: ben_vulpes: was it you and me that ran into this problem at some point? I cannot remember regarding what
trinque: for sure. I'll let all know what I find.
trinque: so then if I've got a sig of an un-transformed item in ML, it may contain things the transformer would've stripped/modified if it were clearsigned
asciilifeform: mircea_popescu: this is neither 1st nor 10th 'faux computer' i make.
asciilifeform: i could go on but why ruin surprises.
trinque: I'd have to spelunk further to confirm, but it looks like clearsigning is canonicalize -> sign
asciilifeform: that i omitted for simplicity
asciilifeform: phf: http://wotpaste.cascadianhacker.com/pastes/ApmIh/?raw=true << same example but before i stripped out the comments
phf: asciilifeform: you have 9ae 2ff 100 da9 * = unless i'm misreading
trinque: alright, but I am willing to entertain running gpg and P in parallel for some time, ftr.
asciilifeform: trinque: i cannot answer this, because it is an experimental weapon
asciilifeform: but i don't see a good argument for fucking it but not to deaoth
mircea_popescu: i suspect we just write a convertor.
asciilifeform: i have nfi yet.
asciilifeform: i dunno if there exists upon this cursed earth a rope that doesn't break when i go and pull on it...
asciilifeform: which brings back to #1 horror -- how do i deedbot a vpatch and its sig..?
asciilifeform: exists but i ain't signing that horror show.
asciilifeform: the schem will be nonclearsigned, the sig -- posted. the boards -- physically wrapped in copies of the schem. is all i can offer.
mircea_popescu: hey, i don't want unreadable turds in v trees either.
asciilifeform: and i find myself agreeing with phf
asciilifeform: simply that i am stuck in this corner, where there is a thing that needs doing, that i do not have with what to do.
asciilifeform: and i haven't one
mircea_popescu: give me something other than a 5mb dxf to work with, as per this "Short when i wrote it" ?
asciilifeform: it was short when i wrote it.
mircea_popescu: at this point i'm not at all clear what problem you're trying to solve here, but it seems to have become "i wish to pack an arbitrarily long poem into an arbitrarily short notation in such a way it will never be forgotten."
jurov: it's just an attribute. when i include some TEXT chunk in png with an url, nothing happens either.
mircea_popescu: i also tested
asciilifeform: i tested.
asciilifeform: i do not want to sign a 'insert usg turd here!' even if theoretically the instruction is not followed on extant renderer
mircea_popescu: i have nfi, you won't fix your set-up so you can see how great a svg i made out of your dxf!
mircea_popescu: asciilifeform i could readily reduce the svg if you wish, most of it is dreamweaver-style pointless tagging ☟︎
asciilifeform: which i am not even sure differs substantially from the svg situation.
asciilifeform: i am apparently 'blessed' with turning over every stone in every garden and releasing every type of insect possible.
asciilifeform: and ftr i am not signing a document that i am supposed to be the original author of but CANNOT GET TO HAPPEN ON MY BOX
phf: mircea_popescu: i have nfi either, i have it unpacked
jurov: i de-base64 each one, then concat and i can open it fine
asciilifeform: i had -i -d
jurov: then it decodes and i can view the svg
asciilifeform: jurov: ^ is what i did
jurov: when i do base64 -di
mircea_popescu: asciilifeform look, saying "the v is not allowing x char sequence i wanna use" is one thing. saying "o woes i have this here book of 5mn chars and i want it to be readable in 3 minutes" is another thing.
asciilifeform: and i've been using THIS gimp since 2010.
mircea_popescu: phf i have nfi what he's on about. seems to me totally broken gimp install.
asciilifeform: i am NOT signing 2+MB of <path d="M 74.336 74.2623 A 0.03178446947803285 0.03178446947803285 0 0 1 74.381 74.3072 " stroke-width="0.0635"/>
trinque: release and I'll build into deedbot
asciilifeform: trinque: that is simple and i solved it.
trinque: I am discussing a supposed tmsr sign format that does not have but a header and payload
asciilifeform: i have '---' in there. it will FUCKING STAY '---'.
trinque: wtf if I invalidate #1 that says nothing of #21
trinque: I read the whole log.
asciilifeform: i will NOT allow gtk.
mircea_popescu: asciilifeform i do not use gtk3!
asciilifeform: what, i gotta allow gtk3 now ?!?!??!?!??!?!
asciilifeform: because i have nothing on my box that will show THIS svg
asciilifeform: a) 2MB crapaola, i'm not signing
mircea_popescu: asciilifeform get a working gimp ? i dunno what to say. mine eats it, i am looking at a 1960x2490 version of it atm, looks fine
trinque: I signed his signed thing is already done
asciilifeform: i tried in www browsers also -- also barf
mircea_popescu: wut ? i'm looking at it as it is.
mircea_popescu: i got it!
asciilifeform: http://nosuchlabs.com/pub/tmp/goat.dxf << and i will not that i HAVE NFI WHAT THIS LOOKS LIKE or if it corresponds to what i saw when i drew the fucker!!!!
mircea_popescu: anyway, "png as v format" is inept beyond belief. let alone "i wish to inspect this matter and can't use my eyes", it's worse : "suppose i want this to be 3x as large" "oh can't do that". well da fuck.
asciilifeform: there'd be 2 of them, i'll make 1 for example
asciilifeform: mircea_popescu: i did, 0 result.
a111: Logged on 2016-12-11 19:14 phf: binary blobs remain an unsolved problem. the whole idea of binary (or base64) is contrary to some of the more philosophical aspects of vpatch you and mp like to discuss, so i don't know if base64 even solves it.
mircea_popescu: see, there's many problems here, and phf correctly identifies the general case in http://btcbase.org/log/2016-12-11#1581294 ; for eg : what if i want to scale ? ☝︎
asciilifeform: also dxf apparently, but i have not been able to get ~these~ to render anywhere!
mircea_popescu: i was wtf is this extra shit on the side oh OH!
asciilifeform: and i ain't signing this shit soup
a111: Logged on 2016-12-11 19:05 asciilifeform: i have nfi right now what to do with this nonsense.
asciilifeform: i will illustrate: yes, cad proggy can export netlist. but said netlist has no provisions for describing a) part valus (e.g., you get C10, and no place for '0.47uF') or the geometries of the physical chips (you get, e.g., IO1-15 but way to say 'that's pin 44 of a pqfp-44 plastic thinleadc carrier)
phf: so my proposed "put everything into prelude" solution preserves the literacy angle, and uses prelude as a "annotation" section, i.e. space for verbiage, supporting material etc. this will work for free with things like btcbase. can also pack it into a tar file and sign ~that~, but breaks a lot of tools
phf: mircea_popescu: well, the way i got what you grokked from v when it originally came out, is that vpatches are literate, for things that you can reason ~and meaningfully amend~. "unicode on a chalkboard" thread is also relevant