Mon, Oct 22
One day, Math will not suck...
Sep 19 2018
These requests should go through Special:Contactfirstname.lastname@example.org but test wikis are against our Content Policy anyway.
Almost everything on this list is not set the way you're requesting on purpose.
Jan 28 2018
Jan 27 2018
Jan 26 2018
You won't see an identified cause or steps towards a solution because you're not a member of staff. It is a known issue and is being worked on.
Oct 25 2017
Produced a fairly basic special page prototype. Job needs fleshing out and form needs validation.
Oct 20 2017
Aug 21 2017
Currently being used on Brickipedia with no issues. Hope to roll out globally soon.
StaffWiki now done.
Certificates expired for *.shoutwiki.com.
Jul 7 2017
So I'm going to target this for February 2018... it'll give us a bit of prep time after LetsEncrypt launches wildcard certificates in January.
I'm going to go as far as to say I can't see us supporting this extension any time in the next 12 months. I'm almost tempted to go further, but who knows. A few months ago, I would have said the same thing about Echo.
Jul 5 2017
So the idea, other than just providing the deletion log if a wiki was deleted, is to provide something along the lines of the old Wikia home page with image links to related and big wikis.
So NoSuchWiki no longer uses HTTP_REFERER as browsers don't set this often enough for this to be reliable.
Jun 16 2017
Looks very useful. Might try and get this out soon.
Jun 12 2017
Jun 11 2017
Isn't there already a task to rewrite CreateWiki's backend?
The fix is to stop using HTTPS. I know, it sucks, but it's unsupported for a very good reason at the moment, and it'll stop working when our current certificate expires in about two months time.
Jun 8 2017
This is actually a good request we hear quite a lot.
Within certain parameters, yes. Email email@example.com. This isn't a bug, and it is a widely known fact.
Oh, really? I was under the impression we get CPM as well as CPC bids on our ad units. But then again, what do I know? I'm only the person with the access to the data.
Yes, there are security and/or privacy issues. The applicable part here being "privacy issues". Which is why only staff can use these tools to enable us to do our jobs. We take privacy seriously, and these tools are not used unless it is necessary. LookupUser was originally written by one of the key MediaWiki developers, who is currently employed by the Wikimedia Foundation, so will have been written with security and privacy concerns in mind.
There's a reason a number of extensions in the repository are unused. For Configure it's a case of "works okay for one wiki, not 8800+."
Jun 3 2017
Jun 2 2017
Jun 1 2017
Apr 9 2017
Mar 30 2017
Mar 29 2017
Mar 28 2017
Based on the fact that patch was filed... over half a year ago, we can safely assume it's been deployed. Can we close this as resolved?
Mar 27 2017
Should be fixed?
Mar 25 2017
Mar 18 2017
I think this was resolved with T180 and various other changes.
Mar 17 2017
So after more reports of session issues this morning, I've put sessions in Redis for now.
Mar 14 2017
While having this page available in as many languages would be nice, I'm not really sure if it's feasible.
Thinking about it, we could do with a better 404 and 403 error page.