While these candidates have been ranked through the vote, they still need to be appointed to the Board of Trustees. They need to pass a successful background check and meet the qualifications outlined in the Bylaws. New trustees will be appointed at the next Board meeting in December 2024.
Suggestion from @Shirayuki: "Since the only page passing both dev=y and admin=y in {{Hubs}} is Manual:Maintenance scripts, I personally think it would be good to place it near that."
We have created a new wikihoster, but I can't because abuse filter believes that my edit it's spam. Could you add
"|-
| SkyWiki
| USA
| farm
|
| style="background:#9F9;vertical-align:middle;text-align:center;" class="table-yes" | Yes
| style="background:#9F9;vertical-align:middle;text-align:center;" class="table-yes" | Yes, or subdomain
| free (no ads)
| Discord server
|
| Extension install on request, after security review. No hard limits on server resource usage and runs latest MediaWiki version." on this page please?
Editing the main namespace is limited for new users. This site is for documenting the MediaWiki software. It is not the wiki that you set up for your class, workplace, or personal use, nor is it Wikipedia. If you want to create a Wikipedia article, please start here. Think this is an error? Ask at Project:Village pump.
I've been trying to add a link to a MediaWiki host that I've had personal experiences with, but I'm getting a message "It seems that you're trying to add an external link to a page. [...] If you believe that you received this message in error or have a legitimate need for the link, please file a request at Project:Village Pump", which is what I'm doing. Can someone please look into this?
Users who have 1.) few edits and 2.) have not been registered here for long cannot post links. After you have made x edits and been here for y days, that restriction will go away. I don't know the exact numbers for this wiki, but something like 5 edits and 14 days is common on many Wikimedia Foundation wikis.
The criteria here are very low - you can't post links as your first or second edit, with a bunch of other exceptions. RaySS1987 should be able to post a link successfully now.
However this page does not exist. This causes the client generator (a tool that generate source code from a rest api description) that im using to break. I could probably workaround, but to me the most constructive solution would be to create the data-parsoid spec page.
However i cannot, since my account is new. Does anyone agree or disagree?
Create it with what content? I believe it's upto the API owners to decide when they want to create it. You should probably continue using your workaround.
Note that Specs/data-parsoid/0.0.2 exists; you should probably file a Phabricator task about these references to unwritten(?) documentation, rather than on-wiki.
Translatable pages allow contents such as project documentation on Mediawiki.org to be multilingual. Currently a flat list with all languages in which the content is available is listed above the page contents. As the content is translated into more languages, this makes it hard for users to find the content in their language (they have to scan a long list or rely on the browser search), clutters the page, and pushes the content down.
Language list on top of multilingual page on MediaWiki.orgWikipedia page connected to other language versions
To address this issue, the Language and Product Localization team is implementing a change to use the Language selector from ULS for language selection on Vector 2022. This aims to ensure consistency with the way languages are selected on other projects, such as Wikipedia.
Specifically, the configuration option ($wgPageTranslationLanguageList = 'sidebar-only';) that we are planning to use would display languages as interlanguage links only and ignore the tag even if present on the page. You can see this in action on translatewiki.net:
We’re planning to enable this on Test Wikipedia first, and then roll-out on all wikis where Translate extension is enabled based on community feedback. Feel free to leave your feedback here, or on the Phabricator task.
FAQ
Q: Why are we making this change?
A: Currently a flat list of all languages to which the page is translated is displayed at the top of page contents. As the content is translated into more languages, this makes it hard for users to find the content in their language (they have to scan a long list or rely on the browser search), clutters the page, and pushes the content down.
Using the Language selector from ULS, makes the available language list searchable and clears up the top of the page to display the actual content. It also brings uniformity to how content language selection is done across our sites.
Q: Will I still be able to see the translation progress for each language?
A: Yes, translation statistics for each language will be displayed within circles in the same manner that it is displayed currently. The special page Special:MessageGroupStats can also be used to view per language translation statistics.
Q: Where can I see this in action?
A: This change is already active on translatewiki.net. You can see it in action there:
Q: How will this change affect the ULS for other projects like Wikipedia? Currently, the ULS in Wikipedia shows and links to Wikipedias that have the translated version of the same article in other languages. How will this new workflow affect the Wikipedia User Interface?
A: This change will not have any impact on projects that do not use the Translate extension and as such Wikipedia and its sister sites will not be impacted.
Q: This new ULS menu design shows 20 languages before scrolling. Does it mean I have to scroll and skim through maybe 90 languages to access my language if it is the last on the list?
A: No, you won't have to scroll all the way. You can type the two or three letters of your language in the Universal Language Selector for the search to fetch your language translation.
In addition, the Universal Language Selector uses different techniques to determine which languages will be most relevant to you, and displays those at the top.
Q: What is the roll-out plan?
A: We’re planning to enable this on Test Wikipedia first, followed by MediaWiki.org and then roll-out on all wikis where the Translate extension is enabled.
This is awesome. I had to actually hide this languages list with CSS on Meta-wiki several years back because of how distracting it was to me. Good to see I no longer need to hide it for myself.
I use a private mediawiki in my company and today I had a data leak by one of my employee. He has been caught copying and pasting the pages content directly into a Word document. After this I went looking at the page UserPageViewTracker to see its activity. I discovered that this morning he just visited 187 pages which seems very supicious. I wondered if there is any way to get informed when a user has a suspicious activity. I searched for a solution but mediawiki doesn't seem to have one. I thought about using Google Analytics or Matomo to track this activity but it seems impossible to send any alert when a user visits to much pages in a short amount of time. So I'm asking if anybody has a solution for this. Should I create my own extension on Mediawiki, or should I change my wiki to a knowledge database for example, or should I code a python script checking tracking the activity, or should I use a monitoring app? Or is there an easier solution for this?
If the information in question needs to have accesses audited (e.g. it's confidential and your company needs to know who accesses what when), MediaWiki is probably not the right platform for it (though I don't know what software might be a better fit).
I am pleased to announce the following individual as regional members of the U4C, who will fulfill a term until 15 June 2026:
North America (USA and Canada)
Ajraddatz
The following seats were not filled during this special election:
Latin America and Caribbean
Central and East Europe (CEE)
Sub-Saharan Africa
South Asia
The four remaining Community-At-Large seats
Thank you again to everyone who participated in this process and much appreciation to the candidates for your leadership and dedication to the Wikimedia movement and community.
Over the next few weeks, the U4C will begin meeting and planning the 2024-25 year in supporting the implementation and review of the UCoC and Enforcement Guidelines. You can follow their work on Meta-Wiki.
