Young Hands
21h 42m30m30m13d 18h 16m4d 18h 43m16d 20h 46m8m

spyked: <-- ohey, thanks! re. xml parser, it's stolen off github, but code was small enough for me to read and understand in ~1 week
ossabot: Logged on 2019-10-28 13:35:21 jfw: spyked: I thought it was pretty cool that feedbot, at least from first glance, is parsing xml in lisp rather than binding to C libs like every other language I've seen does it. And I look forward to more reading time in your tarpit, once I'm a bit more unstuck from my own.
spyked: <-- I also hit this problem, sounds like an apache access control issue. iirc there's a .htaccess in wp-includes/wp-admin that needs some tuning.
ossabot: Logged on 2019-10-28 13:41:32 jfw: diana_coman: I noticed* are returning 403, which slows the page load and probably breaks some kind of admin functionality. I don't mind disabling JS on the whole domain - loads faster, more secure and all - though this would mean some gadgets like the word counter and autosave won't work
spyked: <-- lol, fair point. tbf, that particular secretary was always helpful rather than a hindrance, as opposed to the general image of harpies hired for that job.
ossabot: Logged on 2019-10-28 19:53:07 diana_coman: - spyked, for the life of me, I can't call those secretaries at upg "ladies" lolz; you really are too polite.
spyked: I also worked with some of the harpies at one point, found out that they're overworked and underpaid, as per general chaotic "organizational" pattern in upb. looking at things from that point of view, it's hard to blame 'em now.
diana_coman: spyked: the access on is more lax because of multiple authors from wherever etc; + the "rape & pillage good for highschool" lolz.
diana_coman: spyked: if you publish though your recipe re .htaccess tuning, I'll read and apply if it fits the trouble, ofc.
diana_coman: re harpies though, no, this "oh, we are overworked and underpaid so we'll steal from students (yes, they did, there was a whole thing with the transport reimbursements) + we'll therefore take it on students because we can" is precisely the sort of bullshit that *is* the very problem in the first place; if they are overworked and underpaid, they should *leave*.
diana_coman: there is absolutely no excuse there.
diana_coman: spyked: you know, this "oh, but see it from my point of view, how hard I have it" smacks of ~rezistenta prin cultura ; (and so my blood boils already at 9 am, lolz).
spyked: eh, they've nowhere to leave, they're basically another version of the peasant subsisting on welfare. which means that yes, they'll be overworked and underpaid for years to come now
spyked: diana_coman, had no idea they stole from students, but I don't find it surprising either. their boss and their boss' boss also steals from some bag or another, so this just perpetuates down the hierarchy. I wouldn't be surprised to hear the cleaning staff steals toilet paper, lol.
diana_coman: spyked: nope, there is no such thing as "nowhere to leave" either; loads of land that nobody works because "it's not worth it" so what "nowhere to leave".
diana_coman: and in general, this is what they'll always say, of course, of course, "oh, but there was *nothing else* I could do, poor me".
diana_coman: note also that the one helpful exception you mean somehow could not-be a harpie though surely just as "underpaid and overworked", no?
diana_coman: spyked: re toilet paper, probably they do, yes; but there is no way I'll buy into this passing the buck either up or down; it's again the "oh, it's owned by the state aka by nobody and therefore we can all steal, let's see who is the idiot who still does some work so we can *also* laugh at him", yes?
diana_coman: so no, it's irrelevant if their boss steals too or whatever; they are still responsible individually, there is no we, what.
spyked: re. leaving, yes, their barriers are 100% self-imposed. it's prolly in the job description too.
spyked: diana_coman, I meant that they most likely learned that habit from their boss. but otherwise sure
diana_coman: eh, they "learnt" it as in they saw that they can get away with it just fine and therefore did it, what learnt.
diana_coman: sure, precisely the sort of "dobitoaca dracului" , that much I agree.
diana_coman: and in unexpected milestones: we have 1st spam (bitcoin advizee for ze millenial inveztorz!!) on! congrats and all that, if I get any time today I'll write it up already.
bvt: spyked: typically they work there for years and see what can be done without getting caught. at some point they start doing stupid shit (subtly sabotaging work) just out of boredom - not like they the work they do ever changes
spyked: bvt, not sure how it goes elsewhere, but in ro they have this elaborate pretense of "public vacancies", where e.g. two people must compete for the job in order for the vacancy to be filled; in reality however the jobs are created on-demand for people who are brought in by relatives etc. (e.g. one of the admin. directors is the dean's cousin). hence my point above that everyone's in on it.
spyked: <-- yeah, I guess it depends on what policy you wanna enforce. I have a .htaccess in my wp-includes/js/ that looks along the lines of ; afaik the default setting for mp-wp is to block everything
ossabot: Logged on 2019-10-31 06:12:12 diana_coman: spyked: if you publish though your recipe re .htaccess tuning, I'll read and apply if it fits the trouble, ofc.
diana_coman: spyked: certainly; and I'd gladly burn the *whole lot* of it & them; (now you know just why I didn't want to go and give talks or whatevers there).
diana_coman: the trouble not being that much that they are brought in, but that they are brought in *to steal and pretend*, nothing more.
shinohai: Nothing like waking up in the morning and reading irc logs where diana_coman wants to burn stuff. It's gonna be a great day.
diana_coman: lolz, what would that do for you shinohai, anyway?
bvt: imo this is irrelevant detail, in places where there actually is a competition stuff is ~same (even if there is no stealing). one of profs at our university recently moved to another city because he could not fire his own secretary, who was messing to much with the chair
shinohai: I dunno, I just imagine you as some sort of modern Olga of Kiev, wreaking havoc on enemies with fire and brings smile to my face.
diana_coman: bvt: ahahaha; but I can imagine it, yes.
diana_coman: shinohai: lol! I'll add it to the collection then.
shinohai: It'd make a fantastic addition to Eulora - birds of fire appearing at snap of finger to immolate enemy.
diana_coman: eh, dream on re snap of fingers.
shinohai: Hilariously, didja notice now redirects to diana_coman ?
diana_coman: no idea and it doesn't really matter either.
whaack: jfw: my table prefix was not the issue (it was set to mpwp_) The problem was occurring because the sql statement used for the archives widget doesn't work with the mysql version i am running, 5.7.27
diana_coman: o.O I thought you had solved that yesterday whaack , didn't realise it was still dragging on; is it solved now?
whaack: i did solve it yesterday and then went to bed, just now responding to jfw
diana_coman: ah, ok.
whaack: diana_coman: there is a decent bit I have to say on html linking itself before I address the separate personal issue I have with allocating my time to research how a tool works before i use it. I think it makes the most sense to make two posts, one addressing each of these points
diana_coman: whaack: all right, no problem there at all
jfw: diana_coman: I report with some trepidation that I didn't finish my outline last night. It wasn't distraction, more of a sulking state where I know I gotta, but something in me just doesn't wanna; then somehow I got unwedged and it started to flow. Clearly a time waste and I dunno what to say other than it's a long standing pattern with my writing and I want to fix it. Gotta focus on other things
jfw: now but I'll get back to it with urgency tonight and remind myself not to pre-optimize.
jfw: whaack: I was gonna say I'd probably been talking nonsense there and maybe check your mysql & php versions? -- but too late; glad you solved it then.
dorion: << login was successful.
ossabot: Logged on 2019-10-30 17:55:32 dorion: << thanks, I've got the cyphertext, not going to be near my key until later this evening. I'll update once I've logged in.
dorion: diana_coman how long should my review stretch this week? since I applied ~2 weeks ago?
diana_coman: dorion: whichever you prefer there.
diana_coman: jfw: treat the sulking state with a big ignore and - if need be - force writing ie just *write continuously* whatever until sulky-you can't stand it anymore and rather than keep at nonsense will back off.
dorion: diana_coman aok, thanks.
whaack: diana_coman: from what i read about the new html linking, it seems there may exists a tool that will find appropriate values for the query parameters b & e. however I did not find that tool on the post/in the logs, afaik the values need to be hand crafted. the closest thing i found was the code for xmlrpc on the post, which haphazardly finds a value for b to include in the link back to the source sending a pingback.
diana_coman: whaack: where did you read of a tool exactly?
whaack: diana_coman: it was hinted at in the lines "no one needs javascript to produce a selection" (although that could be because you can craft them now by hand) and hinted at in the linked discussion b/w alf and mp
diana_coman: whaack: link please
whaack: i was wondering if this 'selector' was created and i had not found it
diana_coman: whaack: not done, no.
diana_coman: and not worth doing as stated there either in my opinion.
diana_coman: ie not in js.
whaack: okay ty.
whaack: lol til after hitting 'save draft' on a mpwp post with html characters escaped, the escaped characters are evaluated to their html characters, thus hitting 'save draft' twice in succession can alter the content of a post.
diana_coman: ugh.
BingoBoingo: whaack: Is this in the html view or the vestigial visual editor?
whaack: BingoBoingo: in the html view. afaik the most recent mp-wp patch does not contain the visual editor.
whaack: s/the most recent mp-wp patch/mp-wp pressed to the most recent patch/
diana_coman: whaack: add that to your post on the html linking please; a concrete example would be best, too.
whaack: diana_coman: will do.
whaack bbl
billymg: whaack: i have run into this same bug myself. the problem is html renders "escaped" html characters as their symbols. e.g. if you initially input something like "&lt;p&gt;" to render a <p> tag it will get saved as such in mysql. but when you edit the post, and the same "&lt;p&gt;" is pulled out of the db and put into the text area, it will render as "<p>"
billymg: so saving again saves the "<p>", not the "&lt;p&gt;" you originally entered
whaack: billymg: yup, that is my understanding of the problem
billymg: this might be helpful
billymg: running the db output through that before inserting into the <textarea> converts everything to html entities. so tags you intended as tags, e.g. <p>, go into the <textarea> as &lt;p&gt; (rendered as the desired <p>), and tags you intended to escape, e.g. &lt;p&gt;, go into the <textarea> as &amp;lt;p&amp;gt; (rendered as the desired &lt;p&gt;)
billymg: would certainly be a useful patch if you have the time to test further and ensure it works as expected without side effects
billymg: also provided diana_coman finds it a worthwhile use of your time i should say
whaack: billymg: ^ hah that is always a given. yes it seems like a good idea at first pass
whaack: lobbes: i am working on a solution to this . you don't want to put any string for the b query param that is going to match a string inside of an anchor tag. this problem occurs frequently because often the same text in a link you want to select is inside of the anchor tag: i.e. for the text 'mp writes at <a href="">trilema</a>' if you try to select trilema w
ossabot: (trilema) 2019-10-31 lobbes: in other weird, I found an odd (albeit edge case) bug in the new blog selection mechanism. If you do a select that begins with "http" (e.g. "?b=http&e=#select") it will mangle the selected link in the post itself when rendered
whaack: ith b=trilema you will break the anchor tag instead.
whaack: the other weird about the new selection mechanism is that when you leave no value for e, there is no closing </span> being added anywhere. afaik all browsers handle this by 'closing' the <span ..> tag by putting a </span> before either the next (1) the opening tag of a block element (2) the closing tag of any element that the <span ..> opening tag is nested in
lobbes: whaack: aa interesting. I didn't know that about the no value for e; now that weird makes sense at least
lobbes: and nifty. I look forward to your solution (possibly this was in the #o logz already and I missed it)
whaack: lobbes: there is no solution proposed yet. the first two fixes that came to mind are to (1) make sure that you are not inside of an anchor tag when putting in the opening <span> and (2) to make sure you put the </span> explicitly if you hit one of the above scenarios before finding a match for the "e" value
jfw: - I had also encountered this
ossabot: Logged on 2019-10-31 18:33:26 whaack: lol til after hitting 'save draft' on a mpwp post with html characters escaped, the escaped characters are evaluated to their html characters, thus hitting 'save draft' twice in succession can alter the content of a post.

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