Hide Idle (>14 d.) Chans


← 2020-03-18 | 2020-03-20 →
dorion: http://logs.ossasepia.com/log/ossasepia/2020-03-19#1022284 - yeah, forgot about that. enthdegree, you'll have to pm diana_coman when she's available, 19 UTC is her regular time here. make sure you have a key registered though.
ossabot: Logged on 2020-03-19 01:04:50 lobbes: I think he needs voice from ChanServ anyways
ossabot: Logged on 2020-02-09 20:13:49 diana_coman: and for any newcomers and log readers: please register first a key with deedbot (see the guide: http://www.eulorum.org/Account_Setup) as otherwise it's unlikely you'll get voiced in here.
diana_coman: hello enthdegree , what brings you here?
diana_coman: re deedbot I suppose I'll have to roll my own too since I'll be damned if after all of it I'll just go about re-doing all the ritualic dances too.
diana_coman: so meanwhile consider the requirements slightly relaxed and take advantage of the situation while it lasts.
diana_coman: ritualistic*
diana_coman: (for the log, the ritualistic dance in this case goes like this: something is promised; naive person awaits for it; nothing happens; naive person asks about it and promise is reiterated; still nothing happens; on it goes)
diana_coman will be back later.
trinque: diana_coman: see, over here it looks like "ex-soviet bellows demands, offers nothing in return" as the prime cultural offering of once-tmsr.
trinque: I told you what, two days ago, that deedbot needed to be modified a bit to support multiple channels.
trinque: in *all of you* from the soviet system there's "narcissism for me; altruism for you"
spyked: heh. I'll be pedantic (and besides the point) and say that in particular the Ro system looked closer to dprk than the soviets, but... yeah.
diana_coman: trinque: you know, if I meant to target you with that , I'd have pinged you; no, I mean it way more general as an approach and it rests on my incoming-review (that will still take some time because myeah, loads of work)
trinque: at any rate, the changes to deedbot are minimal, certainly not of the "design an OS" scale.
diana_coman: trinque: where exactly did I bellow any demand from you? because the way it reads from here is that you gave in to your own brand of hubris and grand-words above with ex-soviets and all that.
trinque: I read above something I offered turned into homework on which I'm late.
diana_coman: trinque: no, I don't do implicit like that, aka "it's obvious", so no.
trinque: anyhow. deedbot is running in both #deedbot and #trinque, so that part works.
trinque: next step is the wot calculations, and seeing that e.g. voicing in one channel does not in the other, etc
diana_coman: trinque: what's the reason you are doing this deedbot update & roll out anyway?
trinque: multi-channel deedbot is the next best approximation of a distributed http://wot.deedbot.org/
diana_coman: ok, but what's your plan with that or you know, why sink time into it?
diana_coman: http://logs.ossasepia.com/log/ossasepia/2020-03-19#1022304 - btw, esp in the light of all my recent re-reading of past-tmsr stuff, this is particularly infuriating in its blindness and informed-by-own-feelings.
ossabot: Logged on 2020-03-19 09:57:03 trinque: in *all of you* from the soviet system there's "narcissism for me; altruism for you"
trinque: "everyone is a secret wrecker but me" also extremely infurating.
trinque: stan also does this.
diana_coman: what's a secret wrecker?
trinque: I just went on a dive for the thread, didn't find.
diana_coman: and what the fuck does stan have to do in this conversation?
trinque: I really have no idea how to read what you said as other than "trinque ain't bringing deedbot"
trinque: but whatever.
diana_coman: http://logs.ossasepia.com/log/ossasepia/2020-03-19#1022318 - I can see this being infuriating (working with some guess as to "secret wrecker"); I have no idea though how does it relate to me; does it relate to me?
ossabot: Logged on 2020-03-19 10:17:50 trinque: "everyone is a secret wrecker but me" also extremely infurating.
diana_coman: trinque: so why not *ask*, man? how the fuck am I supposed to guess what you read in it/can't read in it? I meant specifically that I won't ask people for stuff.
trinque: to answer your earlier question, I am working on deedbot because I wish to help keep some cohesion in former-tmsr as it devolves.
trinque: deedbot has long been a bad prototype of a gossipd node, making it an incrementally less-bad prototype
trinque: diana_coman: I guess there are things we're all furious about, then. thanks for explaining.
diana_coman: thank you for the clear answer; and indeed re prototype of gossipd node, I can see it.
trinque: nonzero chance of another great depression after all this money printing and panic.
trinque: which is sort of ironic. kinda reminds me of the biblical revelations thing, where by the time christ comes back, nobody believes in him, or w/e.
trinque: point being, the use-case for bitcoin might become abundantly clear real soon.
diana_coman: sure; still too late.
trinque: we're certain to find out either way.
trinque: https://www.opentable.com/state-of-industry << I was struck recently by how uniform the reaction looks in this dataset, came up on w/e news orifice.
diana_coman: http://logs.ossasepia.com/log/ossasepia/2020-03-19#1022305 - lolz, I missed this but I have to say I disagree on both counts really.
ossabot: Logged on 2020-03-19 10:00:51 spyked: heh. I'll be pedantic (and besides the point) and say that in particular the Ro system looked closer to dprk than the soviets, but... yeah.
trinque: it seems like when there's something real to fear, human behavior is quite rational.
trinque: even among the derps.
trinque: it'd have to be for there to any derps in the first place, I'd claim.
diana_coman: trinque: not sure how you link "uniform response" to "rational".
diana_coman: spyked: now I wonder if you imagine #trilema and #ossasepia as exercises in narcissism of the two respective owners; is that what you're saying?
spyked: diana_coman, not at all. I was discussing the soviet/dprk thing besides trinque's point. but I was just thinking, where does one draw the line between "personality cult" and "protecting the elite among one's group"? I can certainly see the narcissism angle, although I don't personally abide by it.
diana_coman: I am even quite curious so if anyone cares to make a coherent case for #ossasepia being about my narcissism, I'd certainly read it; as already stated, I won't ask even for this but I'd certainly read and comment on it.
diana_coman: spyked: do you realise that the "personality cult" is not the doing of the person at the centre of it? ie if everyone strived to *immitate* MP, it's *their doing*, not his, wtf.
diana_coman: this is pretty much the old "they whistle after her -> she's a whore!"
spyked: no argument here
trinque: diana_coman: I do not wish to trade insults. I took you as taking a shot at me, and I accept that you weren't.
diana_coman: re soviet/dprk, on one hand the reality in Ro was quite different depending on whether industrial town or not (talk to some from each type of town and you'll notice - if no heavy industry, it was nowhere near as horrible in a day to day sense)
diana_coman: and otoh, if you talk to people from the proper soviets, it's pretty much a matter of timing.
trinque: I don't buy the idea that the leadership has nothing to do with a personality cult, though.
trinque: leadership authors culture, doesn't it?
diana_coman: trinque: I don't quite follow your full reasoning there and atm I need to go so - do you mind if we get back to this around 7pm UTC?
trinque: sure, I'll be around all day.
diana_coman: cool; laters then.
spyked: diana_coman, agreed re. reality. I was thinking more about the ideology (as outlined in the july theses, for example)
diana_coman: spyked: I confess I'm quite ignorant regarding dprk's ideology
diana_coman: I suppose it can be though.
diana_coman: trinque: assuming you referenced there the what is art (which I don't dispute), I still don't see how you get from there to the personality cult
jfw: http://logs.ossasepia.com/log/ossasepia/2020-03-19#1022291 - tyvm lobbes. That spot didn't have pre-2016 when I last checked (during the "trilema goes dark" incident), and I missed where phf announced that.
ossabot: Logged on 2020-03-19 01:10:33 lobbes: jfw: actually, phf still has those old logs up it seems
ericbot: (trilema) 2019-08-09 phf: there's no need to znc, the entire archive of logs is available here: http://btcbase.org/log-raw/ with 2016-03.txt being the last kako file. the only outlier is tmsr-logs-apr2012-oct2013.txt which is the dump mircea_popescu gave me of the prehistoric logs, which i have a custom reader for.
dorion: hi diana_coman, making progress over here. thrown out a couple drafts that read a bit to much as before. cutting to the chase more on my latest iteration.
diana_coman: dorion: focus always and even start with the things you actually do/did, yes; even if it ends up as the middle in your article/draft, there's no problem and it helps to start with what you did because that's surely what you also know best, obviously.
diana_coman: lobbes: is that apr2012-oct2013 the only part currently missing from your logger's webpage?
diana_coman: iirc mine is also missing some part in the beginning and I guess it's that one (haven't looked at it in ages and I don't recall now)
dorion: thanks. right now I'm starting with the problem. the biggest problem we're aiming to solve computer security. this allows me to incorporate mp's prior advice : http://logs.ossasepia.com/log/trilema/2020-01-24#1957236 , http://logs.ossasepia.com/log/trilema/2020-01-24#1957237
ossabot: (trilema) 2020-01-24 mircea_popescu: so my proposal is rather to look at the matter not as much as you're in the business of TEACHING LINUX (while getting together), but in the business of GETTING TOGETHER (while for instance teaching linux, or gales, or bitcoin, or whatever is needed)
ossabot: (trilema) 2020-01-24 mircea_popescu: build it around the relationship, their building, their lifecycle, their needs. do not build it around the imaginary "point", that isn't.
dorion: I'm still detailing the hardware/gales/training package, but making it clear that's not all we do.
diana_coman: dorion: from what you say as such, it sounds fine indeed; and sure, what problem you solve is part of what you do, obviously.
dorion: http://logs.ossasepia.com/log/ossasepia/2020-03-19#1022347 - I see it more as you're interested in creating relationships and helping pe
dorion: ople become more effective in achieving their goals. Pretty much all you've demanded so far is they commit to consistently improving the
ossabot: Logged on 2020-03-19 10:53:16 diana_coman: I am even quite curious so if anyone cares to make a coherent case for #ossasepia being about my narcissism, I'd certainly read it; as already stated, I won't ask even for this but I'd certainly read and comment on it.
dorion: themselves*
lobbes: http://logs.ericbenevides.com/log/ossasepia/2020-03-19#1022353 << I think March 28th 2016 is the starting point for at least your logger and mine. (I haven't confirmed this on alf's, but I think his too starts at this date).
ericbot: Logged on 2020-03-19 19:15:31 diana_coman: lobbes: is that apr2012-oct2013 the only part currently missing from your logger's webpage?
diana_coman: dorion: thanks for stating it.
diana_coman: lobbes: ah; somehow I recall the raw archive and I'm pretty sure I have it; possibly there was some trouble at import and I never got around to sort it, nor really added it to the todo list.
diana_coman: lobbes: do I take it that your bot imports everything from 2012 on?
lobbes: diana_coman, no, only from 2016 on
diana_coman: (because I'd really not "solve" stuff if there's no need for it; there's plenty to solve without adding to it things already solved)
lobbes: mp imported those old logs from his personal logs
trinque: diana_coman: I don't think mp was curating a personality cult.
trinque: I made the claim that leadership authors culture, is all.
lobbes: but, if we move to use the new blog-logger then he technically has all the data we'd need (just a dump from his mysql)
jfw: diana_coman: the trouble was precisely that the raw-log archive only started at 2016-04.txt (actually the tail end of March) when asciilifeform built his logger and nobody online at the time had earlier except via lossy scraping.
trinque: I also totally agree with your "catcall doesn't make her a whore" comment
trinque: so I'll think on this more
diana_coman: trinque: ok.
diana_coman: lobbes: so what was with that custom reader you said you made/had? I'm confused now.
lobbes: diana_coman: I have the reader, but MP has the full dataset. Since the original plan was that once he gets everything imported to trilema.com, I'd then be running a server with a copy of his data
diana_coman: oh, I see; ok, I'll just ask him for a dump and sync with that when everything else is in place, not a problem.
lobbes: nice :)
lobbes: I'll be happy if this thing actually turns into.. something at least
lobbes bbl in a few
jfw: I've been working through bvt's v.sh part 1. Not sure if I'd class it as a luxury or necessity in this case but either way the inline commentary is appreciated. mod6's v.pl may have great usage docs, but has zero code-level comments; rather a regression from the original v.py it seems to me.
jfw: Got some questions queuing up, some of which have resolved themselves on further reading so I'll keep at that for now.
jfw brb in 10 mins
diana_coman: jfw: that's how it usually goes with questions in my experience too so yeah, possibly worth finishing first one read and then asking whatever questions are still standing.
jfw: right
diana_coman will be back tomorrow.
whaack: I am attempting to produce the list of channels I've successfully logged for (at least) 2 weeks without a disconnect lasting longer than N minutes. I have logs that contain the bots' JOIN / DISCONNECT timestamps for various channels. I need to run a postgres command with the psuedocode "list all channels whose first JOIN is > 2 weeks ago, excluding all channels that have a DISCONNECT without a
whaack: following JOIN that occured within N minutes.
jfw: whaack: something's missing from that pseudocode
jfw: also dunno if it's a terminology difference between your code or cl-irc and irc protocol, but in the latter you PART or are KICKed from a channel, disconnect isn't an irc message
whaack is thinking about what's missing.
whaack: jfw: It's a terminology difference. I considered myself connected when I receive a "JOIN" message from irc, and so I used the same term "JOIN" to denote connection to a channel. I use the term "DISCONNECT" because I can be disconnected from a channel for various reasons such as being KICK'd or losing connection to the network.
jfw: what do you consider yourself when you've connected to the server but not yet joined any channels then? :P but suit yourself I suppose
whaack: Here is the data http://paste.deedbot.org/?id=0dXY (and I realize I actually use "JOINED" rather than "JOIN")
whaack: Right, better names could have been used. I also did not log the event of connecting to the server.
jfw: re the pseudocode, just compare it to your stated goal in the same line
whaack: argh sorry, I actually do specify KICKs with KICKED
jfw: uh, you do distinguish KICKED from DISCONNECTED though! -yep.
whaack: (so first correction is excluding all channels that have a DISCONNECT _or KICKED_ without a following JOIN...)
dorion: hey jfw check pm real quick
whaack: jfw: Another problem with my pseudocode is that if I have a channel I joined 3 weeks ago that the bot successfully logged for 2 weeks, but then disconnected during the 3rd week, I would erroneously exclude that channel.
jfw: right.
jfw: whaack: I'll add that this sounds like a pretty tricky thing to do purely in SQL. You're looking at differences between subsequent events, which seems much better fit to a ...list-processing language (even if just awk) than a set-processing one :)
jfw: but maybe I'm just a sql-noob and there's a nice way, would love to see it.
whaack: jfw: I was planning on taking the intersection of the channels that matched the above criteria with the channels I am *currently* connected to. There is a case where I don't properly log the DISCONNECT message - when the bot crashes. I am concerned that there is another case where I may stop logging a channel without receiving a KICK/DISCONNECT message that I have not considered.
jfw: whaack: do you think the intersection solves that problem?
jfw: if considering all disconnect cases is really too hard, maybe look for where the time since last message from a given server (irrespective of channel) exceeds a given timeout
jfw: that'll be prone to false positives of course.
whaack: jfw: No the intersection is not really a solution. Perhaps taking that intersection and seeing if it even reduces the original set at all will give some evidence of a problem, but it won't do more than that.
jfw: I'd have thought the bot would automatically move on to the next channel in the queue after 2 weeks thus it'd be more concerning if there *wasn't* a reduction there (dunno how long it's been going though)
jfw: anyway I'm off for now.
feedbot: http://ossasepia.com/2020/03/19/the-soap-rush-and-the-toilet-roll-bubble/ << Ossa Sepia -- The Soap Rush And the Toilet Roll Bubble
whaack: jfw: thanks. atm there is no functionality to automatically rotate through channels.
← 2020-03-18 | 2020-03-20 →