They seem to have one: https://github.com/wikimedia/WikimediaUI-Style-Guide (maybe it is already in gerrit?)
Fri, Jan 19
Improving FeaturedFeeds seems the way to go…
@Legoktm pointed out that "Gerrit would probably not be able to talk to things in cloud services" and indeed, it seems undesirable that Gerrit login page (an high security context) included content from a lower security one. (E.g. a naive implementation copies html produced there into Gerrit login page, then someone compromises the toollabs project and uses it to steal developer credentials)
I guess the existing विकिविद्यालय should be kept as an alias, so that existing links don't break.
It would be nice to have a generic solution that can be used by other sites wishing to include the POTD, ie. keep the Gerrit-specific part as small as possible.
Wed, Jan 17
Sat, Jan 13
Alternatively, give them a real cookie containing a temporary token, which is what we will be using.
Note we'd then have to vary on that cookie, at least for views served via EditPage.
Fri, Jan 12
On the BebasNeue typeface, the design agency wanted to use it for certain graphics so it's use is limited. Because the majority of the site is in our open source brand font (Montserrat) we had accepted this artistic choice as a "limited decorative" element.
Thu, Jan 11
Ah, okay. So those pages are currently cache-bypassing without being session-starting. I assume the patch would need to change this to do both. Or is there another way? I haven't checked the numbers, but I imagine we should be able to handle the increased load from that (basically, anon bounce rate of edit page; possibly inflated by crawlers).
This bug only happens when $wgLegacyEncoding is set. But the variable doesn't seem to be checked anywhere!
EditPage::internalAttemptSave() → WikiPage::doEditContent() → WikiPage::doModify() → Revision::__construct() calls RevisionStore::newMutableRevisionFromArray()
I don't think the file license would be compatible with scaps run by WMF employees. Could be used by those run by volunteers, though.
Wed, Jan 10
I guess your manager at WMDE should confirm here that you are indeed a WMDE developer?
Tue, Jan 9
This task says: We have docs at https://www.mediawiki.org/wiki/Manual:Installing_MediaWiki and https://www.mediawiki.org/wiki/Manual:Upgrading Someone should try installing using that documentation, and see if they are outdated or is wrong with such documents.
Mon, Jan 8
Sun, Jan 7
The extension seems to work with the provided changes. A Special:WatchSubpages special page is added, and it allows adding pages to the watchlist.
Fri, Jan 5
Sat, Dec 30
I expect other developers would be interested on this as well, but I can help mentoring this (added).
Fri, Dec 29
Dec 13 2017
Maybe it would be possible to extract from swift the list of files stored there? Then no HTTP requests would be needed (unless this shows that the problem lies on a different layer, of course).
Nov 20 2017
Completely confusing indeed.
Rather than "prevent", I think the UI should offer to "replace" the existing request (conceptually equivalent to cancel + open new one, but nicer UI)
Nov 8 2017
There is a third extension fighting for 'v' accesskey on edit page: FlaggedRevs.
I don't think it makes sense to have different actions depending on browser, either.
Oct 22 2017
Thanks fo the answer, @Sagorika1996!
Let me also support the position of not restricting <templatestyles> to a specific namespace.
Oct 21 2017
No problem. I was just reporting that the assumption that it was issued just once and never again turned out to be false.
Oct 19 2017
Is this expected to be a private tool (only showing your own contributions) or a public one (you can view the contributions of any user)?
I just received this ghost notification a second time. This time with &uselang=en version:
I don't think there are any news to investigate here.
I get a "new device" notification every other day or so (but I don't login to the wiki everyday), since I enabled it as stated on T174263#3574597
Sep 13 2017
I remember suffering silly self-conflicts. An additional issue is that ~~~~ magic expansion almost ensures that there will be a conflict, even if it could otherwise be automatically resolved.
Sep 2 2017
@IKhitron By definition, if the system does something that it shouldn't be doing, it is a bug. You may consider it unlikely, or even that the reporter was wrong. But if we admit that it happened, well, how else would you categorize it? :)
I wonder if it is worth creating a course on Visual Basic 6 on 2017 (19 years after release, unable to create 64 bit apps, unsupported for ~12 years…).
1- That captcha is not accessible, is annoying (all captchas are to some point, though), slow to solve, sometimes ambiguous, and generally a pain to pass (even in the best case).
That's the bug. Supposedly, that shouldn't happen…
So, you can't be sure.
What's ambiguous about:
I don't think we should be setting per-wiki defaults for these preferences that should be global. See T174263#3557302
Sep 1 2017
They are now 301s to http://www.aol.com/
Maybe they do. Perhaps Google is smarter and uses more datapoints/configured differently. They could even not be using Gmail.
Aug 31 2017
@IKhitron if the browser is configured to delete the cookies on exit, it will be unfamiliar every time, so you are back to "Did he edit recently from a nearby IP address?".
Aug 30 2017
I am surprised by this. I thought this was GPLv2 (like MediaWiki). Maybe we talked about it on Berlin but forgot to write it down? O_O
Aug 27 2017
These should be global preferences. It doesn't make much sense to receive an email when someone attempts to login with my account at hewiki, but not when they do so at enwiki, when it's the same password. And if it was treated as a global preference (isn't the case right now), then the defaults shouldn't be determined per-wiki, so it may be preferable not to setup custom values for these preferences.
Not only for fairly new accounts. Today, I received an echo notification that I had successfuly accessed my account from a new device, and my account is not new at all.
Aug 22 2017
Does it work if Danny tries to log into Niharika?
Aug 20 2017
@MER-C this is abusing confusion between the latin o with "о" the U+043E CYRILLIC SMALL LETTER O, but that equivalence has been there for years...
Aug 19 2017
Aug 18 2017
$wgSessionCacheType is misspelled in LocalSettings (so it is actually CACHE_ANYTHING) or just when typing it into phabricator?
Aug 17 2017
Maybe worth adding a link to https://www.ssllabs.com/ssltest/viewMyClient.html to the error page so people can check their cipher support ?
Aug 10 2017
@Dzahn was anything found there? Can this task be closed?
@valhallasw is there anything left to do here?
Maybe changing the contents for X-Spam-Report would be enough to work around this Google problem.
The Community discussion from https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Miscellaneous#Provide_a_dummy_email_address also raises some interesting points:
The problem with a forwarder is that when people start eg. sending emails with viruses attached (or simply spam) to @private.wikipedia.org addresses, they will go out from WMF IPs, which are then categorised as a source of virus/spam.
Aug 5 2017
Although @Nemo_bis is not listed there, currently.
Jun 19 2017
That AND log_params NOT LIKE '%::auto";i:1%' is everything but efficient. You should be able to replace it with AND log_action = 'patrol' (ie. log_action != 'patrol'), after which you could at least use type_action index.
May 15 2017
Rather than changing countless uses, and also annoying downstream users and developers, why don't you let the input keep wpSummary id?
That seems a much nicer solution, instead of repurposing an id that has been used that way for nearly 12 years.
Apr 26 2017
https://code.organicdesign.co.nz/extensions/tree/master/MediaWiki/EmailPage/ shows that it is using PHPMailer-5.2.21
Apr 18 2017
There's a longer list at https://aurbano.eu/blog/2008/04/04/bad-words-list/
We could use several blacklists. Adding that list should be easy. Not that many of those words could be generated by our captcha, though.
Are you perhaps a «powerful bureaucrat» on your dev wiki?
Apr 17 2017
Apr 7 2017
We should definitely reject emails failing SPF. Much less forward that to mailing lists
(forwarding to list owners might be acceptable, although I wouldn't recommend that, as 99.999% will be spam).
Apr 5 2017
Given that the problem seems to be just the algorithm memory check rather than actually needing that extra memory, this has a really simple solution:
Apr 2 2017
This is requesting a technical solution for what is a social problem. A template saying «This is a work in progress. I do not want anyone else to edit this page, no matter how wrong it may be» could be enough to solve it.
Mar 25 2017
It doesn't have debug symbols for /usr/lib/x86_64-linux-gnu/liblua5.1-c++.so.0 Those are provided by the liblua5.1-0-dbg package.