Re: [Wikitech-l] Allow HTML email
Tim Starling wrote: > We still haven't heard from Faidon who, last I heard, still reads his > emails by piping telnet into less or something. But I think he can > make sense of multipart/alternative as long as it's not base-64 > encoded... I'm not Faidon, and I'm not even a regular contributor to this list, but as a data point of almost vanishingly possible interest, I can say that the above isn't even much of an exaggeration for the suitably old-guard set. Me, I read mail using a shell script 'mshow', which boils down to a selective cat from $MAIL into more, and gratuitous base-64 encoding is indeed an issue, causing me to pretty regularly have to type mshow | mailbody | b64 -d | more I have really got to automate that some day. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] GeoHack glitch
This probably isn't the right place to report this, but if anyone knows anyone who maintains GeoHack, today it's emitting KML placemark names containing raw ampersands, which Google Earth doesn't like. Example: [[Baltimore & Ohio Railroad Bridge, Antietam Creek]]. Manually editing it to solves the problem. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] changing edit summaries
bawolff wrote: For comparision, how many revision control systems allow editing commit messages. Perforce does. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] changing edit summaries
Martijn Hoekstra wrote: Wow, that escalated quickly. How did we go from hey, what's the deal with this? To YOURE BURNING THE WIKI in a few posts? Easy: because it's a hard question, with excellent arguments on both sides. Clearly, people are going to make typos in edit summaries from time to time, and clearly, making a null edit to correct the summary is a stupid kludge, so clearly, editing of edit summaries should be allowed. But clearly, allowing editing of edit summaries would introduce all new kinds of abuse, so clearly, I cannot choose the goblet in front of you, I mean, editing of edit summaries must remain impossible. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] SVG guidelines
bawolff wrote: On Apr 21, 2014 9:21 PM, Lars Aronsson l...@aronsson.se wrote: Do we have any guidelines for how to hand-write the source code of SVG diagrams? Should we? Really this seems like the domain of commons to set standards for svg writing. I think this should be brought up over there I found: https://commons.wikimedia.org/wiki/Help:SVG https://commons.wikimedia.org/wiki/Help:Inkscape These seem to contain some decent guidelines, although they don't seem to mention anything about dimensioning (pixels vs. otherwise). ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] login Javascript?
That would be a good guess, but the script handles redirects and https just fine -- or at least it did, when those changes went into effect a month ago. It was working fine up until this past Tuesday or Wednesday, when it stopped being able to log in. Tyler Romeo wrote: My guess is either the script does not handle redirects, and is failing when the login page tries to redirect you to HTTPS, or your script doesn't handle HTTPS, and fails when redirected to the secure page. On Sat, Aug 31, 2013 at 6:48 AM, Bartosz DziewoÅski matma@gmail.comwrote: There is very little JavaScript on the login page. Is your script HTTPS-compliant? Logging in is now HTTPS-only since a few days ago, attempting to access the login page via HTTP will redirect you to HTTPS. -- Matma Rex ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] login Javascript?
Ah, spoke too soon. It was handling redirects and https, but not always redirects and https and POST. But if I simply reconfigure the script to hit the https: addresses from the beginning (meaning the server doesn't have to send any redirects at all), everything works fine. Dunno why I didn't try that at first. (In hindsight, dunno why I didn't do that years ago.) I wrote: That would be a good guess, but the script handles redirects and https just fine -- or at least it did, when those changes went into effect a month ago. It was working fine up until this past Tuesday or Wednesday, when it stopped being able to log in. Tyler Romeo wrote: My guess is either the script does not handle redirects, and is failing when the login page tries to redirect you to HTTPS, or your script doesn't handle HTTPS, and fails when redirected to the secure page. On Sat, Aug 31, 2013 at 6:48 AM, Bartosz DziewoÅski matma@gmail.comwrote: There is very little JavaScript on the login page. Is your script HTTPS-compliant? Logging in is now HTTPS-only since a few days ago, attempting to access the login page via HTTP will redirect you to HTTPS. -- Matma Rex ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] login Javascript?
I have a bot editing script that started having trouble logging in to the English Wikipedia a few days ago. I think what's happening is that the login process started using Javascript in a way it didn't before, and is detecting that my script doesn't do Javascript (which it doesn't), and throwing a second, fallback, non-Javascript-using login page at the point where the script is expecting to have already logged in. So the question is, if this is the case, is there a way to force the use of the non-Javascript login page from the beginning? Or if this is not the case, is there some other recent change that might have affected the flow? (And, in case you're wondering, no, the script does not use the API, but yes, I know about it, and this may be the circumstance that goads me into actually using it.) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] You have new messages glitch?
Today I'm noticing that if I visit someone else's user or talk page (this is on en.wp), I see a little orange box saying Talk: you have new messages even though I don't. Presumably that user does, or something. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] VE and nowiki
Risker wrote: On 23 July 2013 15:32, Robert Rohde raro...@gmail.com wrote: * Corrupted page content that appears to be caused by the unfamiliar UI (e.g. nowiki[[Foo]]/nowiki) Why do you think those nowiki tags were added by the editors? I assume that since it's VE's job to be wysiwyg, and to insulate the user from the low-level markup details, any time anyone forgets they're in VE and attempts to create a link by reflexively typing [[pagename]] VE will (correctly, from its point of view) translate that to nowiki[[pagename]]/nowiki in the page source. This is a likely enough mistake, and the number of times you really want explicit double square brackets is small enough, that it's worth thinking about (if it hasn't been already) having VE detect and DTRT when a user types that. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Remove 'visualeditor-enable' from $wgHiddenPrefs
Tyler Romeo wrote: On Mon, Jul 22, 2013 at 9:35 PM, James Forrester jforres...@wikimedia.orgwrote: Each added preference adds to the complexity of our software - so increasing the cost and slowness of development and testing, and the difficulty of user support. Stop being so dramatic. This is clearly false. Creating such a preference is a lie, and a lie I cannot endorse. In conclusion, if you really think lying to the community is so bad, then I recommend the VE team stop doing so as well as stop shoving this propaganda down the community's throat as if VE is the second coming. Actually, it would probably help if both sides of this debate stopped being so dramatic. No, VE is not the second coming -- of the deity or the devil. No, its developers shouldn't be jamming it down anyone's throats, but I think they do deserve to be at least a little bit proud of their accomplishment, because as we know it's been a very highly desired feature for a long time but has been very difficult to implement. And on the other side, I don't think people should be calling it broken or a bad idea or dismissing it as something so repugnant that they want to ban it from their sight. Now, don't get me wrong: I'm a low-level kind of guy, who hasn't used VE and probably never will; matter of fact just yesterday I was pining for the good old days of text formatting using troff. But I believe -- and I don't think this is a controversial belief -- that those of us who prefer markup as opposed to wysiwyg formatting are in a pretty tiny minority. Having a whole preference just so that a handful of people -- power users, no less! -- can hide one unused feature seems odd, a historical accident at best. Here's a thought experiment: if visual editing had existed (with reasonable functionality) since day 1, would there ever have been a way to disable it, let alone a hue and cry over a lack of a way to disable it? Now, given that it hasn't existed since day 1, a transition to its existence is bound to be wrenching, but my hunch is that in a year or two all this consternation (over VE's existence, or initial bugginess, or lack of disableability) will be pretty much forgotten. (Seriously, how hard is it to choose edit source if that's what you want to do?) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Git for idiots
S Page wrote: Note Mediawiki.org doesn't have a Git tutorial. There are tons of those on the web... Git+Gerrit is fundamentally hard and complicated... So perhaps there could be a little section somewhere saying something like: Using Git and Gerrit effectively requires understanding how they work. If you're used to conventional source code repositories like svn, you'll find git to be considerably different, in part because it's completely distributed, without any central repository which you check files out of, much less that you check files in to. Instead, with git, you mumble flarg the bjango in order to tnark your flittle and svetch it out to the rest of the hortlespoon. For a good explanation of this, see http://one.of.the/tons/of/good/tutorials/on/the/web. (Obviously that's incomplete, but as someone who only understands conventional repositories that you check files out of and in to, I don't yet get git at all, myself, either.) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Has someone just changed math rendering?
David Gerard wrote: This page came up with raw mathtex, then I saw a math rendering xx% counter at bottom right, then 15 seconds later I had the page: https://en.wikipedia.org/wiki/Noether's_theorem I admit this sort of page would make a good stress test ... Possibly related: the Math reference desk was rendering impossibly slowly (to the point of timeouts and WMF error pages) a few days ago. Discussion at: http://en.wikipedia.org/wiki/Wikipedia:RD/MA#Posting_here_is_really_slow_today http://en.wikipedia.org/wiki/Wikipedia:RD/MA#Preformatted_math-tags_cut_this_page_30_seconds http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Posting_to_the_math_reference_desk_is_really_slow ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Can we make an acceptable behavior policy?
MZMcBride wrote: Ryan Lane wrote: Again with the phrasing. Cut it out. Sincerely, I'm still a little unclear what phrasing you object to here. Just to be perfectly clear, it's the use of the word mess, right? If so, I can make note not to use that word going forward on this list. It may be a regional thing... I think it's more of a cultural thing. You've displayed two traits that I'd tend to associate with the old Usenet culture: 1. A near-absolute reverence for doing things Right. In the case of system administrative tasks, that means, Never Fuck Up the Data in a Lossy Way. If you have to stay up all night to fix it, you stay up all night. 2. A willingness to avoid issues of delivery in communication, a predilection for calling a spade a spade. If someone gets their feelings hurt by that kind of directness, it's their problem. As someone who harbors both these traits myself, you have all my sympathy. But as someone who has badly insulted others, and who has been badly insulted by others, the others in this thread have all my sympathy, too. (How's that for fence-sitting?) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] IE7 tax
MZMcBride wrote: Right... well, again, just like the OP, you're focusing on how you feel the world should be while completely ignoring reality. It's not a matter of catering to obstinate IT folks. It's a matter of being pragmatic about the current landscape and its limitations. This touches, I think, on both the fundamental issue, and the reason we can (and likely will) debate this forever, without ever finding a right or even a consensus answer. Do we want to educate/force people to use the right browser, or do we want to support them, regardless of what they're using? There are lots of reasons to want to educate/force a change: security, implementational convenience, standards compliance, modernity, etc. And there are just as many reasons to oppose the imposition: personal preference, obstinate IT department, obsolete computer, cascading incompatibilities. Some of these reasons (on both sides) are super important, while others are more subjective -- but not everyone will even agree on which are which. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Temporary password too short
William Allen Simpson wrote: This replacement password is much more easily guessed. The account could have been stolen within minutes or hours. Is this true? (Yes, I know that a fast machine can try zillions of passwords per hour in theory, but for a reasonably designed system, certainly not in practice.) Please update the password generator to use at least 17 characters, That seems like far too many. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Coding challenge about to land. :)
Would I sound like a reactionary old crank if I asked why the coding challenge welcome page requires JavaScript? Without it, one can't even see the list of challenges! ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] pages jerk up and down every 10 seconds
Platonides wrote: jida...@jidanni.org wrote: On some of the Wikipedia sites, there are some messages near the top of each page. [...] This causes the entire page to jerk up and down the screen... Do they change in the same page view, or when changing pages? (I have seen the later, when several campaigns are enabled, but the former shouldn't happen) I noticed something similar a few weeks ago. It didn't quite match jidanni's description, but it was certainly annoying. The top-of-page message -- it might have been one about the image tagging campaign -- was JavaScript-enabled, with a show/hide button. And, for me at least, it rendered initially in one state, and then, after the entire rest of the page had loaded and rendered, some last bit of JavaScript seemed to run, and flip the show/collapse state. By now, typically, I already had my mouse over some regular link or edit button I intended to click, but just as I did so, the page jumped by a few lines, and I'd miss. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] WMF XML dump title case problem
Emmanuel Engelhart wrote: Titles should be stored in the table page with a first letter uppercased... Unfortunately, it seems that we have XML dumps (and consequently mwdumper generated SQL) containing titles with a first letter lowercased. For example: $wget http://download.wikimedia.org/mywiktionary/20110617/mywiktionary-20110617-pages-articles.xml.bz2 Wiktionary is different. Its users requested reconfiguration so that words are stored in the database with their exact capitalization. The Wikipedia-style first-letter capitalization (which caused pretty severe problems for a dictionary) is *not* performed there. See also http://en.wiktionary.org/wiki/Wiktionary:Capitalization . ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Collaboration between staff and volunteers: a two-way street
Roan Kattouw wrote: [The volunteers'] role, IMO, is to keep the collaborative environment positive. This means being welcoming to new staff, embracing them, pat them on the shoulder when they to things right and correct them when they do things wrong, while keeping their patience. I feel that especially the shoulder-patting and patience parts have been lacking lately, at least in the perception of the staff members I spoke to. This leads to them perceiving the environment as predominantly negative towards them, which does not encourage them. Please pardon an outside comment which may be misinformed, or too blunt; I haven't been part of this discussion or followed all of it, and I'm not well-informed on the tensions which motivated it. But: It seems to me that if we're talking about backpats, it's the volunteers who are more likely to need them, not the paid staff. Since you hire the paid staff, you can presumably pick people who are professional enough to understand their job requirements and remuneration structure, and the special issues involved in working with volunteers. One of those issues is that the volunteers are sometimes going to be cantankerous, or even downright vituperative, and if in spite of this you think it's primarily the volunteers whose job it is to keep the environment positive, you're likely to be disappointed. You don't hire the volunteers, of course, and you're somewhat stuck with the ones you get. If one of them gets his nose bent out of joint over some perceived slight, then you might have to give him a pat on the back (even if you think he doesn't deserve it), because you can't get rid of him if you think he's being oversensitive, and you certainly can't tell him to quit his blubbering and be happy with the paycheck he's getting. The volunteer's primary job is to donate real work for free, and if he imagines that one of the perks of the role is the right to get kvetchy from time to time (perhaps due to a twinge of jealousy that the staff are getting paid and he's not), then that's okay, and it's the staff's job to humor him, with a pat on the back if necessary. Unfair and asymmetrical it may be, but the staff does *not* get to get kvetchy in turn about a negative or unwelcoming atmosphere. [Disclaimer: I am not at all trying to suggest that Wikimedia's volunteers *are* a bunch of praise-craving blubberers. But if anyone's going to act that way, it should be the volunteers, not the staff.] ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] So, Java.
David Gerard wrote: On 13 August 2010 22:05, Aryeh Gregor simetrical+wikil...@gmail.com wrote: Oracle is only suing Google because Google is redistributing Java without paying them, and because they're using a modified version (so technically they're not covered by the patent grants), and because Google has deep pockets. It's pretty implausible that they'll sue users and developers directly. If they do, Wikimedia has little enough money to be extremely low on their list. I don't think we need to worry about this one way or the other at this point. I wasn't aware of if we can probably get away with it in the WMF guidelines regarding free software. But the first half of Aryeh's first sentence (Oracle is only suing... not covered by the patent grants) stands alone. Unless we're afraid that Oracle is going to start going after anyone who uses Java in any way, we shouldn't have to worry. (We're not redistributing JDK's, let alone modifying them.) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] User-Agent:
daniel wrote: I have put some basic info about requireing the User-Agent header at... This way, there's a place where can point people for more info. Thanks, but FWIW, the very first sentence: Wikimedia sites require a HTTP User-Agent header for all requests. is false. (As near as I can tell, the header is required only for those requests that include an action= modifier.) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] User-Agent:
Yes, that's precisely the violation of Postel's Law I was thinking of. Steve, someone is sending us this User-Agent, is that you?:)) No. :-| Let me tell you a story. Once upon a time, there was a browser named SeaMonkey... I have no idea what point you were trying to make there (I had considerable difficulty reading it at all, crammed onto one line as it was), but never mind. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] User-Agent:
Domas wrote: We don't use UA as first step of analysis, it was helpful tertiary tool... But it's now being claimed (one might assume, in defense of the new policy) that disallowing missing User-Agent strings is cutting 20-50% of the (presumably undesirable) load. Which sounds pretty primary. So which is it? Presumably some percentage of that 20-50% will come back as the spammers realize they have to supply the string. Presumably we then start playing whack-a-mole. Presumably there's a plan for what to do when the spammers begin supplying a new, random string every time. (I do worry about where this is going, though.) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] User-Agent:
Conrad wrote: Given the lack of of any evidence, I assert that most of the percentage of people who a) notice a problem, b) care, c) know how to fix it; probably deserve to be using the resources anyway. Besides anyone who doesn't deserve but still fixes the problem will likely be able to, and want to, circumvent other measures. It's the last point that's the kicker. I don't have any evidence, either, nor do I know precisely what problem is attempting to be solved, here. Spamvertisers have been mentioned. The impression I get is that when it comes to spamming, the vast majority of the damage is caused by a small minority of operators who are extremely motivated and have the resources to hire arbitrarily talented programmers. Therefore, an approach like this might block a large number of the nasties, but a small percentage of the total damage. So, in the end, if the spam problem ends up being more or less exactly as bad as it was before, then all of this is actually a net loss. Not only are the spammers unimpeded, but the collateral damage is still exacted: the unknown numbers of innocent bystanders (who, for whatever reason, don't have User-Agent supplied for them and aren't in a position to complain about or fix it) remain excluded. Furthermore, once we've taught/forced the canny spammers to undetectably spoof the User-Agent string, that string becomes that much more useless, not only to us, but to everyone else on the net, too. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] User-Agent:
Ariel Glenn wrote: I understand it's aggravating to people who didn't get notice; let's look forward. PLease just add the UA header and your tools / bots/ etc. will be back to working. Thanks. Well, sorry, no, it's not quite like that. A few of us -- though I fear an inconsequential minority -- are concerned that this is a destabilizing change, being made in a hurry, by a top-10 website, with consequences that aren't easy to predict and (apparently) haven't even been thought about. The more of us who just go along with it, the less the consequences will be thought and talked about, and the more they'll be further hidden, and made inevitable. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] User-Agent:
Robert Rohde wrote: If you going to do such blocking can we PLEASE finally find a way to set up a more informative error message for blocked user agents... When the new code blocks requests with missing User Agent strings (which is, oddly, not all of the time), it is with a 403 Forbidden response and the very simple message Please provide a User-Agent header (No html tags, no nothing.) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] User-Agent:
Domas wrote: from now on specific per-bot/per-software/per-client User-Agent header is mandatory for contacting Wikimedia sites. Oh, my. And not just to be a bot, or to edit the site manually, but even to view it. You can't even fetch a single, simple page now without supplying that header. If this has been discussed to death elsewhere and represents some bizarrely-informed consensus, I'll try to spare this list my belated rantings, but this is a terrible, terrible idea. Relying on User-Agent represents the very antithesis of [[Postel's Law]], a rock-solid principle o which the Internet (used to be) based. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] User-Agent:
Domas wrote: Hi Steve, But why? Because we need to identify malicious behavior. You're trying to detect / guard against malicious behavior using *User-Agent*?? Good grief. Have fun with the whack-a-mole game, then. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Browser stats - OS as well?
Since some sites have regexes that assume that major version is one character long, the Opera developers had to resort to reporting a 9.x version in the old place, and append the actual version later. Good grief. That's one of the stupidest things I've heard in some time. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] A suitable error message for iPhones
dgerard wrote: Are you *sure* we can't put a narky message when iPhone users click a video? Adobe do! http://twitpic.com/kf361 I'm not up on the details of Flash, so this comment may be misguided, but *if* the reason Apple restricts these unstated technologies is for security reasons, then I'm quite glad Apple does, and I'd say it's Adobe that deserves the snarky comment. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] secure slower and slower
Gregory Maxwell wrote: For instance, take the UK service providers surreptitiously modifying Wikipedia's responses on the fly to create a fake 404 when you hit particular articles. Urk. (Can someone cite the details?) (2) You could script clients to kick users to a malware installer... ...and to make it impossible to remove without disabling client JS. Remind me why client-side JavaScript is a good idea? (Boy, am I glad I use NoScript.) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] image link popup weirdness
I don't know anything about link preview popups, but does the issue discussed in this thread: http://en.wikipedia.org/wiki/Wikipedia:Help_desk/Archives/2009_June_12#.27Adult.27_picture_on_the_Help_Desk.3F indicate a buglet that could/should be fixed? Should the preview code know about nowiki in a way that it currently doesn't? ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] edit form oddity -- newly missing input type
Andrew Garrett wrote: On Wed, Feb 18, 2009 at 7:12 PM, Steve Summit s...@eskimo.com wrote: Sometime between yesterday and today, the edit summary field on en.wp's edit page lost its type=text attribute. Is it causing any problems? No, just a curiosity. It was part of some much-needed code cleanup I did to the editing page. Okay, but beware: wpAntispam still does have the explicit type=text, and there's a confusing welter of single and double quotes among the type='hidden' fields. :-) You should note that bots *should not* be using the UI, as breaking changes such as this. Oh, yeah, I know. But it's an old bot, and it mostly works, and I haven't found time to sit down and rewrite it to use the API. Even using the UI, you should use a proper HTML parser, not regexes (as I suspect you were using) to parse the HTML. Don't worry, it uses a *ML parser. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] edit form oddity -- newly missing input type
Sometime between yesterday and today, the edit summary field on en.wp's edit page lost its type=text attribute. It now reads: input name=wpSummary size=60 value= id=wpSummary maxlength=200 tabindex=1 / Lo and behold, type=text is the default, so it doesn't actually break a standards-compliant browser, but it's kind of an an odd change. (I noticed because it mildly broke a bot of mine, that assumed type=text only by accident, and after printing some extraneous error messages.) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Please make a optional way to set editsection links after section's title
mizusumashi wrote:
Please see [[w:en:User:Mizusumashi/workspace]] with Firefox.
Don't you see moved [edit] links near at the second image?
I see two sections and two edit links, both of them moved down to
roughly the bottom edge of the first section's image. I see this
all the time on the real wiki as well; as far as I know it's a
known, longstanding bug. The solution on the real wiki is often
to put a {{-}} at the end of a section which has an image which
is vertically longer than the sections's text tends to be.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] hosting wikipedia
Jeff Ferland wrote: You'll need a quite impressive machine to host even just the current revisions of the wiki. Expect to expend 10s to even hundreds of gigabytes on the database alone for Wikipedia using only the current versions. No, no, no. You're looking at it all wrong. That's the sucker's way of doing it. If you're smart, you put up a simple page with a text box labeled Wikipedia search, and whenever someone types a query into the box and submits it, you ship the query over to the Wikimedia servers, and then slurp back the response, and display it back to the original submitter. That way only Wikimedia has to worry about all those pesky gigabyte-level database hosting requirements, while you get all the glory. This appears to be what the questioner is asking about. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
