Wikipedia:Warung Kopi (Teknis)/Arsip/Agustus 2015
Periode baru pemilihan gambar pilihan telah dimulai! (periode 2 dan 3 tahun 2016)[sunting sumber]
MediaWiki message delivery (bicara) 2 Agustus 2015 14.12 (UTC)
Latest 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 ContentTranslation extension has been updated:
- The error page you see when the sites are not working is now simpler and easier to read. It also shows the Wikimedia logo. [6]
- MediaWiki now supports redirects for CSS pages. [7]
- Bots can't guess captchas unlimited times anymore. [8]
Problems
- There was a problem with thumbnails on wikis with local images on July 24 and 25. It was due to a code error. [9]
- We can't search by file type on Wikimedia wikis now. [10]
Changes this week
- The new version of MediaWiki will be on test wikis and MediaWiki.org from August 4. It will be on non-Wikipedia wikis from August 5. It will be on all Wikipedias from August 6 (calendar).
Meetings
- You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs are the most important. The meeting will be on August 4 at 19:00 (UTC). See how to join.
Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
3 Agustus 2015 15.51 (UTC)
Latest 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
- MediaWiki can now hide the signature button when you edit a content page. [11]
- The "Your preferences have been saved" message has changed. You can now see more easily what was saved when you change preferences several times. [12]
- You can now play Ogg video files in some browsers that don't support this format. This solution uses JavaScript and works on desktop browsers only for now. It will work on mobile later. [13]
- You can now use the same tools to edit style in VisualEditor on mobile as in desktop browsers. [14]
- It is now easier to see if there is a JavaScript error in a user or site script. [15]
- JavaScript authors:
- You can no longer use the Sajax library. You can see a list of pages to fix. [16] [17]
- You can no longer use
document.writeon Wikimedia wikis. You can see a list of pages to fix. [18] [19]
- The content translation tool now works better. It is easier to use math, and useless tags are no longer added. [20]
Problems
- More edits have been rejected due to loss of session data lately. This is now fixed. [21]
- Importing a Lua module sometimes didn't work. This is now fixed. [22]
- Text was sometimes lost in the content translation tool. One part of the problem is now fixed. [23]
Changes this week
- The new version of MediaWiki will be on test wikis and MediaWiki.org from August 11. It will be on non-Wikipedia wikis from August 12. It will be on all Wikipedias from August 13 (calendar).
- UploadWizard is getting a new look. The look of buttons and checkboxes has already changed. This week, UploadWizard gets a new date picker. The other text fields will change soon. [24]
- You can now test VisualEditor on mobile devices of all sizes. [25]
Meetings
- You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs are the most important. The meeting will be on August 11 at 19:00 (UTC). See how to join.
Future changes
- Some things in the watchlist will get a new look. [26]
Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
10 Agustus 2015 14.57 (UTC)
Selama ini proyek Gambar pilihan (GP) cuman diurus bagian pengusulannya (itu pun masih nggak terlalu banget), tapi saya baru sadari bahwa pada Wikipedia:Gambar pilihan/Topik ternyata masih belum di-update sejak 2009. Oh ya, berhubung karena semenjak 2009 jumlah slot GP-nya meningkat, pastilah jika semua GP dimasukkan situ semua bakal membludak, maka dari itu sekalian dibuat kaya versi halaman Wikipedia bahasa Inggris-nya donk yakni dibikin jadi sub-sub halaman gitu (NB: subhalaman yang masih ada saat ini cuman Wikipedia:Gambar pilihan/Binatang doank, yang lainnya belum) Mohon dibantu ya pengerjaan peng-update-an ini --Erik Fastman (bicara) 14 Agustus 2015 11.08 (UTC)
VisualEditor News #4—2015[sunting sumber]
Read this in another language • Subscription list for this multilingual newsletter
Did you know?
You can add quotations marks before and after a title or phrase with a single click.
Select the relevant text. Find the correct quotations marks in the special character inserter tool (marked as Ω in the toolbar).
Click the button. VisualEditor will add the quotation marks on either side of the text you selected.
You can read and help translate the user guide, which has more information about how to use VisualEditor.
Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.
Wikimania[sunting sumber]
The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations about VisualEditor and the future of editing.
Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince, जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.
For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).
For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%). There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).
We published some graphs showing the effect of the event on the Translathon page. We thank the translators for participating and the translatewiki.net staff for facilitating this initiative.
Recent improvements[sunting sumber]
Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.
Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top. In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.
Future changes[sunting sumber]
The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.
On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.
Let's work together[sunting sumber]
- Share your ideas and ask questions at mw:VisualEditor/Feedback. This feedback page is now using Flow instead of LiquidThreads.
- Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mediawiki.org if you can help.
- If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
- Please file requests for language-appropriate "Tebal" and "Cetak miring" icons for the styling menu in Phabricator.
- The design research team wants to see how real editors work. Please sign up for their research program.
- The weekly task triage meetings continue to be open to volunteers, usually on Tuesdays at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q1 blocker, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.
If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
—Elitre (WMF), 14 Agustus 2015 22.28 (UTC)
Wiki labels & Revision Scoring as a Service for Indonesian Wikipedia[sunting sumber]
Hello Indonesian Wikipedia,
I apologize for my complete lack of Indonesian skills. I would most welcome if my post is translated to Indonesian.
So computers are very good at crunching numbers. Your average calculator can out smart you in arithmetic. However computers are terrible at pretty much in everything else. Programming computers to under take any task no matter how simple beyond computing tends to be very difficult. This is where Artificial Intelligence comes in. With Artificial Intelligence we teach computers how to solve problems without explicit programming for the solution. This is what we are doing.
We are working on a project called m:Research:Revision scoring as a service which aims to provide quality control Artificial Intelligence infrastructure for Mediawiki and Wikimedia projects. We already have our system implemented and running on Azerbaijani, English, French, Indonesian, Persian, Portuguese, Spanish, Turkish and Vietnamese editions on Wikipedia. We are hoping to adapt our tool to serve Indonesian language as well as a number of other languages.
We are currently mainly focusing on vandalism detection where we provide an API (m:ORES) that provides scores. We have made an effort to keep our system robust.
The examples I'll provide are based on a machine learning algorithm that was trained to use 20,000 reverted edits. This is kind of modelling is problematic for two reasons. First is, there are non-vandalism related reasons for edits to be reverted such as mistakes from new users, this would develop such an unproductive bias. Second problem would be it lacks the ability to distinguish good faith users from malicious ones. To demonstrate our system I will give three examples from English wikipedia. I have picked these three semi-random.
- Score of 90% diff en:Moncef Mezghanni
- As visible in the diff, it is clearly something that shouldn't be welcome on English wikipedia. Algorithms confidence also matches my human assessment.
- Score of 75% diff en:Monin
- When I look at the diff it isn't immediately clear to me if this should be reverted. Detailed look reveals that prior version had more neutral information, but new version at a glance isn't exactly clear cut vandalism, albeit spammy. Algorithms confidence drops just as my human assessment.
- Score of 19% diff en:Curiosity killed the cat, but satisfaction brought it back
- As visible in the diff this edit clearly improves the article. The algorithms confidence plummets as well. Algorithm is more confident that this edit should NOT be reveted.
We are also working towards a system for article quality where we use existing assessment by en:Wikipedia:Version 1.0 Editorial Teamto train our system. We only have this system on English wikipedia at the moment but we would be more than happy to expand to other language editions. I am uncertain if Indonesian Wikipedia has a similar quality assessment scale. I have picked 5 random articles to demonstrate this.
- Predicted: Start class (not even assessed) Perm link en:Maidenhead Advertiser
- Predicted: Stub class (actually marked Stub class) Perm link en:Joel Turrill
- Predicted: C class (actually marked stub class) Perm link en:Kajaanin Haka
- Predicted: C class (actually marked C class) Perm link en:Castell Arnallt
- Predicted: Featured class (actually marked Featured article) Perm link en:Hurricane Diane
Typical problem is that humans typically do not re-asses articles over time or articles are never assessed in the first place. Our system circumvents this problem by automating this.
We have already gathered some language features such as bad words and informal words.
We need a localization of en:Wikipedia:Labels serving as our local landing page. After this is done, we would like to start an edit quality campaign where we request the local community to hand code/label ~2000 revisions labeling them productive/damaging and good faith/bad faith. This would be similar to the campaign on English Wikipedia en:Wikipedia:Labels/Edit quality.
After this we will be able to generate scores for revisions that is usable by gadgets such as ScoredRevisions as well as (potentially) tools like huggle. If community desires it, it can even be used to create a local vandalism reversion bot.
So in a nutshell our algorithm relies on community input to support the community. Feel free to ask any questions. Either here, on meta or on IRC on the freenode server and #wikimedia-ai channel where we hang out. You can also reach us at https://github.com/wiki-ai
-- とある白い猫 chi? 17 Agustus 2015 11.36 (UTC)
Suka ·· Kℇℵ℟ℑℭK 19 Agustus 2015 00.32 (UTC)
Latest 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
- Many Wikipedias can now use information from any Wikidata item in any Wikipedia article. Before they could only use the Wikidata item that matched the subject of the article. [27] [28] [29]
- Some auto-saving problems and other issues in the Content Translation tool are now fixed. Please report to the Content Translation feedback page if you still have problems. [30]
Problems
- Older gadgets that are not using ResourceLoader are not loading anymore. They need to be updated. [31] [32]
- On August 12 the machine translation servers and the Content Translation tool didn't work. This was fixed on the same day. [33]
Changes this week
- The new version of MediaWiki will be on test wikis and MediaWiki.org from August 18. It will be on non-Wikipedia wikis from August 19. It will be on all Wikipedias from August 20 (calendar).
- You can soon watch when something is added to or removed from a category. [34]
Meetings
- You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs are the most important. The meeting will be on August 18 at 19:00 (UTC). See how to join.
Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
17 Agustus 2015 16.17 (UTC)
Periode baru pemilihan gambar pilihan telah dimulai! (periode 3 dan 4 tahun 2016)[sunting sumber]
MediaWiki message delivery (bicara) 19 Agustus 2015 00.30 (UTC)
Latest 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
- Disambiguation pages are now excluded from the random page function. [35]
Problems
Changes this week
- The new version of MediaWiki will be on test wikis and MediaWiki.org from August 25. It will be on non-Wikipedia wikis from August 26. It will be on all Wikipedias from August 27 (calendar).
Meetings
- You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs are the most important. The meeting will be on August 25 at 19:00 (UTC). See how to join.
Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
24 Agustus 2015 13.02 (UTC)
Your attention please: VisualEditor feedback will be centralized on www.mediawiki.org[sunting sumber]
Hello. The VisualEditor team would like to inform you of a plan to redirect local pages for VisualEditor feedback to the board on mediawiki.org a few weeks from now. This applies to all the wikis where such pages are inactive or have low traffic, including yours. When this happens, editors will be free to use their own language to write on the mediawiki.org's page - although English is the most popular language there. Even feedback left from within VisualEditor with the built-in tool will be posted to the board on mediawiki.org.
Having all the feedback on a single, centralized place mainly means getting faster, more frequent replies and more attention from a higher number of people, including the people who are building the software. It also means chances are high, that editors will find that someone else has already written there about the issues or requests they wanted to post.
Maintaining a local page instead can be cumbersome: it needs to be checked frequently in case someone reports urgent issues. Old threads need to be archived from time to time. Off-topic comments should be removed to keep readability. Feedback left there is sometimes not easily understandable or actionable at all.
We think this will help us in being more effective while processing feedback from a larger pool of wikis, not just the biggest ones. If you have any comments about this announcement, please leave them at my talk page. Thanks for your understanding, Elitre (WMF) 27 Agustus 2015 17.40 (UTC)
Periode baru pemilihan gambar pilihan telah dimulai! (periode 4 dan 5 tahun 2016)[sunting sumber]
MediaWiki message delivery (bicara) 30 Agustus 2015 12.40 (UTC)
Latest 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
- VisualEditor will now automatically create a link when you type in or paste an ISBN, PMID, or RFC. [37][38]
- The link editor in VisualEditor is now a bit wider. It's now the same width as the automatic citation tool. [39]
- VisualEditor gadget authors can no longer use the backwards-compatibility module
ext.visualEditor.viewPageTarget.init. Useext.visualEditor.desktopArticleTarget.initinstead. [40] - Gadget writers can now use mediawiki.ForeignApi to communicate between different Wikimedia wikis. [41]
Changes this week
- The new version of MediaWiki will be on test wikis and MediaWiki.org from September 1. It will be on non-Wikipedia wikis from September 2. It will be on all Wikipedias from September 3 (calendar).
Meetings
- You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs are the most important. The meeting will be on September 1 at 19:00 (UTC). See how to join.
Future changes
- The Wikidata API will be updated with breaking changes. This will probably happen on September 9. [42]
Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
31 Agustus 2015 21.36 (UTC)