User talk:L29Ah
Sandboxing in Xorg
[edit]First and foremost, references in Wikipedia are not for explaining things but for supporting claims. They must point out to reliable sources so the article can comply with Wikipedia:Verifiability. In that regard, self-published sources are considered not reliable (or else anybody could support literally anything). The provided link falls into that category. Not only that, we don't even know who wrote it; is (s)he "an established expert on the subject matter, whose work in the relevant field has previously been published by reliable third-party publications"? Who knows. (By the way, I am aware that a lot of Wikipedia articles lack of this kind of referencing quality; I have tried to do my best in the sections of the Wayland article that I wrote or modified, and it surely can be improved; unfortunately it's a subject that doesn't have many reliable sources)
If the reference verificability was the only problem then using the Security Extension Specification would be a good starting point. But, as I said in Talk:Wayland (display server protocol), "The fact is, no distribution provides isolation between local X clients as the Wayland model does, not even using SECURITY, XACE or another extension (standard X can't)." There are several problems trying to refute the claim using these extensions[1]: first, there are extensions, not how the X server works by design; second, they are not used by default by any known Linux distro or another operating system; they are not well tested, they are not used, they don't even work with entire classes of X clients (X window managers, screensavers, colour pickers, ...). The user has to manually configure the sandboxing for each X client and hope for it to work. Compare this with whe Wayland scenario where the sandboxing comes by default and the user must do nothing. Now remember what is all about: a section comparing Wayland with X. Do you understand now why I have discarded it? --JavierCantero (talk) 07:58, 1 July 2017 (UTC)
Disambiguation link notification for May 26
[edit]Hi. Thank you for your recent edits. An automated process has detected that when you recently edited Chromium OS, you added a link pointing to the disambiguation page Gentoo (check to confirm | fix with Dab solver). Such links are usually incorrect, since a disambiguation page is merely a list of unrelated topics with similar titles. (Read the FAQ • Join us at the DPL WikiProject.)
It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 09:26, 26 May 2018 (UTC)
![](http://upload.wikimedia.org/wikipedia/commons/thumb/6/66/Orologio_blu.svg/48px-Orologio_blu.svg.png)
L29Ah (block log • active blocks • global blocks • autoblocks • contribs • deleted contribs • abuse filter log • creation log • change block settings • unblock • checkuser (log))
UTRS appeal #23288 was submitted on Nov 18, 2018 00:02:19. This review is now closed.
--UTRSBot (talk) 00:02, 18 November 2018 (UTC)
Disambiguation link notification for July 4
[edit]Hi. Thank you for your recent edits. An automated process has detected that when you recently edited Boron, you added a link pointing to the disambiguation page Boron deficiency (check to confirm | fix with Dab solver). Such links are usually incorrect, since a disambiguation page is merely a list of unrelated topics with similar titles. (Read the FAQ • Join us at the DPL WikiProject.)
It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 13:57, 4 July 2019 (UTC)
Yggdrasil (disambiguation)
[edit]I reverted your edit to Yggdrasil (disambiguation) because I couldn't find any mention of a Yggdrasil mesh net. If I'm mistaken, please revert my edit and add a link to the relevant article. Thanks, Leschnei (talk) 13:55, 24 November 2019 (UTC)
ArbCom 2020 Elections voter message
[edit]ArbCom 2021 Elections voter message
[edit]ArbCom 2022 Elections voter message
[edit]Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2022 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}}
to your user talk page. MediaWiki message delivery (talk) 00:39, 29 November 2022 (UTC)
OrphanReferenceFixer: Help on reversion
[edit]Hi there! I check pages listed in Category:Pages with incorrect ref formatting to try to fix reference errors. Recently, you reverted my fix to Bans on Nazi symbols.
If you did this because the references should be removed from the article, you have misunderstood the situation. Most likely, the article originally contained both <ref name="foo">...</ref>
and one or more <ref name="foo"/>
referring to it. Someone then removed the <ref name="foo">...</ref>
but left the <ref name="foo"/>
, which results in a big red error in the article. I replaced one of the remaining <ref name="foo"/>
with a copy of the <ref name="foo">...</ref>
; I did not re-insert the reference to where it was deleted, I just replaced one of the remaining instances. What you need to do to fix it is to make sure you remove all instances of the named reference so as to not leave any big red error.
If you reverted because I made an actual mistake, please be sure to also correct any reference errors in the page so I won't come back and make the same mistake again. Also, please post an error report at User talk:AnomieBOT so my operator can fix me! If the error is so urgent that I need to be stopped, also post a message at User:AnomieBOT/shutoff/OrphanReferenceFixer. Thanks! AnomieBOT⚡ 00:59, 10 August 2023 (UTC) If you do not wish to receive this message in the future, add {{bots|optout=AnomieBOT-OrphanReferenceFixer}}
to your talk page.
ArbCom 2023 Elections voter message
[edit]Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2023 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}}
to your user talk page. MediaWiki message delivery (talk) 00:35, 28 November 2023 (UTC)
Reminder to vote now to select members of the first U4C
[edit]- You can find this message translated into additional languages on Meta-wiki. Please help translate to other languages.
Dear Wikimedian,
You are receiving this message because you previously participated in the UCoC process.
This is a reminder that the voting period for the Universal Code of Conduct Coordinating Committee (U4C) ends on May 9, 2024. Read the information on the voting page on Meta-wiki to learn more about voting and voter eligibility.
The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members were invited to submit their applications for the U4C. For more information and the responsibilities of the U4C, please review the U4C Charter.
Please share this message with members of your community so they can participate as well.
On behalf of the UCoC project team,
RamzyM (WMF) 23:09, 2 May 2024 (UTC)
- ^ even the more powerful and always forgotten X Access Control Extensions (XACE)