Young Hands
31m1d 20h 24m72d 19h 18m3h 4m19d 8h 35m1d 16h 27m6h 9m

feedbot: << Young Hands Club -- JFW review, week of Jan 13 2020
feedbot: << Young Hands Club -- JFW plan, week of Jan 20 2020
feedbot: << Young Hands Club -- RMD review, Jan 11-19th, 2020
feedbot: << Young Hands Club -- RMD plan, Jan 20-24th, 2020
diana_coman: dorion: you do like living dangerously, don't you.
dorion: diana_coman while I've definitely taken my share of risk - some smart, some dumb - I know I can improve the balance of the ratio in favor of more smart risk.
diana_coman: dorion: some unbalance in that direction may be even better! but yes, setting yourself up for less dumb risk will do wonders and on more fronts than one really.
dorion: for sure. set up to let compound interest of smart risk accrue.
diana_coman: dorion: note the difference there between your stated "more" (risk, be it smart) and my "less" (dumb risk); while "more of smart and less of dumb" may be the theoretical ideal, the practice is best served by focusing on the "less" first; it also makes for more calm and less stress really.
dorion: diana_coman makes sense++
diana_coman: dorion: so how's that Hawaii article going wrt to the current deadline for it?
dorion: diana_coman good. not sure if it'll be out before I sleep tonight, but good chance it will.
diana_coman: iirc deadline is tomorrow so that sounds fine, glad to hear it; and no need to rush/skip the final review either.
dorion: yes, deadline is tomorrow.
diana_coman: whaack: why were the bots kicked in the first place anyway?
whaack: diana_coman: this i have not yet investigated.
diana_coman: when you say they were kicked do you mean you looked and ~all were kicked or do you mean you saw some kicked and so "bots were kicked"?
diana_coman: whaack: well, before "fixing" it, you *have to* investigate what the fuck the problem is in the first place, you know?
whaack: diana_coman: I looked on one VM and I discovered I was banned from ~all of the 7-8 networks I had connected to. Then I looked into a few networks and saw that my bots had been kicked from channels and were constantly trying to rejoin them.
diana_coman: hrm, now there's even a sf story for you but finish the odyssey or it'll take longer than it took ulysses by the sounds of it.
diana_coman: whaack: the same on other VMs or was there only one connected?
diana_coman: this is quite important too because ahem, if you don't figure out and solve it, there's not going to be much systematic anything there.
whaack: diana_coman: I was running bots on two VMs and iirc yes the same thing happened on the other VM (checking now)
diana_coman: there was my previous clear statement re if kicked let the chan be but mk, test run and all that.
ossabot: Logged on 2019-12-19 16:41:24 diana_coman: let it join, what; collect data for 1 month and then see; if it gets kicked from a chan, let the chan be, not like I want to force anyone now out of the hole they enjoy, what.
diana_coman: whaack: any reason given on first kick? because the ban makes sense afterwards given the kick/rejoin dance, ofc.
whaack: I just checked, on the other VM I was banned from 3 networks w/ errors: "ERR_YOUREBANNEDCREEP: snup97 "You are not welcome on this network. G-Lined: join/part spam. Email for more information."" and "NOTICE: snup97 "*** You are banned from GeekShed (You are banned from GeekShed for 8d! Reason: Malicious bots, clones and drones are prohibited by the Network TO
whaack: S." and "NOTICE: roco44 "*** You are banned from P2PChat (either stay on or off (3 days))""
diana_coman: so hm, join/part spam aka...connection flicker??
whaack: no I think the join/part spam is more likely from the kick/join dance
diana_coman: no data re kicks themselves?
whaack: there should be data .. i have to dig for it
BingoBoingo: Maybe the bots need girl names and an Eliza plugged into them?
diana_coman hands whaack a shovel.
diana_coman: BingoBoingo: eh, I'm not (yet) trying to take over all chans too!
whaack: lol
BingoBoingo: Well, something to do call/response
diana_coman: they can certainly say hello but I doubt that's the issue really
diana_coman: and at any rate, it's not like all networks are invited to dump all their issues for whaack to have what to address.
whaack: diana_coman: The query "select message, networkname from irclog where irc_message_type='CL-IRC:IRC-KICK-MESSAGE';" gave me the following results from vm1 and from vm2
diana_coman: ahahaha
diana_coman: "You have been found co-channeling in one or more blacklisted channels"
diana_coman: oh the lulz
diana_coman: but not that much variety, hm.
whaack: I notice that it was only from 3 networks that I received kicks. But my fleetlogs show that on one VM i have 4354 disconnects and 4440 joins
whaack: so there is likely something else causing the disconnect/reconnect dance. or i'm getting kicked from channels without receiving an irc-kick-message.
diana_coman: whaack: well, overall it sounds like you should first understand a bit better just what exactly your bots are doing there and how, really
diana_coman: I mean: there's so much fun to be had there but you do need to be better at it than their lame efforts, seriously.
whaack: btw, i didn't implement the reconnect-on-kick feature intentionally. with cl-irc you set a nick to have a list of channels, and i found out cl-irc automatically rejoins the nick to a network when kicked. I will have to explicitly remove the channel from the nick's list when it gets kicked.
whaack: diana_coman: what do you mean by I need to be better at it than their lame efforts?
diana_coman: anyway, fix so it doesn't reconnect on kick for starters; get to the bottom of that 4354 disconnects vs 4440 joins, if at all possible; add whatever additional logging you need to have full information on hand and preferably timely delivered too; maybe start with a smaller trial that you can monitor more closely to figure out what's going on, if needed
diana_coman: whaack: well, their "fighting the oh-noez-spam-not-ours" is from what I see a combination of "oh, you won't answer me???" and that co-channeling lulz; the rest is just repetition really.
diana_coman: well, unintentional implementation is ....
diana_coman: and anyways, their bans are for some number of days, can even rotate etc.
whaack: alright I'll take BingoBoingo's advice and see if adding an Eliza-light will help
diana_coman: but it's not yet even clear it's worth the effort
diana_coman: whaack: first of all get to the bottom of the connect/reconnect and kick/not kick, anyway; eliza-light comes afterwards and only if really justified.
whaack: diana_coman: btw do you have a way you'd like me to select the channels? I sorted by the most popular channels and joined those first...that was not because I thought that was a particularly good idea in the general case - but because I was mostly testing networks that had ~0 activity in anything but the more popular channels
diana_coman: it makes sense since otherwise you'd see empty lines anyway so not much gain; that's not a problem there
whaack: ^ alright i'll publish a plan to address the above this evening / tomorrow midday.
diana_coman: whaack: is the whole code clear to you now how and why it works and what is going on in there?
whaack: diana_coman: my code and trinque's irclogger are clear to me. (btw trinque did you look into the reconnect bug I pointed out? I will confirm there's a problem and publish a vpatch for it later this week if I get the time.) how cl-irc handles certain things is a bit of a blackbox.
ossabot: Logged on 2020-01-04 22:56:08 whaack: trinque: I think I may understand this if you never got around to it. The thread that normally calls ircbot-reconnect is the ircbot-ping-thread. However the ping-thread commits suicide because ircbot-disconnect calls (sb-thread:terminate-thread (ircbot-ping-thread bot)) . So when the ping thread calls ircbot-reconnect after calling ircbot-disconnect it never gets to the ir
diana_coman: whaack: is cl-irc that huge/gnarly that it's a huge project to look and find out how it handles those exact certain things that you don't know about but need?
whaack: diana_coman: no it is comprehensible. 4.5k LOC and there is a lot of handling of portions of the irc protocol i don't need to look into.
diana_coman: whaack: so then look into it, since you are relying on it for the whole thing.
whaack: (4.5k LOC _and_ from my understanding it does not import any external libraries)
diana_coman: let eliza be for the moment; it might be a good idea but it will get evaluated when the problem and its extent are clear, not just slapped on now because "it seems like a good idea" , ugh.
whaack: (ah nvm it does use three - :split-sequence :usocket and :flexi-streams)
diana_coman: ahaha, it did sound rather too good to be true, lol.
whaack: alright, no eliza
diana_coman: whaack: enough work there to keep you busy ? clear enough so you know what you need to do?
whaack: certainly the former, and yes I think I have a good idea of what to tackle next and how to go about it.
diana_coman: cool then.
whaack: the other major item in the pipeline today is the plan for my computer
diana_coman: anyone else in need of work around here? speak up, there's plenty to pass around!
diana_coman: whaack: wasn't there some article too?
whaack: diana_coman: yup that is done, just needs to do the final review
whaack: i just need*
diana_coman: good then; any trouble re plan for your computer?
whaack: i don't think there should be, but i haven't made a meta plan lol
diana_coman: whaack: ahaha, no, no need for that or you'll loop forever in the meta-metas; I simply meant if you needed to clarify anything on that front.
whaack: diana_coman: no, although I am not sure how much detail I need to go into for how I go about building the computer. Do I need to spell out how all the cables are going to be laid in what directions + what gets zip tied to what?
whaack: Currently I'm thinking I list all the parts I need to install, what order I install them in, and what items i will need / have available in order to do their install. I also will include any important installation notes for various pieces.
diana_coman: whaack: no need for cable-level of detail, no; whenever in such doubt, focus on what the goal of the plan (or whatever it is you are working on) really is
diana_coman: that's where everything else should come from; so: what's the goal of this plan of yours?
whaack: diana_coman: The goal is to ensure I have what I need and know what to do in order to execute a timely, safe, and proper build of my computer.
whaack: safe means I don't open up the possibility of breaking something, and proper means I don't make a mistake that requires me to do undo a bunch of work to fix.
diana_coman: whaack: so then, does that require a list of what gets zip tied and cable directions? (it might or it might not, but it's your decision since you defined the goal of what you need, so ..up to you)
whaack: diana_coman: right...that's why I asked, I'm not so sure. There are certain cables that must be laid out before installing other parts. So I think yes I will have to consider some of the cable layout in my plan.
diana_coman: whaack: so then consider it, sure; it's *your* plan and it should serve you best, first and foremost.
BingoBoingo recommends saving zip ties for last. Otherwise there's opportunities for friction as you plug and unplug cables in search of the cleanest routes, the friction being cutting and placing new zip ties.
whaack: ^ noted
diana_coman: aha, not a bad idea; and in general, tidying stuff neatly up tends to be at the end precisely because otherwise it might get untidy again before everything is done.
BingoBoingo: You also don't want to be putting any cables under unnecessary tension. Once you're satisfied all cables are plugged in with a comfortable amount of slack, then zip tying can begin.
diana_coman: oh hey, nice photos, whaack ! and you basically showed Panama City more than jfw and dorion so far combined, ha! takes a non-local to publish photos of a place, it would seem.
whaack: diana_coman: aha that's how it goes I guess. I have ~no photos of NYC.
BingoBoingo: So much more glass and height than Montevideo has.
diana_coman: BingoBoingo: more recent former money place I guess.
BingoBoingo: diana_coman: Likely.
BingoBoingo: I suspect Uruguay's generally less accomodating to height variance requests leading to 10 to 12 storey canyons on a number of streets.
BingoBoingo: Anyways, my experience here is that the visitors have always come with fresher eyes. It doesn't seem to take much time for the visual landscape anywhere to start feeling normal.
diana_coman: BingoBoingo: if by normal you mean "perpendicular" (to my disposition at times if to nothing else), I'll fully agree to that - it doesn't take much time at all!! lolz
BingoBoingo: diana_coman: By normal I mean, the brain starts applying a "this place is familiar" filter over what they eyes are sending it. There seems to be a window first arriving in a new place where the brain's "Everything in visual range is new!" gets the shutter button on the camera moving.
diana_coman: BingoBoingo: I got what you meant, just being amused otherwise because despite knowing what you mean, I am - if anything - even less able to take a decent picture of something new than of something more familiar.
BingoBoingo: Well, sometimes things are both new and familiar. The local Afro cultists might leave a dead chicken in a new place, but once you've seen enough chickens left in odd locations...
diana_coman: lol, that's one sort of new and familiar, can be.
BingoBoingo: It's not even surprising anymore either. The flies give it away everytime, because it's almost rare to see flies in Montevideo outside of the specific situation.
jfw: whaack: y'know, if cl-irc turns out to be some kind of eldritch horror, there is also which fits both irc client and UI in 2.5k lines. The irc parts could quite likely be isolated for use as a bot. Though I don't expect changing languages would be cheap for you at this point.
jfw: or for that matter there's asciilifeform's log bot too, though looks like it's not set up to handle any message types besides ping and privmsg.
auctionbot: S#1077 O=17mn LB=None E=2020-01-29 05:43:03.567830 (189h28) >>> Dell R610 PE Server ships from U.S. (Server-A)
auctionbot: S#1078 O=17mn LB=18mn E=2020-01-29 05:43:42.679910 (189h28) >>> Dell R610 PE Server ships from Uruguay (Server-B)
auctionbot: --- end of auction list, 18mn total bids ---

Random(ossasepia) | Download daily DB snapshot | Get Source Code