tags instead of (untranslated) hashtags in edit summaries.
New tags are available here. Release schedule below:
Sub tickets by date will be child tickets of this epic.
Related Objects
Event TimelineHNordeenWMF moved this task from Needs Triage to Up Next on the Wikipedia-Android-App-Backlog board. Special:Tags).
Next step tickets (to be created by me and @Seddon) will be linked here:
Comment Actions I like the idea that all the proposed tags start with a common prefix, making it easier for filter writers to treat them as a group. I'm not that familiar with tag usage, but I'm wondering if there's some written standard for how this should be done. And if not, then maybe this is a good time to formally establish one so all future projects like this can just do it the same way instead of inventing their own way. I see two broad categories of tags emerging; those that represent user behaviors (mw-replace, mw-rollback, etc), and those that represent essentially internal markers for UX experiments, such as the ones proposed here. A little bit of planning now to nail down syntax, semantics, and namespaces will probably yield good dividends later. I maintain SPI tools (Trizek-WMF added a comment.May 23 2024, 10:20 AM2024-05-23 10:20:22 (UTC+0)
No, it's not a matter of dashes or spaces; just using tags with a link that clearly goes to a proper explanation page for experienced users. GRowth does this for suggested images: https://www.mediawiki.org/wiki/Help:Growth/Tools/Newcomer_Tasks#s-image
In a certain way, the standardization work started. For Suggested images, Growth highlights the audience with Newcomer task and then the task type with Suggested: add images. We did it It allows patrollers to have several options, as they can either select all Newcomers tasks, or specific tasks. We did it for each tag: https://www.mediawiki.org/wiki/Help:Growth/Tools/Newcomer_Tasks. I'm currently working on changing Editing's tagging as well, for Edit Check. The goal is to follow the same idea of granularity of tagging and to provide more meta information to the other users. Comment Actions Some French Wikipedia sysops are complaining about the use of these hashtags, which are also in English. So yeah, tags should replace them (currently in work). But an important detail: they quoted that some edits as dirty. Apps are adding parameters that don't exist in the templates (like caption instead of légende ; but caption is not in the template data). Is there a ticket for this problem? An AbuseFilter was created to block some edits, but I don't know if it's linked to your hashtags. https://fr.wikipedia.org/wiki/Sp%C3%A9cial:Filtre_antiabus/150 Comment Actions
Thanks for the note! There was a ticket (T365252) for this specific issue a while ago, which has been resolved. The current version of the app will attempt to insert images into an infobox only for English wiki articles. (In the case of other languages, e.g. français, it will not try to insert into any templates, and just add the image to the top of the article.) It is possible that the edits you mentioned were made by an earlier version of the app (before ~June 2024), or it could be someone's custom build of the app based on an earlier version. Also, the other hashtags (#WPWPRW2024, #WPWPRW, #WPWP) are completely unfamiliar to us, and definitely don't exist in our source code. These must have been added explicitly by the user into the edit summary when submitting. Comment Actions Noted, @Dbrant. I will share the answers, thanks. I will look elsewhere for #WPWPRW2024, #WPWPRW, #WPWP.
A bit out of topic, but do you think others wikis could benefit from this feature in the future? I'm a few months/weeks out of step with the changes being made left and right. Please consider that your answer is purely informative and that I'm not asking you to engage yourself in any way. Comment Actions
I think the ability to insert an image into the infobox (when it's available) is the ultimate goal. The problem is that not all infoboxes are the same -- On enwiki, there are dozens of different infobox templates, which have different names (not just infobox, but also taxobox, chembox, speciesbox, etc), and many of these use different parameters for the image and caption! Instead of the default image and caption, some use ImageFile and ImageCaption or image_caption. All of these variations need to be basically hard-coded into our algorithm for deciding where to insert it. There's no programmatic way to determine 1) whether a template is an infobox, and 2) which parameters represent an image and caption. This is why we are only attempting to do this for enwiki for now (and only for a subset of possible infoboxes). If we want to expand it to other language wikis, we would need to know the names of all the potential infobox templates, and their corresponding image and caption parameters. Comment Actions It is certainly sub-optimal for different templates to use different parameter names for the same thing. Do you have any examples of templates that use non-standard names? FWIW, this is similar to the problem I raised in T372202. Comment Actions
Sure, just a few examples:
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Disclaimer · |