Show Idle (>14 d.) Chans


← 2020-06-16 | 2020-06-18 → ↓
00:57 feedbot http://bimbo.club/2020/06/work-report-6152020/ << Bimbo Club -- Work Report - 6/15/2020
01:04 feedbot http://bimbo.club/2020/06/work-report-6162020/ << Bimbo Club -- Work Report - 6/16/2020
~ 14 hours 3 minutes ~
15:08 jfw billymg: since the #select was formerly done in the themes and I gather now in the 'footnotes' processor, perhaps that would need to be reverted too in one's theme?
15:10 diana_coman http://ossasepia.com/2020/06/01/ossasepia-logs-for-Jun-2020/#1027177 - ah, this rings a bell and I'll need to have a look because iirc I have one level nested replies (though not sure it has anything to do with the theme as such, hm)
15:10 sonofawitch 2020-06-17 03:54:19 (#ossasepia) billymg: diana_coman: ^ the above probably a better answer to your earlier question
15:11 jfw whaack, possibly you have some restrictive 'umask' causing the permissions trouble in the first place, but yes cp -p can be helpful
15:15 jfw Working through the process for a demonstration, deploying TRB in a fresh environment - even knowing where to look for all the pieces - is definitely a pain; and my own wallet too though less so
15:18 diana_coman lol, a more familiar pain with own wallet?
15:18 jfw V alone or at least the one I'm using so far doesn't get you over the hill of 'resolve this project name / key / whatever to a set of files ready to press'
15:19 jfw diana_coman: perhaps, but own wallet has fewer pieces needing to be rounded up so far
15:20 diana_coman that sounds like a script being sorely needed
15:21 diana_coman and a write up afterwards.
15:23 jfw that's probably the practical approach, yeah; but needing a special unique script for this one thing grates. I need a bitcoin-bootstrapper, why? haven't I already bootstrapped a unix and V?
15:25 diana_coman well, that route it's already "why do I need to bootstrap V, haven't I already bootstrapped a unix?" heh
15:27 diana_coman the "why" in the end is simple really - because there's no better alternative available and no, can't wait "however long it takes" until that better alternative is "ready" etc
15:31 jfw "that's how we ended up in this software mess in the first place" sticks in my head but I can't disagree
15:32 jfw comes right back to balancing present vs future costs.
15:34 diana_coman no, it's not that how we ended up in this software mess in the first place, heh
15:35 diana_coman choosing what is as opposed to what one might want is certainly not "how one ends up in mess"
15:36 diana_coman note though that choosing what has to be chosen *now* doesn't mean that it has to remain like that forever or anything of the sort
15:37 diana_coman you can argue perhaps that making a script now lowers the pain and thus makes the problem less visible/easier to ignore - in which case fine, don't make the script and keep the pain until the root trouble gets solved, sure
15:38 diana_coman only I don't think it's your clients who are supposed to either solve it or wait until it's solved.
15:48 jfw I think I get it - or at least I've got as far as I'm going to from chewing on this example.
15:52 jfw this one script won't be creating bigger problems, in itself; my thinking was that by using something you become more dependent on it + the system it's a part of. perhaps that's more a result of using it blindly or allowing that to happen than of the mere use though ("don't blame the drug")
15:56 diana_coman jfw, that is exactly what I mean above by makes the problem less visible to some extent; but this visible always depends inevitable on who and how is looking, heh.
15:56 sonofawitch 2020-06-17 21:37:35 (#ossasepia) diana_coman: you can argue perhaps that making a script now lowers the pain and thus makes the problem less visible/easier to ignore - in which case fine, don't make the script and keep the pain until the root trouble gets solved, sure
15:57 diana_coman inevitably*
16:01 jfw I'm just slower to figure out what I'm arguing then!
16:07 diana_coman well, came to rant and ended up arguing - it might take a while to switch!
← 2020-06-16 | 2020-06-18 → ↑