User talk:Chenzw/Archives/Jun 2023
This is a Wikipedia user talk page.
If you find this page on a site that is not Wikipedia, you are viewing a mirror site. The page may be old and the owner of this page may not have a relationship with sites that are not Wikipedia. The original page is located at http://simple.wikipedia.org/wiki/User_talk:Chenzw/Archives/Jun_2023. |
This is the User talk page for Chenzw, where you can send messages and comments to Chenzw. |
|
|
The Signpost: 5 June 2023
change- News and notes: WMRU director forks new 'pedia, birds flap in top '22 piccy, WMF weighs in on Indian gov's map axe plea
- Featured content: Poetry under pressure
- Traffic report: Celebs, controversies and a chatbot in the public eye
Tech News: 2023-23
changeLatest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
- The RealMe extension allows you to mark URLs on your user page as verified for Mastodon and similar software.
- Citation and footnote editing can now be started from the reference list when using the visual editor. This feature request was voted #2 in the 2023 Community Wishlist Survey. [1]
- Previously, clicking on someone else's link to Recent Changes with filters applied within the URL could unintentionally change your preference for "Group results by page". This has now been fixed. [2]
Problems
- For a few days last week, some tools and bots returned outdated information due to database replication problems, and may have been down entirely while it was being fixed. These issues have now been fixed. [3]
Changes later this week
- The new version of MediaWiki will be on test wikis and MediaWiki.org from 6 June. It will be on non-Wikipedia wikis and some Wikipedias from 7 June. It will be on all wikis from 8 June (calendar).
- Bots will no longer be prevented from making edits because of URLs that match the spam blacklist. [4]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
Tech News: 2023-24
changeLatest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
- The content attribution tools Who Wrote That?, XTools Authorship, and XTools Blame now support the Dutch, German, Hungarian, Indonesian, Japanese, Polish and Portuguese Wikipedias. This was the #7 wish in the 2023 Community Wishlist Survey. [5]
- The Search Preview panel has been deployed on four Wikipedias (Catalan, Dutch, Hungarian and Norwegian). The panel will show an image related to the article (if existing), the top sections of the article, related images (coming from MediaSearch on Commons), and eventually the sister projects associated with the article. [6]
- The RealMe extension now allows administrators to verify URLs for any page, for Mastodon and similar software. [7]
- The default project license has been officially upgraded to CC BY-SA 4.0. The software interface messages have been updated. Communities should feel free to start updating any mentions of the old CC BY-SA 3.0 licensing within policies and related documentation pages. [8]
Problems
- For three days last month, some Wikipedia pages edited with VisualEditor or DiscussionTools had an unintended
__TOC__
(or its localized form) added during an edit. There is a listing of affected pages sorted by wiki, that may still need to be fixed. [9] - Currently, the "Sort this page by default as" feature in VisualEditor is broken. Existing
{{DEFAULTSORT:...}}
keywords incorrectly appear as missing templates in VisualEditor. Developers are exploring how to fix this. In the meantime, those wishing to edit the default sortkey of a page are advised to switch to source editing. [10] - Last week, an update to the delete form may have broken some gadgets or user scripts. If you need to manipulate (empty) the reason field, replace
#wpReason
with#wpReason > input
. See an example fix. [11]
Changes later this week
- The new version of MediaWiki will be on test wikis and MediaWiki.org from 13 June. It will be on non-Wikipedia wikis and some Wikipedias from 14 June. It will be on all wikis from 15 June (calendar).
- VisualEditor will be switched to a new backend on English Wikipedia on Monday, and all other large wikis on Thursday. The change should have no noticeable effect on users, but if you experience any slow loading or other strangeness when using VisualEditor, please report it on the phabricator ticket linked here. [12]
Future changes
- From 5 June to 17 July, the Foundation's Security team is holding a consultation with contributors regarding a draft policy to govern the use of third-party resources in volunteer-developed gadgets and scripts. Feedback and suggestions are warmly welcome at Third-party resources policy on meta-wiki.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
The Signpost: 19 June 2023
change- News and notes: WMF Terms of Use now in force, new Creative Commons licensing
- Featured content: Content, featured
- Recent research: Hoaxers prefer currently-popular topics
Tech News: 2023-25
changeLatest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
Changes later this week
- There is no new MediaWiki version this week.
- There is now a toolbar search popup in the visual editor. You can trigger it by typing
\
or pressingctrl + shift + p
. It can help you quickly access most tools in the editor. [15][16]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
User:ChenzwBot for viwiki
changeHi Chenzw, I've been asked on behalf of the Vietnamese Wikipedia project if it is possible to write and operate the Vietnamese version of ChenzwBot to revert vandalism on that project. I noticed that in the source code you wrote that it was theoretically possible to operate it on other MediaWiki wikis, is that still correct? I've subscribed to this topic and watched your talk page for response, so you don't have to be in a hurry anyway. Thank you and regards, NgocAnMaster (talk) 08:56, 3 June 2023 (UTC)
- ...or if you're unable to do that, just send me an email with your full source code for ChenzwBot. NgocAnMaster (talk) 03:12, 8 June 2023 (UTC)
- (talk page stalker) @NgocAnMaster A part of the source code is published on gitlab. — *Fehufangą ♮ ✉ Talk page 03:28, 8 June 2023 (UTC)
- @Fehufanga Thanks, I mean his full source code, not part of it. NgocAnMaster (talk) 03:32, 8 June 2023 (UTC)
- Hey @NgocAnMaster, thanks for reaching out. It's been a long time since I was actively working on the code, so please give me a while to find the code for training the machine learning models. I will try to get back to you by the end of next week. Chenzw Talk 11:41, 13 June 2023 (UTC)
- Okay, just do your work, I won't be panic. Anyway, your bot's public source code is released under the GPL license, so I hope the development won't be affected much by those license restrictions. NgocAnMaster (talk) 16:16, 14 June 2023 (UTC)
- @NgocAnMaster: The support scripts are now available at [17]. Unfortunately, there is no documentation and there is a lot more hard-coded items than I would have liked, since I didn't anticipate its use on other wikis back then in 2020. Here are some notes:
- The initial starting point is the
train-all.sh
shell script. - There are two important input files that you need to provide:
- rev-main_classifier.txt (1)
- rev-nb_classifier.txt (2)
- The above two files are intended to contain revision IDs to train the LightGBM and Naive Bayes classifier respectively. Do note that revision IDs you pass into (1) will also have their tokens extracted and fed into the training set for the Naive Bayes classifier. In other words: the main classifier is training on only file (1), while the Naive Bayes classifier is trained on both (1) and (2).
- Tokens and input features are extracted during training time and persisted to file, in order to account for revisions that may be deleted in future.
- The files accept one line per revision, in space-delimited format:
- The initial starting point is the
- @NgocAnMaster: The support scripts are now available at [17]. Unfortunately, there is no documentation and there is a lot more hard-coded items than I would have liked, since I didn't anticipate its use on other wikis back then in 2020. Here are some notes:
- Okay, just do your work, I won't be panic. Anyway, your bot's public source code is released under the GPL license, so I hope the development won't be affected much by those license restrictions. NgocAnMaster (talk) 16:16, 14 June 2023 (UTC)
- Hey @NgocAnMaster, thanks for reaching out. It's been a long time since I was actively working on the code, so please give me a while to find the code for training the machine learning models. I will try to get back to you by the end of next week. Chenzw Talk 11:41, 13 June 2023 (UTC)
- @Fehufanga Thanks, I mean his full source code, not part of it. NgocAnMaster (talk) 03:32, 8 June 2023 (UTC)
- (talk page stalker) @NgocAnMaster A part of the source code is published on gitlab. — *Fehufangą ♮ ✉ Talk page 03:28, 8 June 2023 (UTC)
123456 vandalism 123457 good 123458 good
- When the tokens are extracted, each token is also subjected to POS tagging, which is done by the spaCy library. As far as I know, there is no official vi language model in spaCy, but there is one community-maintained model here. Your results may vary.
- F1 score is 0.893 and ROC AUC is 0.937 based on initial tests in 2020. However, these metrics were based on a binary output decision. In practice, the bot obtains a probability score from the model for the vandalism class, and compares it against a pre-configured threshold to judge between vandalism/non-vandalism.
- I am quite sure there is still a lot I have not managed to explain yet, so please feel free to ask if there is anything about the bot code that you need clarification on. Chenzw Talk 15:02, 22 June 2023 (UTC)
- Thanks for that. I'll try and get back to you if anything goes wrong. Have a good day! NgocAnMaster (talk) 13:11, 24 June 2023 (UTC)
Tech News: 2023-26
changeLatest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
- The Action API modules and Special:LinkSearch will now add a trailing
/
to allprop=extlinks
responses for bare domains. This is part of the work to remove duplication in theexternallinks
database table. [18]
Problems
Changes later this week
- The new version of MediaWiki will be on test wikis and MediaWiki.org from 27 June. It will be on non-Wikipedia wikis and some Wikipedias from 28 June. It will be on all wikis from 29 June (calendar).
- The Minerva skin now applies more predefined styles to the
.mbox-text
CSS class. This enables support for mbox templates that use divs instead of tables. Please make sure that the new styles won't affect other templates in your wiki. [21][22] - Gadgets will now load on both desktop and mobile by default. Previously, gadgets loaded only on desktop by default. Changing this default using the
|targets=
parameter is also deprecated and should not be used. You should make gadgets work on mobile or disable them based on the skin (with the|skins=
parameter in MediaWiki:Gadgets-definition) rather than whether the user uses the mobile or the desktop website. Popular gadgets that create errors on mobile will be disabled by developers on the Minerva skin as a temporary solution. [23] - All namespace tabs now have the same browser access key by default. Previously, custom and extension-defined namespaces would have to have their access keys set manually on-wiki, but that is no longer necessary. [24]
- The review form of the Flagged Revisions extension now uses the standardized user interface components. [25]
Future changes
- How media is structured in the parser's HTML output will change in the coming weeks at group2 wikis. This change improves the accessibility of content. You may need to update your site-CSS, or userscripts and gadgets. There are details on what code to check, how to update the code, and where to report any related problems. [26]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.