log☇︎
11200+ entries in 0.082s
mircea_popescu: how the fuck am i going to be interested by a three-centuries-later, three-hundred-books-unread rehash of a ~minor~ ~peasant~ movement ?! what next, we're going to sit around wondering in fascination at pete_d's accomplishments ? hory shit, some guy got married and carefully didn't piss off the in-laws his whole life. NEVER HEAR THAT STORY BEFORE PLOX TELL ME MORE!
asciilifeform: mircea_popescu: you should see the jp bible some time.
asciilifeform: iirc mircea_popescu had a piece re macroscale version of cellular apoptosis.
asciilifeform: mircea_popescu: http://btcbase.org/log/2018-12-01#1877614 makes me suspect he's already eltsining ☝︎
a111: Logged on 2018-12-18 07:54 diana_coman: <asciilifeform> danielpbarron: relax, no neg ratings yet. but if folx end up snoring for long enuff, i expect will tune out -> fwiw I already tuned out
asciilifeform: guten morgen mircea_popescu !
a111: Logged on 2017-09-01 06:57 mircea_popescu: this actually happens, you flip the pixels it "learned" and it sees the fridge and says cat.
asciilifeform: btw i ended up using mircea_popescu's formatting pill.
asciilifeform: unrelatedly, mircea_popescu do ya think you can muster 30-40min this wk to eat the 14a maffs ? i'd like to know asap if there's typo or other hole.
asciilifeform: mircea_popescu: i heard before this phrase. what does it mean? 'this here is safe, but that there is where crocodile will emerge from your terminal and bite' ??
asciilifeform: mircea_popescu: for added lulz, given http://btcbase.org/log/2018-12-07#1878844 , one actually ~could~, in principle, bake 'rsa pnoje' ( in the sense that, e.g., 2048 * (1/.296) ~= 7kbit/s , moar than enuff for voice ) ☝︎
a111: Logged on 2018-05-04 17:15 zx2c4: mircea_popescu: oh. so. "the world doesnt care about the cool hackers on the internet, but only the assholes with prestigious positions." this has been a widely known complaint for a long time
asciilifeform: mircea_popescu: near as i can tell, it was a mixture of provocateur shilling and genuinely earnest usefulidjits -- schneier, for instance, was at the time an apparently-earnest 'activist', as was djb (who sued usg at considerable personal expense, and even won in some sense iirc )
a111: Logged on 2016-08-19 13:51 asciilifeform: https://pad.riseup.net/p/87Mazw3Jsdfe_pm/timeslider#11 << multistory lul tower. for instance, i had no idea what is 'riseup' until its pgp keys began to pop.
lobbesbot: juliankunkel: Sent 14 hours and 22 minutes ago: <mircea_popescu> would you kindly spare us the join/part spamming ? can read the weblogs just fine, no need to be connected with nothing to say.
a111: Logged on 2018-12-17 04:38 asciilifeform: diana_coman: http://ossasepia.com/2018/12/16/a-week-in-tmsr-3-9-december-2018/comment-page-1/#comment-4601
a111: Logged on 2018-12-17 03:20 nicoleci: diana_coman, your summary does look great! not as much jealous as amazed :)
BingoBoingo: asciilifeform: ben_vulpes is
a111: Logged on 2018-12-16 21:11 mircea_popescu: a blog doesn't fucking need! at all!) and so on all come at a cost. which cost you strictly and unmitigatably can not afford in web-facing production environments, period and full stop.
asciilifeform: mightily nifty summary piece btw, diana_coman
asciilifeform: diana_coman: http://ossasepia.com/2018/12/16/a-week-in-tmsr-3-9-december-2018/comment-page-1/#comment-4601 ☟︎
nicoleci: diana_coman, your summary does look great! not as much jealous as amazed :) ☟︎
a111: Logged on 2018-12-01 21:21 mircea_popescu: "the notion that airplanes could reproduce through laying eggs is merely a naive extension, in the vein of 'object A has properties a and b ; object B shares property a and therefore it is reasonable ~~~on a first approximation~~~ to expect it exhibit proerty b'. nevertheless, artifacts differ from nature in that one fundamental aspect, that they're inefficient, and therefore to achieve same ends end up heavy, and in the case
lobbesbot: mircea_popescu: The operation succeeded.
phf: also https://franz.com/success/customer_apps/animation_graphics/izware.lhtml
amberglint: it's still mentioned on Allegro CL's site: https://franz.com/success/customer_apps/animation_graphics/nichimen.lhtml
a111: Logged on 2018-12-16 05:30 mircea_popescu: that looks 2001-terrible
asciilifeform: mircea_popescu: seems similar enuff in concept
a111: Logged on 2018-12-16 04:24 mircea_popescu: so, dorks with no connections and no resources somehow nevertheless managed to schelling on this. why the fuck ? what ? cuz it's got a cube-like "icon" and 2010 was all about cube-like icons, gotta kubinetes on unity ?
mircea_popescu: https://en.wikipedia.org/wiki/Unity_Technologies << vaguely interesting to the entomologist, i guess. 100% vaporware, shit never worked nor was it ever useful. yet for reasons unclear it received the microsoft treatment, where usg.ibm started throwing money at it for no reason, rather than the http://trilema.com/2015/you-know-what-gets-no-airplay-unflattering-truth/ usual pump-and-dump scam treatment.
asciilifeform: in other noose, phf , mircea_popescu , et al, the bolix is here. dks packs a++ , princely, all parts on manifest , and kilometre of bubbles. will post photos as soon as i wrap up my albatross of this week, ch14
asciilifeform: mircea_popescu: i can't say i have ever encountered this phobia outside of the yudkowsky/reddit/etc weirdos
a111: Logged on 2018-12-15 05:31 mircea_popescu: what's not being discussed is the problem of space debris. but yes, unsurprisingly enough and predictably enough the end result of "people can now go to space" was "earth now looks like a ball of burata looks once the mold can '''go to space'''. ie, surrounded by a skirting of debris,"
asciilifeform: mircea_popescu: approx what % pass the 'omfg it's cut off' litmus ?
asciilifeform: mircea_popescu: it was in trilema piece
a111: Logged on 2018-12-15 05:39 mircea_popescu: http://btcbase.org/log/2018-12-14#1880861 << incidentally, if and when this pays off (which i suspect it will), shall be lulzy to see the "oh, didn't happen, we did it first bla bla bla" morons.
a111: Logged on 2018-12-15 05:35 mircea_popescu: http://btcbase.org/log/2018-12-14#1880841 << if you do, follow hygiene correctly. xraying not unlike ye olde metal foundry technician's job.
asciilifeform: mircea_popescu: you'd want to coat it in luminophore, prolly
a111: Logged on 2018-12-14 22:49 asciilifeform: mircea_popescu: i'ma prolly end up xraying with own hands, i dun trust heathen derps with the jools
asciilifeform: ( ben_vulpes : can haz logging back in #a plz ? )
asciilifeform: mircea_popescu: i'ma prolly end up xraying with own hands, i dun trust heathen derps with the jools ☟︎
asciilifeform: mircea_popescu: believe or not, bolix aint even the least-gettable old/interesting comp
a111: Logged on 2018-12-14 01:57 mircea_popescu: tbh, a recuperative scholarly series on sns would be most apt use of scholar's time.
asciilifeform: mircea_popescu: according to commenter, nsa killed.
asciilifeform: mircea_popescu, diana_coman: re queues filling : per my reading of http://trilema.com/2018/euloras-communication-protocol-restated/#selection-673.0-673.234 , well-behaved clients cannot cause queue to overfill, as it's a synchronous back/forth. so overfilled queue indicates somebody for the chopping block.
diana_coman: mircea_popescu, well, in principle you can run out of space and that'll raise an exception and program dies :D
asciilifeform: diana_coman: 2nd link in post (to asciilifeform's www) malformed
mircea_popescu: "I'm not even sure whether a sender/receiver should be in fact part of smg_comms" << while this has merit, i'd still keep them in.
diana_coman: mircea_popescu, yes
asciilifeform: mircea_popescu: from my reading, diana_coman will have same proggy on 2 boxen, but routine-a runs on box a, and routine-b on b
diana_coman: they are same code except payload_len parameter
diana_coman: create one rsa_sender or one s_sender
diana_coman: mircea_popescu, no
asciilifeform: ( item can be made as mircea_popescu described, either from 2 fifos or 1 priorityqueue. but the latter is actually much moar complicated, in re moving parts, than the former )
diana_coman: mircea_popescu, I thought you got that?
diana_coman: mircea_popescu, what is to happen?
diana_coman: my implementation is just a bounded queue fifo, 1 item at a time in /out; and yes, I looked again at Ada's standard stuff and I could use I think a bounded_synchronized_queue container but then it forces me to put/get full structure
mircea_popescu: yes. diana_coman mind explaining how this works ? so, queue has 55 elements, 22 of which rsa packets. now what happens ?
asciilifeform: diana_coman seems to have an ordinary queue.
diana_coman: i.e. yes, it could have been implemented as mircea_popescu describes if I didn't aim for this specifically
asciilifeform: ( 'priority queue', i believe. but from my brief look at diana_coman's posted item, it dun do this )
diana_coman: mircea_popescu, the way I implemented it it's as asciilifeform says but the reason it is *this* data structure is because of intended use so linked to above
mircea_popescu: diana_coman can you ?
mircea_popescu: diana_coman you did good.
asciilifeform: mircea_popescu: a 'queue' in the usual sense doesn't have a 'pick an X', it has 'pick from top'
diana_coman: mircea_popescu, that's precisely why I made it that way; I suppose it's not clear there at all but yes - because processing of rsa/s is meant to be easily and entirely separated physically, aka machines
asciilifeform: mircea_popescu: how wouldja, e.g., 'these 6 cpus for serpent, these 3 -- for rsa' if yer packets are in 1 queue ?
asciilifeform: ( i thought orig mircea_popescu spec was 'keep rsa packets in own queue, so clearly cap the resource that is spent on'em'
mircea_popescu: diana_coman yes, certainly should provide whatever diagnosis tools and equipment you want. i don't want to fill that in yet, it'll... come to you, as it happens :)
asciilifeform: diana_coman's udp tester was threaded
asciilifeform: mircea_popescu: sorta the philosophy i went with in FG -- redundancy against iron-death error oughta live upstack ( i.e. you plug in >1 ) rather than inside box
a111: Logged on 2018-12-13 19:39 mircea_popescu: diana_coman you proposing it'd be better to resend than ignore ?
diana_coman: mircea_popescu, re ignore vs retry this sent me into confusion-mode: http://btcbase.org/log/2018-12-13#1880648 ☝︎
mircea_popescu: diana_coman that's a very overloaded sense.
mircea_popescu: diana_coman if the socket is in fact closed, your program dies, there's no twowaysabout this.
asciilifeform: diana_coman: my current understanding is that the socket won't ever close, if iron is intact.
asciilifeform: mircea_popescu: there ain't a 'connection' in udpology
mircea_popescu: the idea is udd_ft is 99.999x% 2 and never 1.
asciilifeform: diana_coman: have you managed to achieve the socket-closing eggog without directly abusing the lib ? (e.g. by trying to send oversized packet, etc)
diana_coman: I don't know but given Close_Socket(S), ignoring seems rather ...
mircea_popescu: diana_coman you proposing it'd be better to resend than ignore ? ☟︎
asciilifeform: diana_coman: see what happens when nic cord yank
diana_coman: so raises UDP_Failed_Transmit
asciilifeform: diana_coman: under what condition wouldja get udp lib barf ?
asciilifeform: diana_coman: what sorta errors ? packet is either legit or not, neh
mircea_popescu: diana_coman what errors ?
asciilifeform: mircea_popescu phrased it correctly earlier, point is to remove from ip stack the job of queueing
asciilifeform: mircea_popescu: 1 thread for tx, 1 for rx
diana_coman: mircea_popescu, works, it's a clear decision at least
asciilifeform: mircea_popescu: threaded worker 'rescuing from nic' into queue, and threaded eaters eating from same, is how asciilifeform baked prototype gossip thing from which udplib taken
mircea_popescu: diana_coman so then : a) thin wrappers mosrtly to rescue the queue from ip stack into ram ; b) threaded workers later, which may include but will likely not be limited to, specialist decipherers.
asciilifeform: diana_coman: can send, but then he's a spammer, not client, and gets kicked
asciilifeform: mircea_popescu: in re 'synchronous', it is my understanding that client is not permitted to send a packet unless the n-1'st has been ack'd
a111: Logged on 2018-12-13 19:29 mircea_popescu: diana_coman conversely, if they're that thin why do they exist.
mircea_popescu: diana_coman to proceed logically : 1. it is factual that the expected bottleneck reasonably is de-serpenting. 2. everything-else then may safely be non-threaded. 3. do we actually want to thread the serpenting part ?
asciilifeform: diana_coman: per my current understanding of mircea_popescu's protocol, it is immune to packet loss (i.e. client will retry)
mircea_popescu: diana_coman conversely, if they're that thin why do they exist. ☟︎
asciilifeform: mircea_popescu: i thought your orig queue was specifically re clog (impedance mismatch) in the unix ip stack
asciilifeform: mircea_popescu: even on hypothetical box with 9000 cpus, still no 'clogs', all you get is that the sender waits on the nic. queue cannot overflow cuz your protocol is synchronous ( server dun send anyffing to client unless asked )
mircea_popescu: diana_coman the expectation that serpenting rather than netsending will be the processing bottleneck is not unfounded, imo.