User talk:Beetstra
No signs that the Arbitration Committee is in any form willing to change for the better (as expected).
For years we have been complaining about anchoring, about railroading, about bias. When someone comes before ArbCom, ArbCom has to sanction, no matter how feeble the evidence is. They do not care to properly present the evidence that they make decisions on. They do not care whether the editor has been trying to improve since. And when an editor comes again in front of ArbCom, they will just increase the sanctions - they have been here before so they must be guilty.
It is becoming more and more clear that there is no will, nor possibility to improve.1 This institute should be abandoned - NOW
| |||||
|
I am the main operator of User:COIBot. If you feel that your name is wrongly on the COI reports list because of an unfortunate overlap between your username and a certain link or text, please ask for whitelisting by starting a new subject on my talkpage. For a better answer please include some specific 'diffs' of your edits (you can copy the link from the report page). If you want a quicker response, make your case at WT:WPSPAM or WP:COIN. COIBot - Talk to COIBot - listings - Link reports - User reports - Page reports | |||||
Responding
I will respond to talk messages where they started, trying to keep discussions in one place (you may want to watch this page for some time after adding a question). Otherwise I will clearly state where the discussion will be moved/copied to. Though, with the large number of pages I am watching, it may be wise to contact me here as well if you need a swift response. If I forget to answer, poke me. ON EXTERNAL LINK REMOVAL
There are several discussions about my link removal here, and in my archives. If you want to contact me about my view of this policy, please read and understand WP:NOT, WP:EL, WP:SPAM and WP:A, and read the discussions on my talkpage or in my archives first. My view in a nutshell: External links are not meant to tunnel people away from the wikipedia. Hence, I will remove external links on pages where I think they do not add to the page (per WP:NOT#REPOSITORY and WP:EL), or when they are added in a way that wikipedia defines as spam (understand that wikipedia defines spam as: '... wide-scale external link spamming ...', even if the link is appropriate; also read this). This may mean that I remove links, while similar links are already there or which are there already for a long time. Still, the question is not whether your link should be there, the question may be whether those other links should be there (again, see the wording of the policies and guidelines). Please consider the alternatives before re-adding the link:
If the linkspam of a certain link perseveres, I will not hesitate to report it to the wikiproject spam for blacklisting (even if the link would be appropriate for wikipedia). It may be wise to consider the alternatives before things get to that point. The answer in a nutshell Please consider if the link you want to add complies with the policies and guidelines. If you have other questions, or still have questions on my view of the external link policy, disagree with me, or think I made a mistake in removing a link you added, please poke me by starting a new subject on my talk-page. If you absolutely want an answer, you can try to poke the people at WT:EL or WT:WPSPAM on your specific case. Also, regarding link, I can be contacted on IRC, channel [1]. Reliable sources
I convert inline URL's into references and convert referencing styles to a consistent format. My preferred style is the style provided by cite.php (<ref> and <references/>). When other mechanisms are mainly (but not consistently) used (e.g. {{ref}}/{{note}}/{{cite}}-templates) I will assess whether referencing would benefit from the cite.php-style. Feel free to revert these edits when I am wrong. Converting inline URLs in references may result in data being retrieved from unreliable sources. In these cases, the link may have been removed, and replaced by a {{cn}}. If you feel that the page should be used as a reference (complying with wp:rs!!), please discuss that on the talkpage of the page, or poke me by starting a new subject on my talk-page Note: I am working with some other developers on mediawiki to expand the possibilities of cite.php, our attempts can be followed here and here. If you like these features and want them enabled, please vote for these bugs. Stub/Importance/Notability/Expand/Expert
I am in general against deletion, except when the page really gives misinformation, is clear spam or copyvio. Otherwise, these pages may need to be expanded or rewritten. For very short articles there are the different {{stub}} marks, which clearly state that the article is to be expanded. For articles that do not state why they are notable, I will add either {{importance}} or {{notability}}. In my view there is a distinct difference between these two templates, while articles carrying one of these templates may not be notable, the first template does say the article is probably notable enough, but the contents does not state that (yet). The latter provides a clear concern that the article is not notable, and should probably be {{prod}}ed or {{AfD}}ed. Removing importance-tags does not take away the backlog, it only hides from attention, deleting pages does not make the database smaller. If you contest the notability/importance of an article, please consider adding an {{expert-subject}} tag, or raise the subject on an appropriate wikiproject. Remember, there are many, many pages on the wikipedia, many need attention, so maybe we have to live with a backlog. Having said this, I generally delete the {{expand}}-template on sight. The template is in most cases superfluous, expansion is intrinsic to the wikipedia (for stubs, expansion is already mentioned in that template). |
|
|
Guide to temporary accounts
[edit]Hello, Beetstra. This message is being sent to remind you of significant upcoming changes regarding logged-out editing.
Starting 4 November, logged-out editors will no longer have their IP address publicly displayed. Instead, they will have a temporary account (TA) associated with their edits. Users with some extended rights like administrators and CheckUsers, as well as users with the temporary account IP viewer (TAIV) user right will still be able to reveal temporary users' IP addresses and all contributions made by temporary accounts from a specific IP address or range.
How do temporary accounts work?
- When a logged-out user completes an edit or a logged action for the first time, a cookie will be set in this user's browser and a temporary account tied with this cookie will be automatically created for them. This account's name will follow the pattern:
~2025-12345-67(a tilde, year of creation, a number split into units of 5). - All subsequent actions by the temporary account user will be attributed to this username. The cookie will expire 90 days after its creation. As long as it exists, all edits made from this device will be attributed to this temporary account. It will be the same account even if the IP address changes, unless the user clears their cookies or uses a different device or web browser.
- A record of the IP address used at the time of each edit will be stored for 90 days after the edit. Users with the temporary account IP viewer (TAIV) user right will be able to see the underlying IP addresses.
- As a measure against vandalism, there are two limitations on the creation of temporary accounts:
- There has to be a minimum of 10 minutes between subsequent temporary account creations from the same IP (or /64 range in case of IPv6).
- There can be a maximum of 6 temporary accounts created from an IP (or /64 range) within a period of 24 hours.
Temporary account IP viewer user right
- Administrators may grant the temporary account IP viewer (TAIV) user right to non-administrators who meet the criteria for granting. Importantly, an editor must make an explicit request for the permission (e.g. at WP:PERM/TAIV)—administrators are not permitted to assign the right without a request.
- Administrators will automatically be able to see temporary account IP information once they have accepted the Access to Temporary Account IP Addresses Policy via Special:Preferences or via the onboarding dialog which comes up after temporary accounts are deployed.
Impact for administrators
- It will be possible to block many abusers by just blocking their temporary accounts. A blocked person won't be able to create new temporary accounts quickly if the admin selects the autoblock option.
- It will still be possible to block an IP address or IP range.
- Temporary accounts will not be retroactively applied to contributions made before the deployment. On Special:Contributions, you will be able to see existing IP user contributions, but not new contributions made by temporary accounts on that IP address. Instead, you should use Special:IPContributions for this (see a video about IPContributions in a gallery below).
Rules about IP information disclosure
- Publicizing an IP address gained through TAIV access is generally not allowed (e.g. ~2025-12345-67 previously edited as 192.0.2.1 or ~2025-12345-67's IP address is 192.0.2.1).
- Publicly linking a TA to another TA is allowed if "reasonably believed to be necessary". (e.g.
~2025-12345-67 and ~2025-12345-68 are likely the same person, so I am counting their reverts together toward 3RR
, but not Hey ~2025-12345-68, you did some good editing as ~2025-12345-67) - See Wikipedia:Temporary account IP viewer § What can and can't be said for more detailed guidelines.
Useful tools for patrollers
- It is possible to view if a user has opted-in to view temporary account IPs via the User Info card, available in Preferences → Appearance → Advanced options →
Enable the user info card
- This feature also makes it possible for anyone to see the approximate count of temporary accounts active on the same IP address range.
- Special:IPContributions allows viewing all edits and temporary accounts connected to a specific IP address or IP range.
- Similarly, Special:GlobalContributions supports global search for a given temporary account's activity.
- The auto-reveal feature (see video below) allows users with the right permissions to automatically reveal all IP addresses for a limited time window.
Videos
-
How to use Special:IPContributions
-
How automatic IP reveal works
-
How to use IP Info
-
How to use User Info
Further information and discussion
- For more information and discussion regarding this change, please see the announcement from the Wikimedia Foundation at Wikipedia:Village pump (WMF) § Temporary accounts rollout.
Most of this message was written by Mz7 (source). Thanks, 🎃 SGrabarczuk (WMF) (talk) 02:48, 31 October 2025 (UTC)
A kitten for you!
[edit]
Respected, Sir, Thanks for your kind consideration.
Tempdispacc (talk) 12:56, 4 November 2025 (UTC)
Administrators' newsletter – November 2025
[edit]News and updates for administrators from the past month (October 2025).
Administrator changes
CheckUser changes
Guideline and policy news
- The speedy deletion criteria U5 has been repealed, with U6 and U7 replacing it. See the FAQ for more clarifications.
- Community-designated contentious topics may now be enforced and appealed at the arbitration enforcement noticeboard (AE) as a result of an RfC.
Technical news
- You can enable a handy user info card next to usernames, which when clicked displays edit count, blocks, thanks, and other information. To enable this feature, visit Preferences → Appearance → Advanced options → Enable the user info card
Arbitration
- The arbitration case Transgender healthcare and people has been closed
- Uninvolved administrators may impose an AE participation restriction on any thread at the Arbitration Enforcement noticeboard.
Miscellaneous
- An unreferenced articles backlog drive is happening in November 2025 to reduce the backlog of articles tagged with {{Unreferenced}}. You can help reduce the backlog by adding citations to these articles. Sign up to participate!
ArbCom 2025 Elections voter message
[edit]Hello! Voting in the 2025 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 1 December 2025. 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 2025 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:22, 18 November 2025 (UTC)
Administrators' newsletter – December 2025
[edit]News and updates for administrators from the past month (November 2025).
Administrator changes
CheckUser changes
Technical news
- Starting on November 4, the IP addresses of logged-out editors are no longer being publicly displayed. Instead, they will have a temporary account associated with their edits.
- Administrators will now find that Special:MergeHistory is now significantly more flexible about what it can merge. It can now merge sections taken from the middle of the history of the source (rather than only the start) and insert revisions anywhere in the history of the destination page (rather than only the start). T382958
Miscellaneous
- The December 2025 administrator elections are scheduled from Nov 25 – Dec 15.
- An Articles for Creation backlog drive is happening in December 2025, with over 1,000 drafts awaiting review from the past two months. In addition to AfC participants, all administrators and new page patrollers can help review using the Yet Another AFC Helper Script, which can be enabled in the Gadgets settings. Sign up here to participate!