Hi there DannyS712. I was wondering if you'd be willing to write/have the time to write/know of a script that would allow users to quickly remove a page on a particular wiki from the WD sitelinks on the corresponding item without navigating to WD. Any help would be much appreciated. Cheers, Hiàn (talk) 02:27, 25 September 2019 (UTC)
@Hiàn: To clarify, when looking at, eg "Help" on enwiki (w:Help), have a button to remove the entry from wikidata:Q20033? Why would this be useful? I could probably make one --DannyS712 (talk) 02:29, 25 September 2019 (UTC)
That's about right. I know it sounds like a very niche area of editing (it probablydefinitely is) but I've been going through the "redirects connected to a Wikidata item" cat on Wikivoyage occasionally and I've been thinking a tool to streamline the process would be a bit helpful.
I'm not sure about whether people other than myself would actually use it - if that's sort of the general criteria for writing up your user scripts then this very clearly fails that. Hiàn (talk) 02:35, 25 September 2019 (UTC)
I should be able to whip something up --DannyS712 (talk) 02:36, 25 September 2019 (UTC)
Much appreciated Danny. Hiàn (talk) 02:43, 25 September 2019 (UTC)
We'd love to send you this badge as an actual sticker. If you want, you can use this Google Form to communicate your address so we can ship it to you. Note that we will close the form on October 13, 2019, and all data will be removed shortly afterwards. Details about this external site are provided at the top of the form.
Again, thanks for everything you are doing to make this movement a better (and multilingual!) place: please do not hesitate to reach out if you have questions, and I hope to hear from you soon. --Elitre (WMF), 13:03, 28 September 2019 (UTC)
Management has migrated to phabricator; to report a bug or request a feature, please create a new task with the script's tag
Message translation has been reduced; for common messages that are already translated in mediawiki core, the system translations are used, in order to reduce duplication of efforts
New pages are shown at the start of a site's feed
Log entries are shown at the end of a site's feed
Basic validation has been added to user settings, applied before saving
Site validation has also been added; a site (excluding unique projects like wikidata, meta, commons, etc.) is considered to be valid if it is the form of "language.project", where both the language code and project name are valid. It does not, however, check that the actual site is valid; only that it could be. In other words, even though sco.wiktionary refers to a site that doesn't exist, it is considered valid, because sco is a valid language code (sco.wikipedia is a working site) and wiktionary is a valid project.
BREAKING CHANGE: Backwards compatibility supporting the use of sites as *.*.org (like 'en.wikipedia.org' or 'meta.wikimedia.org'), deprecated in version 1.7.5, will be removed soon; all sites should now be saved as *.* (like 'de.wikinews' or 'fr.wikisource')
BREAKING CHANGE: Storing user sites as window.GlobalWatchlistSites, deprecated in version version 1.11.11, will be removed soon; all settings should be stored in the window.GlobalWatchlistConfig object
Both of these breaking changes will be implemented alongside version 4.0; until then, any use of the config page (m:Special:BlankPage/GlobalWatchlistConfig) will result in saving settings in the newest format
Version 4.0 should be released in around a week. It will include the new features mentioned above, as well as removal of backwards compatibility for settings and sites.
Could you reconsider and push for translation on those updates/archives for 2019? While jawp is not presented as affiliated community, would you have it benefit from keeping updated of the larger circle please. --Omotecho (talk) 15:16, 8 October 2019 (UTC)
Site validation has been tightened. Previously, only the language code and project name had to be valid - now, they must be a valid combination (i.e. en.wikiversity exists, and so is valid, but sco.wikiversity is not valid, because no such wiki exists).
When the global watchlist feed is loading, an OOUI widget will be shown, rather than an animated gif.
An option has been added to no longer group edits to the same page. For now, this isn't very useful, since metadata for the edits (editor, summary, tags, etc.) are not yet shown, but they will be soon. Until then, ungrouped edits are treated the same as pages with only 1 edit - the minor and bot flags are displayed if applicable. If edits are grouped, the minor and bot flags are only shown if they apply to all of the edits.
Starting with version 5.0, there will be an option at the settings page to switch to and from a "stable" version of the script. When activated, the script import in your global.js should be replaced, and then the page refreshed with the new script loaded. The stable script will live at User:DannyS712/Global watchlist/stable.js, and will be updated with each full release. Otherwise, it shouldn't be edited, providing a version that is less prone to bugs as the script is developed.
WARNING: Starting with version 5.1, the option to mark the pages of a site as seen be implemented using the entirewatchlist API option, rather than manually listing the titles. This is being done to simplify the implementation code. This will result in the same functionality as marking all pages as seen via Special:Watchlist (i.e. even if the page isn't visible due to your filter choices, it will still be marked as seen). If you would like to keep using the current method for a while, please switch to the stable branch.
Version 5.0 has just gone live. It includes the new features mentioned above.
Sounds good. About that duplicated texts on your talk page, I didn't mean to do that. Wikiplus automatically posted those duplicates. This is a wikiplus bug and I have faced this problem before. Masum Reza☎ 11:43, 9 November 2019 (UTC)
Hello Danny. What does it mean that you discouraged further translation of pages of the 2017 movement strategy? Regards, --Gereon Kalkuhl (WMF) (talk) 21:34, 14 November 2019 (UTC)
@Gereon Kalkuhl (WMF): it means that, while translations are allowed, they are not a priority for translators and are less visible. I marked them as discouraged to try and direct translation efforts to more current pages - if a translator has the time to translate a page or two, I think its better to focus on the 2018 movement strategy, etc. than the 2017 pages, since those aren't as relevant. Hope this answers your question. Thanks, --DannyS712 (talk) 23:34, 14 November 2019 (UTC)
I am investigating adding more context to each entry that is shown (such as the edit summaries, tags, patrol marks, the user who made the edit, etc.). Is there any desire for such additions? If so, what should be added first, and what is a low priority? Please leave feedback on the relevant phabricator task, phab:T238300.
Site validation has been overhauled. Rather than hard-coding a list of valid sites, users will be able to watch any site where they have an attached local user account. If a site is rejected as invalid, please ensure that there is indeed a local account attached to your global account.
Users will now be alerted regarding the results of attempting to update their settings.
Live updates have been added - when activated, the script will refresh in the background, and then load the new feed, every 7.5 seconds. In the future, this frequency may be configurable.
OOUI icons have been added to most buttons.
There is now an option to eliminate the confirmation dialog when marking all sites as seen.
WARNING: Starting with version 6.1, site aliases currently used when saving settings will be removed, and only sites in the form of `lang.project` will be accepted.
As noted in the last update, marking a site as seen now uses entirewatchlist, which means that any changes to watched pages between when the watchlist was loaded and when the site was "marked as seen" may be ignored.
Version 6.0 was just finalized for the development and stable branches of the script.
A new "fast" mode has been introduced. When used, the watchlist serves as just a list of pages that have been modified, and no longer includes context about the edits themselves.
More information has been added to entries. When edits are not grouped by page, or when there is only 1 edit to a page, minor and bot flags are shown, as well as the user who made the edit, the summary used, and any tags that were applied. When multiple entries are grouped, bot and minor flags are only shown if all of the grouped edits were made by bots or where marked as minor. If only 1 user edited the page, that user's name is still shown, but no summaries or tags are included.
All watchlists are now fetched in parallel, rather than in series, greatly reducing load time.
Most of the source code is now annotated with jsdoc notes, allowing others to more clearly understand and review the code.
I will be looking into creating guidelines to let others contribute to the script; see phab:T238298.