[02:37:31] <bd808>	 DatGuy: your URL to api.php is wrong. It should be /w/ not /wiki/. For the meta question, once you have an access token you can store it and reuse it until the user revokes access. 
[02:37:49] * bd808 sees a typo in the readme for https://github.com/wikimedia/mediawiki-oauthclient-php too
[02:40:43] <Reedy>	 fixit!
[02:40:57] <bd808>	 Reedy: working on it :)
[12:00:19] <DatGuy>	 bd808: when I try to save the accesstoken in SESSION it gives me an 'invalid signature' problem
[14:03:05] <DanielK_WMDE>	 to whom it may concern: https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Call_for_Nominations
[14:26:11] <DatGuy>	 or well, actually, it seems like it can't find the token
[14:52:32] <DatGuy>	 never mind, found the problem. was looking into 'statustoken' instaed of 'setglobalaccountstatustoken'
[16:33:56] <DanielK_WMDE>	 oh, gotta love flow. it just replaced my comment with "Unable to transfer content: Error contacting the server for conversion between wikitext and HTML. Please check your Internet connection or try again later if the problem persists. If you still get this error please file a bug"
[16:34:07] <DanielK_WMDE>	 i see no way to get mack what i wrote.
[16:34:09] <DanielK_WMDE>	 what the fuck?
[16:35:17] <bawolff>	 lol
[17:17:54] * apergos has no comment on flow
[17:18:02] <apergos>	 none whatsoever
[17:18:06] <apergos>	 not a single one, nope.
[19:02:19] <p858snake>	 DanielK_WMDE: LQT4Lyfe
[19:06:46] <DanielK_WMDE>	 p858snake: *sigh*
[19:06:57] <DanielK_WMDE>	 I *support* the idea. It's just broken :(
[19:07:46] <James_F>	 DanielK_WMDE: Interesting. Did you switch to wikitext and back?
[19:10:54] <Krenair>	 anything interesting in JS console?
[19:13:24] <DanielK_WMDE>	 James_F: no. i edited wikitext, and tried to save.
[19:14:17] <DanielK_WMDE>	 i'm afraid i closed the tab in disgust after losing the edit. sorry
[19:14:30] <Krenair>	 if you reopen the tab and do the same thing does it happen again?
[19:15:10] <DanielK_WMDE>	 one thing i can tell you is - i was editing an old version of the page
[19:15:27] <DanielK_WMDE>	 i had it open since last week. the thread was edited since then. i didn't reload before replying
[19:16:24] <DanielK_WMDE>	 Krenair: no, i can reply to the message now. i didn't try with the same text, though. i don't have it any more. it was longish. about a screenful of wikitext.
[19:17:00] <Krenair>	 depending on the nature of the error you might be able to get someone to dig it out of some logs somewhere?
[19:17:31] <DanielK_WMDE>	 the error was probably just a timeout. i hit a few of those around that time.
[19:17:42] <DanielK_WMDE>	 but the error message *replaced the content*
[19:17:47] <DanielK_WMDE>	 *that* was screwed up.
[19:18:01] <DanielK_WMDE>	 earleir timeouts (on a different page) did not do that
[19:18:33] <DanielK_WMDE>	 perhaps you can track down the error message, and check how it makes its way to the client when it is triggered.
[19:19:55] <DanielK_WMDE>	 I'm off for today. I'll be sure to investigate if it happens again.
[19:24:02] <James_F>	 DanielK_WMDE: Ah. Interesting. Could be breakage around oldid changing and it not being able to cope? I know that area is fragile.
[19:24:38] <James_F>	 In general way too much of MW relies on in-channel communication about exceptions (return the count of X, or -1 if you couldn't work it out, etc.)
[19:27:00] <Platonides>	 DanielK_WMDE: maybe you could recover the text from the browser memory
[19:27:29] <Platonides>	 it hurts when hard-working text disappear due to a page error
[19:30:40] <DanielK_WMDE>	 James_F: i would have been less surprised/annyed by an empty string, or "null" :)
[19:31:09] <James_F>	 Indeed.
[19:31:11] <DanielK_WMDE>	 Platonides: i'm not going to attach a debugger and fish for it in RAM ;)
[19:31:23] <DanielK_WMDE>	 anyway, ttfn