Is there any roadmap for MediaWiki that addresses the EU’s GDPR (General Data Protection Regulation) being enforced as of 28 May 2018?
Mainly addressing user registration on websites and holding what the EU deems personally identifiable information of EU residents such as usernames, real names, email addresses, etc. A method to prove consent such as a checkbox for Terms of Service and the date consent was given.
From the read of GDPR, it effects any company or organization (even those outside the EU) who store data on someone living in the EU.
I am happy to announce the initial release 1.0.0 of the Mermaid
extension  created by James Hong Kong. It requires MediaWiki 1.27 and
later as well as PHP 5.6 and later.
It provides the #mermaid parser function to support the generation of
diagrams and flowcharts with the help of the mermaid script language,
e.g. flowcharts, sequence diagrams and gantt diagrams. See the README
 to learn what this extension is all about.
I'm on version 1.29.2.
Users are not able to log onto the wiki when using the $wgReadOnly
"$wgReadOnly = 'Down for maintenance, access will be restored shortly';"
Users see the following message:
There seems to be a problem with your login session; this action has been
canceled as a precaution against session hijacking. Go back to the previous
page, reload that page and then try again.
In a previous version, we were able to set this variable and users were
able to log in, view the wiki, but just not able to make any changes or
updates. We had just recently upgraded to v1.29.2, but I don't remember
for sure what the previous version was. Perhaps it was 1.26.x, just not a
hundred percent sure. I just know that it worked.
I cannot figure out how to change the default behaviour (MW 1.27.4):
* Users that are not logged in and enter someting in the (built in) search box are searching using the default profile
* Users that are logged in are searching using the advances profile
I want to change that so that also logged-in users are directed to the Special:Search with the default profile, NOT with the advanced profile. I cannot find any configuration variable to influence this.
I am thinking of ways to bootstrap https://www.cyanpages.info The Local
Politician and Bureaucrat Directory in a way I can maintain it myself
because I couldn't get any community organizers to give me the time of
day when I asked them what they wanted to see in a directory. I am just
going to move on without them.
I can do it manually, but there is so much data to input, I won't be
able to afford to throw all of the time it needs to keep it up to date
by myself that way.
What would make sense would be to make a structured wiki that would
automatically pull from the government websites and the government
statistics websites using external data, cargo, and page forms, but
that is too much for me to comprehend where to start.
Right now I what I think I can do right now is create a Google Custom
Search Engine and index all of the websites that I think I need to
index in one search to start and then maybe I will learn just enough to
ingest some data into the wiki in an automated way.
Is there anything else I can do that I didn't think of?
First of all I have no legal background so the solution must be simple and clear (KIS)
On my wiki there are only invited users and from them I have not for example a birthday , address or other personal information.
So in my simple mind I don’t have privacy content.
But the question remains must I still comply to the new ruling??
I don't know if I'll be sending an email for every episode, but - I just
released the 2nd episode of the "Between theBrackets" podcast, featuring an
interview with developer Niklas Laxström, AKA Nikerabbit:
I hope you all like it!
At the moment I'm planning to continue at this rate, and release an episode
every two weeks.
As of Feb 20, 2018, the developers of Parsoid are deprecating support
for node v4. Parsoid is the service that powers VisualEditor, Content
Translation, Structured Discussions (formerly Flow), and other MediaWiki
features. If you don't run a MediaWiki install that uses VisualEditor or
these other features, then this announcement does not affect you.
Node v4 is reaching end of life (EOL) on April 30, 2018 .
In March, we'll release our next debian  and npm  packages. This
will be the last release that will have node v4 support. We'll continue
to provide any necessary critical bug fixes and security fixes for these
packages till node v4's EOL date.
If you are running a Parsoid service on your wiki and are still using
node v4, please upgrade your node version by May 2018. Parsoid has been
tested with node v4, v6 , v8 and the latest (v10) and works with all
these versions. So, the upgrade away from node v4 should be seamless
from the Parsoid point of view.
The Wikimedia cluster runs node v6 right now and will be upgraded to
node v8 some time this year. However, we are dropping support for node
v4 right away from the master branch of Parsoid. Going forward, the
Parsoid codebase will adopt features available in node v6 and higher
(async / await) which aren't supported in node 4x and will constitute a
Going forward, we will NOT be issuing these node version deprecation
announcements. Parsoid's support for specific node versions will be
dropped around the same time that the specific node version reaches its EOL.
On behalf of the Parsoid developers.
 Node.js Long Term Support schedule @ https://github.com/nodejs/LTS