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 ?
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.
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: 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 ?)
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
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
☟︎ 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)
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)
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
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)
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
diana_coman: asciilifeform, myeah,
the actual length is likely
to be different at
the very least, but
that's not a big issue
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
☟︎ diana_coman: I can see your point
there; it was literally a question
to understand
the reasoning behind
the choice, nothing more
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: 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
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.
lobbesbot: asciilifeform:
The operation succeeded.
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
☟︎ 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." ?
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.
mircea_popescu: by
the
time
they do
that, "why are you not just being normal" becomes quite hte question
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.
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.