log☇︎
75800+ entries in 0.046s
a111: Logged on 2018-09-18 13:17 diana_coman: as I was saying earlier: atm the fixed packet length might clash a bit with what I need but it's not even fully clear it's not *better* to have a fixed packet length anyway
a111: Logged on 2018-09-02 02:04 mircea_popescu: well ? how EXACTLY did the entire "torzilla development community" spring up ? what the fuck is a lindsey kuper ?
mircea_popescu: it's obviously enough how laughable monstrosities like http://btcbase.org/log/2018-09-02#1846790 were even produced in the first place. "why does this thing leak more kb/s than an old style modem ?" "because we do all the memory handling inside a live octopus" ☝︎
a111: Logged on 2018-09-17 13:44 asciilifeform: i'ma disagree that '~same' , but this will only be possible to explain once mine's posted.
asciilifeform: btw mircea_popescu , my article is pretty short, should nao be possible to answer the http://btcbase.org/log/2018-09-17#1850792 q mircea_popescu posed. ☝︎
asciilifeform: ( srsly there is no reason for a udptron to allocate anyffing whatsoever , much less to return pointers )
asciilifeform: mircea_popescu: it astonished me how folx were able to so elaborately break such a simple thing.
mircea_popescu: and no "my design, in being inexistent, therefore can not be broken" doesn't work for ideal objects. THESE can be both absent and broken, pandora's blessing.
mircea_popescu: come to think of it, if large bulks of memory have to cross call boundries, something ELSE is almost certainly fucking broken
mircea_popescu: who even does this. in c of all things, what, is it a death wish that can't be otherwise expressed ?
a111: Logged on 2018-09-18 13:05 diana_coman: for completeness, version 3. GNAT.Sockets.Thin that is an Ada wrapper on C system calls containing however questionable approaches (e.g. returning access to String so effectively a pointer but worse than this: allocating memory on the heap and leaving the de-alloc to the caller...)
mircea_popescu: http://btcbase.org/log/2018-09-18#1851102 << this is such, SUCH terribly bad practice, srsly now. scope the fucking memory handling, so both ends always happen in the same context. either the caller allocates and then also deallocates, diana_coman style, or else the callee allocates and deallocates. none of this insane scope bridging jesus christ. ☝︎
diana_coman: I guess what happened is that deedbot gave a lot of voice!!
a111: Logged on 2018-03-23 04:14 douchebag: Okay, why do you guys liek arguing so much? Is this why you guys don't get anything done?
mircea_popescu: and of course, how could one forget to quote the wisdom of the ages : http://btcbase.org/log/2018-03-23#1789029 ☝︎
mircea_popescu: diana_coman: to round this whole thing up: 2 days ago it seemed I had only the gnat.sockets/ thin layer option which wasn't fit for purpose; now I have 2 more options: << it's been an epic few days! (what happened ?)
mircea_popescu: i wonder where he keeps all this voice.
asciilifeform: ( i still have boxen with the old gnat, except for rk, where only ave1's gnat exists )
diana_coman: asciilifeform, ah, I forgot to mention it explicitly but yes, my tests include ave1's gnat as well as adacore's gnat; this is pretty much for any ada code I test
asciilifeform: but this is for the fyootoor, when we start adaizing kernel, perhaps.
asciilifeform: ave1: know what would be neat ? ~raw~ packet support. ( recall mircea_popescu's 'i hate udp' thread )
asciilifeform: ( maybe trinque , if he has time )
asciilifeform: still needs a bigendian test tho.
asciilifeform: incidentally i built an' tested with ave1's gnat, a+++ worx.
asciilifeform: diana_coman: lemme know if you think of further 'why did he do that'-s.
diana_coman: anyways, will give this some more thought
diana_coman: it's not fully clear to me if it's something needed /desired atm; at any rate, compared to where I was 2 days ago, it's great - all of a sudden it went from "need to do this from scratch, ugh" to "there are 2 republican libs with 2 approaches, which one fits best my needs?" ; I'm rather delighted to be honest ☟︎
asciilifeform: incidentally, my lib can be asmed just as readily as ave1 asmed the classical 'all of tcp stack' glue. ( sadly i dun currently have the free hands to do this )
asciilifeform: but yes, you wont get anyffing more detailed than in which unixism was the eggog ( strace will give it to you tho ). idea being. udp does not ever eggog during everyday operation on a correctly configged box
diana_coman: I'd expect that, yes; it was re <asciilifeform> user is told e.g. 'bind eggoged', 'send eggoged', rather than linux-specific whys ( and for that matter, on a working box udp never eggogs , i haven't even any notion presently how to make it , aside from bind()ing a nonexistent local ip)
asciilifeform: slightly under 64k. try it.
diana_coman: re eggogging udp on a machine, perhaps trying to send something above the UDP packet limit I'd say (it's ~64k iirc)
asciilifeform: diana_coman: virtually all nontrivial programs eat or display an ip in txt form somewhere, i've found. incl the demo. hence, included.
asciilifeform: so if your own coad is compatible with this form, can safely jettison the string glue
diana_coman: asciilifeform, the udp lib can request it in a certain format; the rest is layered on top, I don't really see why it needs string representation or eating a string; anyways, splitting hairs on this
asciilifeform: it also shows how to output strings in a civilized way, for n00bz.
asciilifeform: diana_coman: imho that functionality belongs in a udp lib ( given as it demands knowledge of how ip is represented ) but prolly oughta be a troo ada thing, not a callout. however implementing it would double the mass of the proggy
diana_coman: right; in terms of simplicity I can't say atm that I'm able to see anything that can be further cut off from the udp part itself indeed (the string <-> ip part doesn't seem to fit in there necessarily but that's not udp per se anyway)
asciilifeform: user is told e.g. 'bind eggoged', 'send eggoged', rather than linux-specific whys ( and for that matter, on a working box udp never eggogs , i haven't even any notion presently how to make it , aside from bind()ing a nonexistent local ip)
asciilifeform: my approach to eggogology is same as to rest of unix liquishit -- when possible, imprison it, not bring out, so long as proggy behaves reasonably
asciilifeform: observe how the eggogology is organized.
asciilifeform: what i do not do, is to ~distinguish~ all of the,
asciilifeform: diana_coman: imho variable-length-datagram is for the birds. hence i jettisoned good bit of complexity by omitting it
diana_coman: on a different note: I really had trouble coming up with a *full and reliable* set of errors that the UDP ops in linux might throw up; from linux man pages I gathered the unhelpful "all errors from IP may be returned by recv /send" - and looking at that list, it makes for a waaay bigger set than what I see you considered
asciilifeform: can freely experiment, simply turn the knob ( dun forget to turn it on both ends.. ) ☟︎
asciilifeform: but there is also a 'min that will be reassembled on most routers', iirc 580
diana_coman: asciilifeform, myeah, the actual length is likely to be different at the very least, but that's not a big issue
asciilifeform: tho it can be debated exactly which length, as i noted in the proggy
diana_coman: as I was saying earlier: atm the fixed packet length might clash a bit with what I need but it's not even fully clear it's not *better* to have a fixed packet length anyway ☟︎
asciilifeform: 2) 'when i ditch unix, the api should continue to make exactly same amt of sense as before'
asciilifeform: reasoning was twofold, 1) 'want short coad that can be read in half hour'
diana_coman: I can see your point there; it was literally a question to understand the reasoning behind the choice, nothing more
diana_coman: yes, I'm not crying over those
asciilifeform: diana_coman: observe, my lib is somewhat unorthodox, it tries to abstract entirely over the os socket, nails down a fixed packet length, ipv4 4evah, no 'nonblockisms' - who wants these, can implement via ada task; no dnsism supported at all, etc
asciilifeform: diana_coman: afaik the only useful option re udp avail on linux is reuseaddr
mimisbrunnr: Logged on 2018-09-18 12:37 diana_coman: to round this whole thing up: 2 days ago it seemed I had only the gnat.sockets/ thin layer option which wasn't fit for purpose; now I have 2 more options: 1. ave1's ADA implementation of UDP sockets using directly ASM inline 2. asciilifeform's light UDP sockets lib that uses C code for needed UDP sockets calls but provides an Ada wrapper so that any code using the lib can call Ada methods
diana_coman: http://logs.bvulpes.com/trilema?d=2018-9-18#431369 -> refers to http://logs.bvulpes.com/trilema?d=2018-9-16#429804
diana_coman: asciilifeform, any reason why your lib does not support any options at all to be set for the UDP socket?
diana_coman: as it is, the selected minimal set of ops seems ok, except perhaps the fixed message length - I think it's more of a maximum length needed in practice, at least for current version of S.MG protocol
diana_coman: asciilifeform, if I understand your lib correctly, it aims to expose only a strict & minimal set of UDP calls; atm it uses C code for the actual socket part but in principle this layer could be replaced at a later time by some Ada layer while keeping the rest as it is, correct?
diana_coman: version 4. GNAT.Sockets that is built on top of 3. above and mainly serves to force Streams for everything
diana_coman: for completeness, version 3. GNAT.Sockets.Thin that is an Ada wrapper on C system calls containing however questionable approaches (e.g. returning access to String so effectively a pointer but worse than this: allocating memory on the heap and leaving the de-alloc to the caller...) ☟︎
diana_coman: to round this whole thing up: 2 days ago it seemed I had only the gnat.sockets/ thin layer option which wasn't fit for purpose; now I have 2 more options: 1. ave1's ADA implementation of UDP sockets using directly ASM inline 2. asciilifeform's light UDP sockets lib that uses C code for needed UDP sockets calls but provides an Ada wrapper so that any code using the lib can call Ada methods only
diana_coman: asciilifeform, confirmed working nicely with its own tests + adapted client/server test as used previously
diana_coman: thanks asciilifeform! I'll read it and get back to you
deedbot: http://bimbo.club/?p=15 << Bimbo.Club - TMSR Log Summary - 9/07/2018
a111: Logged on 2018-09-17 20:44 diana_coman: the question+kick&ban sounds good to me - kicking "silent" aka "I'm part of it because I hang about in here doing nothing" is even needed by now, I'd say; I can also see very well its usefulness for other channels; while atm #eulora tolerates the allah-spam, it could certainly do without it especially at less-quiet times
lobbesbot: asciilifeform: The operation succeeded.
asciilifeform: !Q later tell phf plox to snarf vpatch in http://www.loper-os.org/?p=2557 , ty
asciilifeform: ^ eventually i'd like to rewrite the human-string routines, and get rid of the unix callout there, but imho errything else prolly oughta stay as is.
lobbesbot: asciilifeform: The operation succeeded.
asciilifeform: !Q later tell diana_coman http://www.loper-os.org/?p=2557 .
mircea_popescu: well, i certainly prefer it to the alternative, whereby ghost-of-mp long after floats about the land
diana_coman: the question+kick&ban sounds good to me - kicking "silent" aka "I'm part of it because I hang about in here doing nothing" is even needed by now, I'd say; I can also see very well its usefulness for other channels; while atm #eulora tolerates the allah-spam, it could certainly do without it especially at less-quiet times ☟︎
asciilifeform: i can't speak for others, but asciilifeform does not find having to unsheath the launch coads erry coupla wks, to be huge headache
asciilifeform: ( this is where it wins over simple 'moderated' chan with hand-curated people list )
asciilifeform: as for the classic voice model, i admit that i like the hidden feature where it causes folx to periodically reassert that they still control their key
asciilifeform: to rewrite the equation, there's a set of folx who have some biznis connecting, and a larger set who do not, and fortunately they are mechanically distinguishable
mircea_popescu: prolly >=1 in there. but anyway.
asciilifeform: aha, same mechanism as trinque presently has for voice filter
mircea_popescu: this may even be feasible, i don't imagine the wotscore lookup is that expensive. i dun see anythinf wrong with it, if anyone's annoying easy enough to fix the score.
mircea_popescu: so you'd want " if you don't, it kicks, and if it kicks you multiple times a day it also bans you." ammended to " if you don't, it kicks, and if it kicks you multiple times a day and your wotranking isn't >1 it also bans you." ?
asciilifeform: nobody needs the 'i'ma lurk here for a year because reading www logs is against koran' types for anyffing, imho.
mircea_popescu: well this'd be it.
asciilifeform: strikes me as orthogonal to the voice q, tho
asciilifeform: ^ i'ma all for the remora ddt.
mircea_popescu: asciilifeform bans are currently free, i don't maintain the list.
mircea_popescu: not that i'm even for a second proposing this is impossible. #eulora famously had one moron who "played" the game for months, merely creating accounts, never actually went in.
asciilifeform: seems to me that items come in 'allcomers' and 'closed wot', and 'allcomers+bans' is simply recipe for whackamole
mircea_popescu: by the time they do that, "why are you not just being normal" becomes quite hte question
asciilifeform: recall the iptables thread ? bans are not a perma-pill, same derps could just as easily go to war with fleanode's nick reg mechanism, get 9000 clean nicks, neh.
mircea_popescu: this is the whole fucking point here, pierce the "convenience" world.
mircea_popescu: the problem with "kick only, no banning" is that the same sort of idle morons that currently idle here would just go to war with the bot with their autoreconnectors ; deedbot would kick the same idiots over and over and oever again, possibly for the next 5 years.
a111: Logged on 2018-09-17 20:05 mircea_popescu: simply have a knob that decides whether {crypto|plain} auth is used ; crypto does what it does now, plain asks a question, "Tell me what color is the sky", picked from a list or somesuch.
asciilifeform: http://btcbase.org/log/2018-09-17#1851024 << 'nonstandard' captchas actually work quite well. ( i have one in the pipeline for my www, which used an ancient heathen service thing that meanwhile died ). there was a famous ru www that had... schoolboy-level integral problems, as 'captcha'. ☝︎
mircea_popescu: it all sprung out from the "how would the deedbot pizarro service look like" consideration.
mircea_popescu: anyway, the point certainly isn't to force people to be more like x, in any case.
mircea_popescu: so i kinda tend to sit at term when ima read logs. maybe this is just my own workflow bias speaking.
mircea_popescu: i personally fucking loathe it, because often i want to answer, and then if i can't i have to savew it, which works poorly.
asciilifeform: aha, was addressing the 'what's the point of reconnectortrons, i want to talk to live people'