jfw: http://logs.ossasepia.com/log/ossasepia/2020-03-17#1022184 - those darn prophecies: would I have finished it today if he hadn't said that?
ossabot: Logged on 2020-03-17 04:48:43 dorion: maybe you will get that saturday review afterall jfw, lol.
jfw: I was pretty distracted / unfocused today. But at least I get to bed before 2am. Small steps back toward a routine.
jfw: spyked: I tried a "!1subscribe http://trilema.com/feed/" to feedbot now that's no longer delivered via #t; it responds "Please provide a valid feed URL".
jfw: lobbes: in that log import project you ever get a hold of the pre-2016 ones (ie. #b-a) in a raw form? It's the kinda thing I'd like to have around and afaik phf never shared what MP had given him to seed btcbase.
dorion: jfw I think you need a space between the 1 and s
spyked: for some reason it didn't like "naked" tags (the trilema feed contains an empty "dc:creator" tag that it previously didn't?) so it croaked suddenly. ftr, I rewrote one of the feed parsing functions in a haste, so I'm not discounting the possibility of further bugs
spyked: will reload this fully in head later, re-read and publish patch
dorion: hey spyked, good to hear from you.
spyked: hey dorion
spyked: btw, in case feedbot PM seems too annoying: #spyked is still set to notify on all the feeds from #trilema, plus a few others; but I can also add them here (or elsewhere) if e.g. diana_coman finds it useful
diana_coman: hi spyked , long time no see
diana_coman: I still have #trilema feeds in PM; now that the log dump is finished I don't expect it will be any trouble as it is, really
diana_coman: that being said, when I get around to do all updates, I'll see.
spyked: hi diana_coman ; ok, lemme know when/if you need any updates to the #o rss
diana_coman: thanks & will do.
diana_coman: http://logs.ossasepia.com/log/ossasepia/2020-03-18#1022242 - lolz, blame it on cassandra nao? jfw, anyways, roll it now together into the one at the end of this week and just review both; only do it by Friday better and be done with it.
ossabot: Logged on 2020-03-18 03:23:08 jfw: http://logs.ossasepia.com/log/ossasepia/2020-03-17#1022184 - those darn prophecies: would I have finished it today if he hadn't said that?
diana_coman waves
dorion: hi diana_coman
diana_coman: hi dorion, how's the draft coming along?
dorion: still working the plan where we left off yesterday.
diana_coman: take the time it takes.
jfw: hi diana_coman. roger on rolling up the review, thanks.
diana_coman: jfw: np; what are you working on this week anyway?
dorion: I got distracted yesterday by a) family business (both parents work at hospital, virus panic kicked in yest) and b) and patching a relationship locally with a guy I had trouble with about 17 months ago or so.
diana_coman: I see.
jfw: Some more articles to write for the blog, overdue housekeeping in the vein of reading more of the V publications, deciding on a keccakized one, testing the keccakized trb tree, and time permitting, that 'gypsy key' and ledger genesis. Also we have another unix + management Saturday session on the calendar.
jfw: Reviewing dorion's draft(s).
dorion: diana_coman for the what we've done opening of the draft, I'm proceeding from university to present at a high level with links. i.e. what we've done as individuals prior to jwrd, leading into the feature offering of jwrd, i.e. the hardware + software + training package.
diana_coman: dorion: iirc from yesterday there was the idea of having a clear statement of the problem you are solving there, so hopefully it fits in your outline above; other than that sure, go ahead and write it so that there's something to look at and talk about; there's not all that much to say just on an outline at that level.
dorion: diana_coman right, what we've done, the problem and our solution, clients who have had success, and how to work with us.
jfw: isn't the "what we've done" more about what we've done about the particular problem rather than our whole backstories? At least for the intro.
dorion: that will certainly cut to the chase much faster.
diana_coman: dorion: jfw is right above; you can still give a very brief background but usually that's a bit to the side ie a sort of short bio for each at the bottom or something
dorion: very glad I asked.
diana_coman: cool, getting to grips with those question-tools!
diana_coman will be back tomorrow
jfw: spyked: thx for fixing, the subscribe worked now.
dorion: hello enthdegree
dorion: enthdegree, better to chat in the channel than pm.
lobbes: I think he needs voice from ChanServ anyways
lobbes: http://logs.ericbenevides.com/log/ossasepia/2020-03-17#1022160 << thanks. It is bittersweet of course (I can't help but think "if I didn't suck maybe it would've extended the shelf-life of tmsr a bit longer"), but it'd have been worse if I didn't even manage to get a log dump to him
ericbot: Logged on 2020-03-17 02:57:01 dorion: lobbes congrats on getting the job done.
ericbot: (trilema) 2019-10-09 mp_en_viaje: you saved them.
lobbes: http://logs.ericbenevides.com/log/ossasepia/2020-03-18#1022231 << March 28, 2016 is as far back as I have for #t logs (I think this is the case for all three 'stan loggers' currently live)
ericbot: Logged on 2020-03-18 06:21:47 jfw: lobbes: in that log import project you ever get a hold of the pre-2016 ones (ie. #b-a) in a raw form? It's the kinda thing I'd like to have around and afaik phf never shared what MP had given him to seed btcbase.
lobbes: though I believe alf may have the older phf logs.
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.