User talk:robertsky

The article Jagaddhatri (disambiguation) has been proposed for deletion because of the following concern:
While all constructive contributions to Wikipedia are appreciated, pages may be deleted for any of several reasons.
You may prevent the proposed deletion by removing the {{proposed deletion/dated}} notice, but please explain why in your edit summary or on the article's talk page.
Please consider improving the page to address the issues raised. Removing {{proposed deletion/dated}} will stop the proposed deletion process, but other deletion processes exist. In particular, the speedy deletion process can result in deletion without discussion, and articles for deletion allows discussion to reach consensus for deletion.
This is an automated notification. Please refer to the page's history for further information. DatBot (talk) 00:30, 28 October 2025 (UTC)
"Next Israeli election" listed at Redirects for discussion
[edit]
The redirect Next Israeli election has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Anyone, including you, is welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2025 October 30 ยง Next Israeli election redirects until a consensus is reached.
Note: Multiple related redirects are bundled in this discussion. โMyceteae๐โ๐ซ (talk) 23:25, 30 October 2025 (UTC)
Guide to temporary accounts
[edit]Hello, Robertsky. 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:47, 31 October 2025 (UTC)
Happy First Edit Anniversary Robertsky ๐
[edit]Hey @Robertsky. Your wiki edit anniversary is today, marking 19 years of dedicated contributions to English Wikipedia. Your passion for sharing knowledge and your remarkable contributions have not only enriched the project, but also inspired countless others to contribute. Thank you for your amazing contributions. Wishing you many more wonderful years ahead in the Wiki journey. :) -โโโโโ GnOeee โโโโโ โ 07:51, 31 October 2025 (UTC)
Question from Loula ama on NotebookLM (21:21, 31 October 2025)
[edit]ู ุฑุญุจุง --Loula ama (talk) 21:21, 31 October 2025 (UTC)
Tech News: 2025-45
[edit]Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
- 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). [1]
- For users with "Automatically subscribe to topics" enabled in their preferences, starting a new topic or adding a reply to an existing topic will now subscribe them to replies to that topic. Previously, this would only happen if the DiscussionTools "Add topic" or "Reply" widgets were used. When DiscussionTools was originally launched existing accounts were not opted in to automatic topic subscriptions, so this change should primarily affect newer accounts and users who have deliberately changed their preferences since that time. [2]
- Scribunto modules can now be used to generate SVG images. This can be used to build charts, graphics and other visualizations dynamically through Lua, reducing the need to compose them externally and upload them as files. [3]
- Wikimedia sites now provide all anonymous users with the option to enable a dark mode color scheme, featuring light-colored text on a dark background. This enhancement aims to deliver a more enjoyable reading experience, especially in dimly lit environments. [4]
- Users with large watchlists have long faced timeouts when editing Special:EditWatchlist. The page now loads entries in smaller sections instead of all at once due to a paging update, allowing everyone to edit their watchlists smoothly. As part of the database update, sorting by expiry has been removed because it was over 100ร slower than sorting by title. A community wish has been created to explore alternative ways to restore sort-by-expiry. If this feature is important to you, please support the wish! [5]
View all 31 community-submitted tasks that were resolved last week. For example, the fixing of the persisting highlighting when using VisualEditor find and replace during a query. [6]
Updates for technical contributors
- Since 2019 the Wikimedia URL Shortener at https://w.wiki is available for all Wikimedia wikis to create short links to articles, permalinks, diffs, etc. It is available in the sidebar as "Get shortened URL". There are 30 wikis that also install an older "ShortUrl" extension. The old extension will soon be removed. This means
/s/URLs will not be advertised under article titles via HTMLclass="title-shortlink". The/s/URLs will keep working. [7] - On Thursday, October 30, the MediaWiki Interfaces and SRE Service Operations teams began rerouting Action API traffic through a common API gateway. Individual wikis will be updated based on the standard release groups, with total traffic increased over time. This change is expected to be non-breaking and non-disruptive. If any issues are observed, please file a Phabricator ticket to the Service Ops team board.
- MediaWiki Train deployments will pause for the final two weeks of 2025: 22 December and 29 December. Backport windows will also pause between Monday, 22 December 2025 and Thursday, 2 January 2026. A backport window is a scheduled time to add things like bug fixes and configuration changes. There are seven deployment trains remaining for 2025. [8]
Detailed code updates later this week: MediaWiki
In depth
- In 2025, the Wikimedia Foundation reported that AI systems and search engines increasingly use Wikipedia content without driving users to the site, contributing to an 8% drop in human pageviews compared to 2024. After detecting bots disguised as humans, Wikimedia updated its traffic data to reflect this shift. Read more about current user trends on Wikipedia in a Diff blog post.
Tech news prepared by Tech News writers and posted by bot โข Contribute โข Translate โข Get help โข Give feedback โข Subscribe or unsubscribe.
MediaWiki message delivery 19:31, 3 November 2025 (UTC)
Administrators' newsletter โ November 2025
[edit]News and updates for administrators from the past month (October 2025).

- 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.
- 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
- 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.
- 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!