[02:23:12] <logmsgbot>	 !log LocalisationUpdate completed (1.20wmf8) at Sun Jul 29 02:23:12 UTC 2012
[02:23:24] <morebots>	 Logged the message, Master
[02:45:34] <logmsgbot>	 !log LocalisationUpdate completed (1.20wmf7) at Sun Jul 29 02:45:34 UTC 2012
[02:45:43] <morebots>	 Logged the message, Master
[16:41:27] <uwe77>	 I've found a bug in the commons upload script, but i am to stupid to explain it in english. Where can i place the bug in german?
[16:42:35] <DaBPunkt>	 uwe77: ask for help at WP:FZW
[16:42:55] <uwe77>	 where? long version please
[16:43:29] <uwe77>	 i did not unterstand
[16:43:52] <DaBPunkt>	 uwe77: Bitte auf http://de.wikipedia.org/wiki/Wikipedia:FZW um Hilfe beim Ausfüllen eines Bugreports
[16:44:01] <uwe77>	 ok, thanks
[16:44:10] <DaBPunkt>	 no problem
[16:58:38] <anarcat>	 hi
[16:58:40] <anarcat>	 i am looking for irc.wikimedia.org 's recent changes channels, is it down?
[16:59:40] <MatmaRex>	 hi guys
[16:59:54] <MatmaRex>	 is it just me, or does 1.20wmf8 beak <source> tags rendering?
[17:00:01] <MatmaRex>	 e.g. see https://en.wikibooks.org/wiki/C_Programming/Variables
[17:00:23] <MatmaRex>	 there are huge margin added to the top and bottom of the code
[17:00:26] <MatmaRex>	 margins*
[17:01:23] <MatmaRex>	 the trouble is caused by "white-space: pre-wrap;" applied to .mw-code
[17:01:48] <MatmaRex>	 see eg https://bits.wikimedia.org/en.wikibooks.org/load.php?debug=true&lang=pl&modules=skins.vector&only=styles&skin=vector&*, the huge comment starting with "Wrap properly." and the next two lines.
[17:01:49] <Platonides>	 I see
[17:02:03] <MatmaRex>	 who do i poke to have this fixed before all wikipedias are broken as well?
[17:02:27] <MatmaRex>	 minimal fix is to add ".mw-code{white-space:inherit}"
[17:04:26] <Platonides>	 you should bug krinkle, who is the committer
[17:04:45] <MatmaRex>	 where do i poke him?
[17:05:10] <MatmaRex>	 (i dont even have gerrit account or however you guys call it)
[17:05:21] <Platonides>	 I'm not sure if you should reopen https://bugzilla.wikimedia.org/show_bug.cgi?id=260 with that
[17:05:24] <Platonides>	 or create a new bug
[17:05:30] <Platonides>	 probably reopening it
[17:05:42] <Platonides>	 even though it is already gigantic
[17:05:59] <MatmaRex>	 eh
[17:06:03] <MatmaRex>	 and maybe it will be unbroken by hte next deployment?
[17:08:29] <Platonides>	 iif it's only adding that line, it should go in without problems
[17:08:55] <MatmaRex>	 well, that line is not exactly a pretty fix
[17:09:02] <MatmaRex>	 actually that whole chunk of code is pretty weird
[17:09:03] <Platonides>	 if it would break something else, it may stay or be reverted
[17:09:21] <MatmaRex>	 i dont know why we apply the css to both pre and .mw-code, when <pre> is always placed within .mw-code
[17:09:46] <MatmaRex>	 at least it is on the pages i looked for
[17:09:59] <MatmaRex>	 i dont know how <souce> works internally
[17:10:07] <Platonides>	 it's an extension
[17:10:34] <MatmaRex>	 yeah, and we might have non-default config on the wikimedia wikis, etc, etc
[17:11:01] <MatmaRex>	 the line i posted doesnt break stuff at least on pl.wikibooks, as far as i can see
[17:18:41] <MatmaRex>	 alright. i'm reopening bug 260, then
[17:19:24] <MatmaRex>	 wait
[17:19:28] <MatmaRex>	 can i even reopen it?
[17:20:39] <Platonides>	 I suppose so
[17:20:41] <Platonides>	 can't you?
[17:20:48] <Platonides>	 are you logged in into bugzilla?
[17:21:17] <MatmaRex>	 yup
[17:21:23] <MatmaRex>	 i only have the additional comments field
[17:21:27] <MatmaRex>	 and i can add myself to cc list
[17:21:35] <MatmaRex>	 i dontsee any other form fields
[17:21:42] <MatmaRex>	 or am i just being stupid and its somewhere else?
[17:22:13] <Platonides>	 it should be below the comment box
[17:22:15] <Damianz>	 You don't see an edit next to the status or a dropdown next to posting the comment button?
[17:22:45] <Platonides>	 Status: RESOLVED FIXED     Save changes
[17:23:06] <Platonides>	 if it's not there, you can't
[17:23:23] <MatmaRex>	 nah
[17:23:25] <MatmaRex>	 i'm on https://bugzilla.wikimedia.org/show_bug.cgi?id=260
[17:23:36] <Platonides>	 we strengthed the account rights some time ago
[17:23:43] <MatmaRex>	 yeah, i probably dont have any
[17:23:56] <MatmaRex>	 i think all i ever did on bugzilla was report a bug and co mment on one other
[17:24:31] <MatmaRex>	 uh, so can one of you do it for me? and just copy my ramblings from earlier there?
[17:25:19] <Platonides>	 just add the comment
[17:25:31] <Platonides>	 I'll then reopen it for you
[17:29:57] <MatmaRex>	 done
[17:30:01] <MatmaRex>	 Platonides: ^
[17:30:28] <Platonides>	 reopened
[17:30:40] <Nemo_bis>	 Brooke et al: is "E-mail me when a page or file on my watchlist is changed" actually set to true by default as a preference?
[17:31:17] <Nemo_bis>	 I assumed so but it isn't if I restore default settings on a random account
[17:31:32] <Brooke>	 I don't think it's set to true.
[17:31:34] <Brooke>	 By default.
[17:31:35] <Nemo_bis>	 so I don't understand how https://bugzilla.wikimedia.org/show_bug.cgi?id=36316 could have sent that many emails
[17:31:39] <Brooke>	 It'd be kind of annoying if it were.
[17:31:49] <Platonides>	 not in mediawiki
[17:31:50] <Platonides>	 	'enotifwatchlistpages' => 0,
[17:31:50] <Nemo_bis>	 how so?
[17:32:20] <Nemo_bis>	 one can disable it when watchlist grows to big (ie never for like 99.95 % users)
[17:32:23] <Platonides>	 it could be on wmf configuration
[17:32:33] <Nemo_bis>	 no it doesn't seem to be
[17:32:59] <Brooke>	 Well, you can make a bug for flipping the default.
[17:33:12] <Brooke>	 I imagine most users don't understand a watchlist.
[17:33:35] <Nemo_bis>	 sigh
[17:34:20] <Nemo_bis>	 jdforester triggered this check btw, he wrote me «I assumed that when I created an account "e-mail me about pages I»
[17:34:23] <Nemo_bis>	 watch" was switched on, as per most other instances nowadays.
[17:35:14] <Nemo_bis>	 because I feel like filing new bugs which will stay around for years, I'll file one more
[17:36:20] <Brooke>	 That's called winning.
[17:36:26] <Brooke>	 You're winning Bugzilla.
[17:42:06] <Nemo_bis>	 hmmm
[17:42:27] <Nemo_bis>	 many of use are winning bugzilla
[17:43:10] <Nemo_bis>	 https://bugzilla.wikimedia.org/reports.cgi?product=MediaWiki&datasets=NEW&datasets=FIXED&datasets=DUPLICATE
[17:43:50] <Nemo_bis>	 (I was so satisfied that I got this chart to work)
[17:44:09] <Brooke>	 I didn't even know Bugzilla had charts.
[18:04:30] <Nemo_bis>	 Platonides: how is "Add pages I create and files I upload to my watchlist" in MW master?
[18:04:46] <Nemo_bis>	 it's true by default on WM projects, but doesn't exist as an option on TWN
[18:06:15] <Reedy>	 It's possible to hide/remove preferences
[18:07:17] <Nemo_bis>	 Reedy: where?
[18:07:21] <Nemo_bis>	 didn't find it in the config
[18:07:25] <Nemo_bis>	 bug filed https://bugzilla.wikimedia.org/show_bug.cgi?id=38796
[18:07:48] <Reedy>	 $wgHiddenPrefs = array();
[18:07:52] <Reedy>	 /** An array of preferences to not show for the user */
[18:07:55] <Nemo_bis>	 oh right $wgHiddenPrefs[] = 'watchmoves';
[18:35:31] <Nemo_bis>	 aah, it's our config: if( $wgDBname != 'commonswiki' ) { $wgDefaultUserOptions['watchcreations'] = 1; }
[18:41:34] <Nemo_bis>	 I suspect https://bugzilla.wikimedia.org/show_bug.cgi?id=13619 won't go anywhere
[18:46:33] <Brooke>	 What's wrong with being explicit?
[18:46:58] <anarcat>	 is it normal if irc.wikimedia.org is down?
[18:47:14] <Brooke>	 anarcat: No.
[18:47:24] <anarcat>	 okay, is it just me then? :)
[18:47:33] <anarcat>	 i was looking for the recent changes irc feed
[18:47:39] <anarcat>	 i'm that kind of crazy junky
[18:47:44] <Brooke>	 It's not down.
[18:47:47] <anarcat>	 crap
[18:48:02] <anarcat>	 duh, okay, it's me, sorry!
[18:48:07] <anarcat>	 it was my proxy blowing things
[18:52:49] <Nemo_bis>	 Platonides: assuming you know how to se gitweb or whatever way better than me, can you give me a direct link to the portion of the parser linked here? https://bugzilla.wikimedia.org/show_bug.cgi?id=18443#c7
[20:30:15] <BarkingFish>	 evening guys.  Can someone possibly tell us what the new part of the URLs is for on enwp please? we're getting &pe=1 turning up in them, I saw it earlier and didn't understand it either, and now someone else has commented the same.
[20:33:55] <Jarry1250>	 BarkingFish: This came up on VPT
[20:34:02] <Jarry1250>	 it's a "post edit trigger"
[20:34:32] <Jarry1250>	 Which will do absolutely nothing except for new registered users
[20:35:00] <BarkingFish>	 ah.  So what is it designed to do? 
[20:35:10] <Jarry1250>	 Speaking of which, I think that's StevenW area of expertise
[20:35:14] <Jarry1250>	 *'s
[20:35:18] <StevenW>	 Hey
[20:35:31] <StevenW>	 You guys talking about the post-edit feedback experiment?
[20:35:32] <Jarry1250>	 BarkingFish was just asking about &pe=1
[20:35:36] <Jarry1250>	 Yup
[20:36:20] <StevenW>	 Yes, there's details on VPT, but you can ignore it safely. 
[20:36:24] <BarkingFish>	 StevenW, I noticed it earlier, and TBloemink picked it up a few moments ago. I was sort of wondering what it was intended for.
[20:36:48] <BarkingFish>	 Ok then StevenW - since TBloemink is in here, I have no need to tell him now :)
[20:36:54] <BarkingFish>	 Thanks for the info
[20:36:57] * TBloemink  was double pinged

[20:37:01] <TBloemink>	 Thanks for the information
[20:37:04] <Jarry1250>	 StevenW: I still don't understand why you can't just $wgOut->redirect(...) it out ?
[20:37:39] <StevenW>	 The purely technical parts are something that I'm not skilled enough to answer, not being a developer myself.
[20:37:57] <Jarry1250>	 Fair enough, I'm not familiar with the extension myself
[20:38:07] <Jarry1250>	 It just doesn't sound like something that would be difficult to do
[20:38:09] <StevenW>	 But my guess to that specific workaround is that the bucketing and tracking for the experiment is all done on the client side via JS, not in the extension's PHP
[20:38:52] <StevenW>	 The best documentation about this test if anyone's interested is at https://www.mediawiki.org/wiki/Post-edit_feedback
[20:39:18] <StevenW>	 but we will announce more details tomorrow on VPT, and there's always a list of active experiments at [[WP:E3]] on ENWP.
[20:39:31] <StevenW>	 BarkingFish, TBloemink ^
[20:39:31] <Jarry1250>	 StevenW: Who would be a technical contact on that?
[20:39:41] <TBloemink>	 okay
[20:39:49] <BarkingFish>	 yeah, I'm reading mediawiki.org's docs on it
[20:40:13] <StevenW>	 Ori Livneh. If he's online you can find him at ori-l on IRC. He's usually here in wikimedia-tech and wikimedia-dev
[20:43:31] <BarkingFish>	 he is online right now, can't tell on which nick, it's either ori-l or atdt
[20:44:31] <ori-l>	 I'm here
[20:44:51] <ori-l>	 TBloemink / Jarry1250: catching up, just a moment.
[20:46:52] <ori-l>	 Jarry1250: what would $wgOut->redirect do that's different?
[20:47:27] <Jarry1250>	 ori-l: Something to get rid of the &pe= section that's confusing everyone
[20:48:29] <ori-l>	 Jarry1250: but where would you redirect to if not the article page? and how would you signal post-edit state to the client except by adding a query param?
[20:49:17] <Jarry1250>	 ori-l: Well, firstly, this seems to be appearing to people who aren't in the target group.
[20:49:17] <ori-l>	 apologies if i'm being daft.
[20:49:36] <Jarry1250>	 So surely you could just drop the parameter if the user wasn't in the target group?
[20:49:54] <Jarry1250>	 I think that's the main thing that's intriguing me here
[20:50:30] <ori-l>	 Jarry1250: i'd rather deal with each issue in sequence rather than jump around. if we move on to this, should i assume $wgOut->redirect would be an improvement after all?
[20:50:40] <ori-l>	 wouldn't, rather
[20:50:49] <ori-l>	 if you still think it would be, could you explain?
[20:51:15] <Jarry1250>	 That was my proposed solution before Steven correctly pointed out you're doing most of this in JS so it wouldn't work
[20:51:34] <ori-l>	 oh, okay, sorry -- i missed that
[20:51:42] <ori-l>	 let me answer your other question then
[20:52:40] <ori-l>	 the short answer is yes, you could drop the parameter for people not in the experiment, and that would almost certainly be cleaner.
[20:53:03] <ori-l>	 the slightly longer answer entails a slight detour, which i hope you'll brook
[20:53:11] <Jarry1250>	 ori-l, sure, go on
[20:54:24] <ori-l>	 the E3 team is tasked with designing and deploying experiments that are 1) short-term and 2) provide insight on editor engagement and retention
[20:55:19] <ori-l>	 we therefore consciously optimize for insight and development speed, occasionally at the cost of committing kludges
[20:55:52] <ori-l>	 our assumption is that everything we do will be disruptive and annoying to some extent. the sheer fact of having different interfaces for different users is confusing.
[20:56:09] <ori-l>	 imagine a new editor came on irc and asked about this pe=1 and you had no idea what they were talking about.
[20:56:45] <ori-l>	 our conviction is that the payout from the insights generated by these experiments will offset the annoyance
[20:57:33] <Jarry1250>	 ori-l: Oh, I get the generals. But I think the specifics here point towards a five minute fix
[20:57:44] <Jarry1250>	 I say five minutes, I mean, I image it is.
[20:57:50] <Jarry1250>	 I haven't actually checked.
[20:58:42] <ori-l>	 Jarry1250: but the fix would come at the cost of debuggability
[20:59:13] <Jarry1250>	 Hmm?
[20:59:17] <ori-l>	 Jarry1250: deploying it to everyone makes it easier for us to test and means that if there are any problems, they'd get picked up very quickly by savvy members of the community.
[21:00:18] <Jarry1250>	 Oh, I though Steven said non-new editors +anons weren't int he target group so nothing would happen for them?
[21:00:19] <ori-l>	 deploying an experiment requires quite a lot of coordination between ux/ui / data / community / dev people
[21:00:25] <Nemo_bis>	 ori-l> imagine a new editor came on irc and asked about this pe=1 and you had no idea what they were talking about. <-- which is likely given that they're usually told to go to #wikipedia instead of #wikimedia-tech
[21:00:36] <Jarry1250>	 Also, they wouldn't notice
[21:00:52] <Jarry1250>	 ^ re: nemo
[21:01:05] <ori-l>	 Jarry1250: there are lots of ways things could break
[21:01:15] <ori-l>	 that would be visible to everyone
[21:01:39] <ori-l>	 suppose we forgot to prefix the query parameter with '&' / '?' and you got something like ?action=viewpe=1
[21:01:42] <StevenW>	 re: debugging explanation etc. see https://www.mediawiki.org/wiki/Extension:E3_Experiments/Testing
[21:02:02] <Jarry1250>	 ori-l: I think perhaps you're misunderstanding me
[21:02:27] <Jarry1250>	 All I'm suggesting is that people who aren't bucketed don't get &pe uselessly appended to their URLs
[21:02:33] <Jarry1250>	 s/don't/shouldn't/
[21:03:37] <ori-l>	 Jarry1250: and what i'm saying is it's already hideously complicated to alter behavior and interface at run-time to different users based on criteria and we don't want to make it more granular than we need to because it's harder for us to reason about and makes it less likely our experiments will work
[21:04:10] <ori-l>	 That was desperately short on punctuation. I can rephrase if that wasn't clear.
[21:04:10] <Jarry1250>	 Which extension is this in?
[21:04:20] <ori-l>	 Jarry1250: E3Experiments
[21:04:32] <Jarry1250>	 I'll have a poke. Code is clearer than English
[21:04:46] <ori-l>	 see /experiments/postEditFeedback
[21:11:21] <Jarry1250>	 ori-l: Oh, it's all logged-in users? (Or I'm misreading that?)
[21:13:26] <Jarry1250>	 Oh, no, I am
[21:15:04] <Jarry1250>	 ori-l: Ah, I see, you're deciding eligibility in JS rather than PHP; I'm guessing you made that decision late because you have pef_eligibility coded for, but I can't find where it's assigned
[21:15:09] <ori-l>	 Jarry1250: depends what you mean. Data collection and UI/UX changes will only happen for logged in, newly-registered editors. These changes are gated by JavaScript code that check the current environment (is the user logged in? are they newly registered? etc.) against the experiment's criteria. That gating code will run for all users, and the query string fragment is an artifact of that that is world-visible.
[21:16:01] <ori-l>	 Jarry1250: "pef_eligibility" is a debug hook -- it's never added to URLS programmatically
[21:16:31] <ori-l>	 Jarry1250: it's something we can use to force a coerce a certain condition to be true because (for example) it's annoying to have to keep creating new accounts while we're testing
[21:16:46] <Jarry1250>	 Ah, I see. Well, I can see why this isn't easy for you. I'd assumed you'd be deciding eligibility in PHP rather than doing it all client side.
[21:17:34] <ori-l>	 Jarry1250: that was a tough design decision to make, but the direction of web development is to push state down to the client
[21:18:27] <ori-l>	 Jarry1250: it's easier for the back-end to send bits of information down to the client than it is for the client to report on state that may be decoupled from discrete http requests / responses
[21:19:27] <Jarry1250>	 You're having the backend send down data and then reconstructing it at the moment, rather than calculating first and then sending a single thing. Anyway, what's done is done.
[21:19:29] <ori-l>	 Jarry1250: and scattering bucketing logic in both PHP and JS code is too confusing
[21:20:55] <ori-l>	 Jarry1250: yup.
[21:21:39] <ori-l>	 Jarry1250: let me add one last point -- though we apply different standards to experiments than we do to permanent features, it isn't our intention to be cavalier about breaking things
[21:21:56] <ori-l>	 if what we're doing is seriously disruptive, it's not acceptable, and we should fix it
[21:23:04] <ori-l>	 we're principled about being kludgy :)
[21:23:43] <Jarry1250>	 Yeah, I'm just trying to work out if there's actually a fix to this...
[21:23:57] <Jarry1250>	 It seems like there *should* be, but apparently not...
[21:23:58] <spagewmf>	 ori-l , is ?pe=1 related to en wiki edits redirecting to /w/index.php?title=Page_name&pe=1 link rather than a more palatable /wiki/Page_name?pe=1 
[21:24:33] <Jarry1250>	 spagewmf: which of this is chosen is decided by MW, I think
[21:26:30] * Jarry1250  looks up the ArticleUpdateBeforeRedirect hook

[21:27:03] <ori-l>	 yeah, that's my understanding. i presume the addition of an unfamiliar query param is the trigger but i don't know for certain.
[21:29:12] <Jarry1250>	 I *think* it's in Title::getLocalUrl but it's too late for me to be able to follow that
[21:30:55] <Jarry1250>	 Anyway, to answer the original point, you can't hide it because it's not actually related to eligibility as I had assumed, but merely to the fact that it's a post-edit page at all.
[21:31:26] <Jarry1250>	 (I mean, you could related it to eligibility but that would mean porting the detection from JS to PHP which would be a pain for reasons previously stated)
[21:31:34] <ori-l>	 Jarry1250: right. you could tidy it up by delegating some of the eligibility logic to PHP-land, but that would suck
[21:31:35] <ori-l>	 yes, exactly
[21:32:14] <Jarry1250>	 Okay, well that's my curiosity sated. :)
[21:33:20] <ori-l>	 Jarry1250: i'm a little embarrassed that you explained it better than me. if you keep that up i'll start directing people to you :P
[21:51:13] <BarkingFish>	 evening guys :)  Are you aware of any issues with the servers in the Netherlands, please?  I just ran a traceroute to en.wikipedia.org, and it's getting as far as my ISP's interchange in Amsterdam, and then stopping dead. I get 6 complete  hops out of 30, the other 24 are dead
[21:51:14] <BarkingFish>	 http://pastebin.com/pbqgLLTh
[21:56:05] <domas>	 your  ISP sucks!
[21:56:40] <BarkingFish>	 It doesn't normally, domas :)  I just tracerouted secure.wikimedia.org and it hit perfectly, 16 hops and didn't miss one or timeout anywhere
[21:57:22] <domas>	 your ISP's amsix connectivity has issues then!
[21:57:25] <ori-l>	 domas: traceroute --opinionated
[21:57:27] <domas>	 mine works fine
[21:57:38] <domas>	 hehe
[21:58:54] <BarkingFish>	 http://pastebin.com/PdrUpaHS
[21:59:01] <BarkingFish>	 That's the one I just took to secure
[21:59:03] <domas>	 barkingfish: what is your IP?
[21:59:10] <BarkingFish>	 it didn't even hiccup the local router
[21:59:28] <domas>	 heh
[21:59:34] <BarkingFish>	 I don't know what my public IP is
[21:59:36] <domas>	 I'm sure local router is remote destination aware!
[21:59:50] <DaBPunkt>	 BarkingFish: ip.apper.de
[21:59:52] <domas>	 http://whatismyip.net/
[21:59:53] <domas>	 etc
[22:00:06] <BarkingFish>	 82.26.4.133
[22:01:24] <domas>	 heh
[22:01:26] <domas>	 http://p.defau.lt/?P5JwC5B32k2KKxqumR0gAA
[22:01:42] <domas>	 virginmedia is stupid!
[22:01:44] <ori-l>	 hey domas did you read the ops thread about clicktracking / varnish / bits etc from friday?
[22:02:02] <domas>	 was flying
[22:02:04] <domas>	 anything interesting?
[22:02:47] <BarkingFish>	 domas, virgin media has always been stupid.  That's not to say they don't provide decent internet, but they couldn't find their arseholes in daylight if you gave them a map and a compass :)
[22:04:36] <ori-l>	 domas: for you, no -- all hideously trivial and exhausting. for me, yes :) wanted to get your advice re getting log data from bits to collection point. i could explain, or you can read the email thread, or you can wait for me to finish a write-up i'm working on, or you can tell me to buzz off :)
[22:06:08] <BarkingFish>	 It is most likely network issues this end, domas.  It's not just wikipedia now, everything is taking ages to load through.
[22:11:11] <domas>	 eh
[22:11:12] <paravoid>	 BarkingFish: it's definitely something on your end
[22:11:28] <paravoid>	 call them up and complain
[22:12:05] <BarkingFish>	 i would, but tech is not answering - i suspect others are complaining. I am in a queue with 42 people ahead of me
[22:14:30] <paravoid>	 it's never late to switch ISPs :)
[22:15:01] <paravoid>	 although to be fair, if their upstreams are screwed, it's normal to have a large tech support queue.
[22:15:24] <BarkingFish>	 it is when you live in an uncabled area, paravoid - my only choice other than virgin media's public wifi network is BT's ADSL service, at a cracking 1.5MB/s
[22:15:26] <BarkingFish>	 wow
[22:15:29] * domas  waits for mail to load

[22:15:42] <domas>	 barkingfish: you can go to sleep :) 
[22:15:47] <domas>	 I GOT 300MBPS 
[22:16:07] <BarkingFish>	 i can't wait to finish my move to Munich in a week's time, and actually have decent internet access.
[22:17:18] <BarkingFish>	 domas, enjoy it. We're only just getting fiber lines rolled out in the UK, which will hit 100MBPS.
[22:17:55] <BarkingFish>	 then again, why people need anything above 100MBPS is beyond me. What are you doing, downloading the entire Library of congress or something? :)
[22:18:13] <domas>	 rich media! 
[22:18:24] <domas>	 virtual  machines!
[22:19:03] <BarkingFish>	 yeah. The most I do is sit here on aMule expanding my already rather vast music collection :)
[22:19:57] <DaBPunkt>	 BarkingFish: before youtube, most people didn't need 6000kbits ;)
[22:20:05] <paravoid>	 640K ought to be enough for anybody, after all.
[22:20:50] <ori-l>	 paravoid: K? in my day the alphabet stopped at H, and it suited us just fine.
[22:38:43] <DaBPunkt>	 gn8 folks
[22:39:23] <BarkingFish>	 n8 DaBPunkt 
[22:39:29] <BarkingFish>	 schlaf wohl
[22:39:51] <DaBPunkt>	 BarkingFish: that sounds like someone from the middle age ;)
[22:40:20] <BarkingFish>	 I'm almost 40, DaBPunkt :)
[22:48:16] <domas>	 always pleasure to read threads about gerrit
[22:53:52] <ori-l>	 the longer the better
[22:54:03] <ori-l>	 brb
[22:58:48] <nibalizer>	 arstu/win 41
[22:58:52] <nibalizer>	 er
[23:13:25] <logmsgbot>	 !log reedy synchronized php-1.20wmf8/includes/WebRequest.php 
[23:13:34] <morebots>	 Logged the message, Master
[23:54:11] <Thehelpfulone>	 Reedy, I created it at the same time as you!
[23:54:29] <Thehelpfulone>	 I'll delete my one, it's "E3Experiments" (no space)