log☇︎
4800+ entries in 0.003s
mircea_popescu: no fucking wayu, really this dumb ?!
diana_coman: no "pings" for instance; but that wp_list_comments method has specific parameters at least according to docs
diana_coman: it's mpwp that does same thing in two different ways; all I do is to conform to its different ways; and no; in db the comment_type is (as I checked) with 3 distinct values: empty string, "trackback" or "pingback"
mircea_popescu: the function is just a wrapper on the exact same thing, wp_list_comments('type=comment'); is exactly SELECT * FROM $wpdb->comments WHERE comment_approved = '1' and comment_type = 'comment'
mircea_popescu: you're doing the same thing in two different ways -- one place you ask for an empty type, the other for a "comment" type
diana_coman: in one place it does a direct select in db ; in the other it uses its own function and that has its own parameters
diana_coman: mircea_popescu: that's in mpwp, what can I do if it does same thing in 2 different ways?
mircea_popescu: it's really the same conditional, shouldn't it rather be and comment_type = comment' ?
mircea_popescu: incidentally -- there's a divergence in your patch. on the first heading you say and comment_type = '' but on the second heading you say
diana_coman: well, the way this goes then is simply this - I should have passed the vpatch making on to a more junior person then; because ok, familiarity -> figure the shit out but the fixed cost of vpatch packaging is what it is
mircea_popescu: as the man said, "you wanted me to design a typeface, it takes 10 minutes + a lifetime dedicated to preparing for those 10 minutes"
mircea_popescu: i guarantee you it'd have taken anyone else > 30 minutes to figure the shit out. just because you have the massiva advantage of perfect familiarity doesn't mean so much,
diana_coman: no, it's not about the loc and I specifically did not mention loc.
mircea_popescu: what, should there be more lines ?
diana_coman: code changes that took 30 minutes, lol; not sure how can one define it more precisely in the general like that, it depends on a lot of things after all.
diana_coman: hence the "will have to wait until they accumulate"
diana_coman: mircea_popescu: no, it's neither about the write up (after all, I did it *because* I considered it needed) nor about the 20 minutes on it; it's about the fact that a vpatch containing ~30 hours worth of changes would have taken ~similar in writeup and the rest.
mircea_popescu: maybe the problem here is one of expectations management.
mircea_popescu: arguably a press + vdiff + test press + sign shouldn't be half an hour, but it seems to me by now we're trying to measure the measuring tool, it's not even clear the measurement tolerance is narrower than the width of that "shouldn't". by how much shouldn't it be half hour.
mircea_popescu: now, that time shouldn't be excessive ; but 20 minutes hardly strikes me as excessive, dunno, is the argument here ?
mircea_popescu: honestly it doesn't seem to me the breakdown you have is unreasonable. it will take some time to write things up. this time SHOULD be taken, there's no benefit from "oh, let me mention things vaguely and anti-usefully in the log", it's worse than nothing, it's a cost upon the future.
mircea_popescu: im not saying that lol
feedbot: http://qntra.net/2019/11/man-convicted-of-terror-plot-and-released-in-december-2018-shot-while-stabbing-near-london-bridge/ << Qntra -- Man Convicted Of Terror Plot And Released In December 2018 Shot While Stabbing Near London Bridge
diana_coman: the grating thing being also that the only alternative I see would be "drop it in the logs/blog" as a clue/how-to and then keep searching for it or something.
diana_coman: at any rate, the hour was spent: ~10 minutes figuring out the change and making it directly on my blog so that the results were clear; ~30 minutes for full vpatch process: retrieve+press current v-tree to head; make code + manifest file changes; test press of result & check + final sign; ~20 minutes for write-up + upload + overall final check.
diana_coman: not to mention that I specifically packed more than just the initial change that you were pushing, precisely because of this issue - the overhead on a vpatch means that small but useful changes will have to wait to accumulate.
diana_coman: maybe that is true though I think it shouldn't be.
diana_coman: it can be said also that "well, 2 lines of change taking 10 minutes to do should NOT HAVE BEEN a vpatch"
diana_coman: sure, you can say "you're an idiot, set out your workbench better"; maybe it is that; I think there's more to it though but probably I'll have to find some time to scope it and write it down.
diana_coman: mircea_popescu: mno, it's not just a matter of "tools were not set out properly"; tools were set out and there was no time lost gathering them or whatever; yes, there is some inevitable delay when using key, for obv reason but by now that part is as streamlined as it can currently be.
mircea_popescu: taylorism ftw, half the time the problem's one of "you know, if you set out the tools on the bench BEFORE you got the hot piece out of the oven, rather than run around the smithy holding a chunk of red iron while looking for things..."
mircea_popescu: well, HOW was that hour spent ?
diana_coman: and then ofc something stares me in the face but I can't yet even fully scope it, gah.
diana_coman: should add that I think the problem is relatively superficial ie one of tools as they currently stand, not one of principles.
diana_coman: mircea_popescu: trouble is that it's *not* development that is painful-er, not at all; it's...publishing that is painfuller and I doubt that has any merits.
mircea_popescu: then again, that was pushed through in a different context, maybe needs reexamination
mircea_popescu: well, ideologically the thing stood at "let development be painful-er than entirely painless, it'll produce better code in the end".
ossabot: Logged on 2019-11-29 17:10:06 mircea_popescu: do we have a problem there, is it ?
diana_coman: http://logs.ossasepia.com/log/trilema/2019-11-29#1953885 - tbh I think we do; I've been mulling this for a while ie I'm not happy with the full V setup as it is - at least as it is for me currently - but so far it never made it to the front to push for some solution.
lobbes continues first thing tomorrow, but for now sleeps
lobbes: in other news bracket linking now functional in mpwp logger. Tip of the hat again to asciilifeform, as I ended up lifting his bracket linking code verbatim from the reader.py
ericbot: Logged on 2019-11-29 15:20:21 mircea_popescu: lobbes, except if you do that, i'd rather do it on trilema.com first
lobbes: http://logs.ericbenevides.com/log/trilema/2019-11-29#1953847 << gotcha. So perhaps I can get an initial dump to you for trilema.com (with > march 2016 archives imported), then you can give the final dump to me for trilema.org?
feedbot: http://qntra.net/2019/11/new-zealand-court-refuses-to-allow-access-to-evidence-in-kim-dotcom-case-kim-dotcom-case-still-ongoing/ << Qntra -- New Zealand Court Refuses To Allow Access To Evidence In Kim Dotcom Case, Kim Dotcom Case Still Ongoing
jfw: mircea_popescu: nifty, thanks. Will see if I can accomodate on this pass; otherwise what I'd be working toward is a wallet that's still "declared" but with keys not accessible to node.
mircea_popescu: bvt, yes, but this was also deliberate -- i suspect current v toolset could well benefit from some hardcore usage to iron out inefficiencies, wrinkles and crumples.
jfw: Luby / LT codes? Got a paper on that waiting in a nearby pile, heh
mircea_popescu: this is lubby, at the root of it. look through the log for it, and then read the math. but it's not just math ; it's one of those places where philosophy masquerades as science.
mircea_popescu: jfw, after all, if q = a + b and p = a + c and r = b + c then q + p - r = 2a. if as are addresses and qs are wallets, one needn't ~declare~ his wallet to count his money.
jfw: (or whoever - I'm unclear on the early history there.)
jfw: The necessary index would be large if history is included, perhaps on the order of the existing ones (blkindex.dat), but omitting it strikes me as rather a premature optimization by satoshi.
ossabot: Logged on 2019-11-29 07:32:01 mircea_popescu: jfw, http://fixpoint.welshcomputing.com/2019/gales-bitcoin-wallet-spec-and-battle-plan/#comment-69 << do you understsnd what we're talking about ?
jfw: mircea_popescu: http://logs.ossasepia.com/log/trilema/2019-11-29#1953825 - I think I do now: the ideal node would be able to readily list outputs and thus balances, and perhaps also history, for any given list of addresses, statelessly. Like a block explorer that didn't suck.
mircea_popescu: do we have a problem there, is it ?
diana_coman: so in v time-costs and all that: changes took ~10 minutes including figuring out wtf to change (because I'm no expert in either mpwp or php) and then the rest up to 1 hour was making vpatch + test-press + write-up; pshaw.
diana_coman: fine, let me pack both then.
diana_coman: ah, could be but if I get to that, might as well fix the recent comments too or it ain't worth the gpged, lol.
mircea_popescu: the fix for sorting them at the end
diana_coman: mircea_popescu: this what?
mircea_popescu: diana_coman, this could be a patch, no ?
deedbot: 2019/11/07 02:34:06 <billymg> mircea_popescu: yup, the plan remains, january will be the time
diana_coman: I guess so; but I meant it more as in why default in the genesised mpwp; anyways, perhaps billymg makes a patch to take those out of there and to put also trackbacks/pingbacks as last in comments (I've fixed this on my blog only a few days ago but by default they mix in comments too)
mircea_popescu: at the rate of one trackback each death of a bishop's the bug was never observed.
mircea_popescu: in the original idiot prototype trackbacks function as a sort of assonaut social interaction, the transcription online of the weird talking into the air eyes averted thing they do.
mircea_popescu: because in pre-trilema world articles ~never referenced anything, so nobody understood what a trackback even is.
diana_coman: yeah, that default is annoying, not sure *why* are they there by default
mircea_popescu: dorion, it'd prolly be a good idea to take your own trackbacks out of the (independently --VERY SHORT) recent comments toolbar. i can't tell what's going on
diana_coman: tbh by now I really want to give a spin to jfw's gales thing too and actually see what's there.
mircea_popescu now off to read spyked 's "how and why systemd has won" 2014 piece, kinda curious how 5 years aged it.
BingoBoingo: In pantsuit fail, spammers seem to have captured Central Methodist University's servers
mircea_popescu: this 2 really goes all the way back to the proposed portage supremacy i nixed back in 2018 or w/e it was. NO, portage is not special cuntlet, NO, portage may not be more important than any other turd. V rules, portage obeys or goes away.
mircea_popescu: and 2) really gotta genesis, both the script so people DO have a sane way to make edits, and the sources, so we don't depend on randotards keeping whatever software package online.
mircea_popescu: but in any case multi-gb things can not be called operating systems nomore than run of the mill failboats can be called buttplugs. yes, even if you end up butt-impaled on one somehow ;
mircea_popescu: aaaanyways. my chief takeaways from spyked 's article are that 1) a multi-gb os is a joke, no matter how you turn this. it is deeply unclear to me 1mb is a defensible amt of space for the os to occupy,
mircea_popescu: from what I understand, it's not possible to compile Emacs using Musl << bwahahaha what the fuck
diana_coman: hm, looking now at it, there doesn't seem to be a pingback on trinque's article from mine despite my linking it; weird.
spyked: diana_coman, approved and ty for the link. I knew there was _some_ discussion on that, but I could not for the life of me find it at the time.
diana_coman: and apparently the bits and pieces known/sorted about this are not that easy to find or something, hmmm; esp the paths issue was discussed and sorted in the logs + documented at http://ossasepia.com/2019/07/14/a-working-cuntoo-install-on-amd-fx-8350-with-script/
feedbot: http://thetarpit.org/2019/assorted-notes-on-bootstrapping-cuntoo << The Tar Pit -- Assorted notes on bootstrapping Cuntoo
mircea_popescu: lobbes, except if you do that, i'd rather do it on trilema.com first
ossabot: Logged on 2019-11-28 23:48:45 lobbes: what's left: publish outstanding related vpatches, get base mp-wp and then the bot installed on server, import the remaining logs > 28th march 2016
ericbot: Logged on 2019-11-29 11:37:28 mircea_popescu: http://logs.ossasepia.com/log/trilema/2019-11-28#1953799 << mind that you want a post id > 100k. trilema is in the 90`000s atm. and also, how are we gonna handle the mar 2016 - today log dump ?
lobbes: http://logs.ericbenevides.com/log/trilema/2019-11-29#1953830 << this is a point re: ids. It may make sense for me to first just import your trilema dump and then import my archives
ericbot: Logged on 2019-11-29 11:35:36 mircea_popescu: had some testing in #trilema-lobbes, fucken beautiful. btw lobbes, you intent to implement the square brackets convention ?
lobbes: http://logs.ericbenevides.com/log/trilema/2019-11-29#1953829 << glad you like it :) And yes, I was thinking of implementing the square-bracket convention. It just seems incomplete without it.
mircea_popescu: nice. me too tbh
spyked: mircea_popescu, I pushed a fix to feedbot, lessee how it works. I expect it should send the notifications in the correct order next time
mircea_popescu: lobbes, thinking about it, this is actually just about mature enough i should forward sql dump and filesystem huh ?
mircea_popescu: it's been consistently doing this during [http://logs.ossasepia.com/log/trilema/2019-11-24][logday[.
ossabot: Logged on 2019-11-29 03:31:50 diana_coman: spyked: doesn't feedbot report comments in order? it just reported in pm 3 comments on an article in reverse order (and a couple of hours late by the looks of it)
mircea_popescu: http://logs.ossasepia.com/log/trilema/2019-11-29#1953802 << if it sees more than one new element it reports them in the order seen, which is counter-historical because for some reason rss is newmost on top and obviously irc is newmost on bottom. imo this needs a fix, have the list reversed on feedbot end.
ossabot: Logged on 2019-11-28 23:48:45 lobbes: what's left: publish outstanding related vpatches, get base mp-wp and then the bot installed on server, import the remaining logs > 28th march 2016
mircea_popescu: http://logs.ossasepia.com/log/trilema/2019-11-28#1953799 << mind that you want a post id > 100k. trilema is in the 90`000s atm. and also, how are we gonna handle the mar 2016 - today log dump ?
mircea_popescu had some testing in #trilema-lobbes, fucken beautiful. btw lobbes, you intent to implement the square brackets convention ?
mircea_popescu: trinque, weirdly, deedbot never said anything in response to me verifying http://logs.ossasepia.com/log/trilema/2019-11-28#1953791 ; wasn't it supposed to ?
mircea_popescu: jfw, http://fixpoint.welshcomputing.com/2019/gales-bitcoin-wallet-spec-and-battle-plan/#comment-69 << do you understsnd what we're talking about ?
diana_coman will gladly read the humongous cuntoo write-up.
spyked: aaand should be fixed. will test next time notifications queue up like that
spyked: diana_coman, np, thanks for reporting the issue
ossabot: Logged on 2019-11-27 14:58:06 dorion_road: The other priority areas of ownership to clarify : c library, boot process (bios, bootloader, init), userland, install process, process supervision and logging and package management options beyond ebuilds.