Wikipedia:چوک
कॉशिरिस विकीपीडियाअस चौकस प्यठ स्वागत।
Contents
- ١ Page Previews (Hovercards) update
- ٢ Improved search in deleted pages archive
- ٣ RfC regarding "Interlinking of accounts involved with paid editing to decrease impersonation"
- ٤ Discussion on synced reading lists
- ٥ Changes to the global ban policy
- ٦ New print to pdf feature for mobile web readers
- ٧ Call for Wikimania 2018 Scholarships
- ٨ User group for Military Historians
- ٩ Editing News #1—2018
- ١٠ Galicia 15 - 15 Challenge
- ١١ Time to bring embedded maps (‘mapframe’) to most Wikipedias
- ١٢ AdvancedSearch
- ١٣ New Wikipedia Library Accounts Available Now (May 2018)
- ١٤ Update on page issues on mobile web
- ١٥ Global preferences are available
- ١٦ Consultation on the creation of a separate user group for editing sitewide CSS/JS
- ١٧ New user group for editing sitewide CSS/JS
- ١٨ Enabling a helpful feature for Template editors
- ١٩ नागरी खोतिर सहयोग
- ٢٠ प्रबंदकुक हक खॉतिर दरखॊस्थ
- ٢١ Editing of sitewide CSS/JS is only possible for interface administrators from now
- ٢٢ Read-only mode for up to an hour on 12 September and 10 October
Page Previews (Hovercards) update[edit]
Hello,
A quick update on the progress of enabling Page Previews (previously named Hovercards) on this project. Page Previews provide a preview of any linked article, giving readers a quick understanding of a related article without leaving the current page. As mentioned in December we're preparing to remove the feature from Beta and make it the default behavior for logged-out users. We have recently made a large update to the code which fixes most outstanding bugs.
Due to some issues with our instrumentation, we delayed our deployment by a few months. We are finally ready to deploy the feature. Page Previews will be off by default and available in the user preferences page for logged-in users the week of July 24th. The feature will be on by default for current beta users and logged-out users. If you would like to preview the feature, you can enable it as a beta feature. For more information see Page Previews. Questions can be left on the talk page in your preferred language.
Thank you again.
Improved search in deleted pages archive[edit]
Please help translate to your language
During Wikimedia Hackathon 2016, the Discovery team worked on one of the items on the 2015 community wishlist, namely enabling searching the archive of deleted pages. This feature is now ready for production deployment, and will be enabled on all wikis, except Wikidata.
Right now, the feature is behind a feature flag - to use it on your wiki, please go to the Special:Undelete page, and add &fuzzy=1 to the URL, like this: https://test.wikipedia.org/w/index.php?title=Special%3AUndelete&fuzzy=1. Then search for the pages you're interested in. There should be more results than before, due to using ElasticSearch indexing (via the CirrusSearch extension).
We plan to enable this improved search by default on all wikis soon (around August 1, 2017). If you have any objections to this - please raise them with the Discovery team via email or on this announcement's discussion page. Like most Mediawiki configuration parameters, the functionality can be configured per wiki.
Once the improved search becomes the default, you can still access the old mode using &fuzzy=0 in the URL, like this: https://test.wikipedia.org/w/index.php?title=Special%3AUndelete&fuzzy=0
Please note that since Special:Undelete is an admin-only feature, this search capability is also only accessible to wiki admins.
Thank you! CKoerner (WMF) (talk) ١٨:٤٠, ٢٥ جولائی ٢٠١٧ (UTC)
RfC regarding "Interlinking of accounts involved with paid editing to decrease impersonation"[edit]
There is currently a RfC open on Meta regarding "requiring those involved with paid editing on Wikipedia to link on their user page to all other active accounts through which they advertise paid Wikipedia editing business."
Note this is to apply to Wikipedia and not necessarily other sister projects, this is only to apply to websites where people are specifically advertising that they will edit Wikipedia for pay and not any other personal, professional, or social media accounts a person may have.
Please comment on meta. Thanks. Send on behalf of User:Doc James.
MediaWiki message delivery (talk) ٢١:٠٦, ١٧ سیٚپٹَمبَر ٢٠١٧ (UTC)
Discussion on synced reading lists[edit]
Discussion on synced reading lists
Hello,
The Reading Infrastructure team at the Wikimedia Foundation is developing a cross-platform reading list service for the mobile Wikipedia app. Reading lists are like bookmark folders in your web browser. They allow readers using the Wikipedia app to bookmark pages into folders to read later. This includes reading offline. Reading lists do not create or alter content in any way..png)
To create Reading Lists, app users will register an account and marked pages will be tied to that account. Reading List account preferences sync between devices. You can read the same pages on different mobile platforms (tablets, phones). This is the first time we are syncing preference data between devices in such a way. We want to hear and address concerns about privacy and data security. We also want to explain why the current watchlist system is not being adapted for this purpose.
Background[edit]
In 2016 the Android team replaced the simple Saved Pages feature with Reading Lists. Reading Lists allow users to bookmark pages into folders and for reading offline. The intent of this feature was to allow "syncing" of these lists for users with many devices. Due to overlap with the Gather feature and related community concerns, this part was put on hold.
The Android team has identified this lack of synching as a major area of complaint from users. They expect lists to sync. The iOS team has held off implementing Reading Lists, as syncing was seen as a "must have" for this feature. A recent technical RfC has allowed these user stories and needs to be unblocked. Initially for Android, then iOS, and with web to potentially follow.
Reading lists are private, stored as part of a user's account, not as a public wiki page. There is no sharing or publishing ability for reading lists. No planned work to make these public. The target audience are people that read Wikipedia and want to bookmark and organize that content in the app. There is a potential for the feature to be available on the web in the future.
Why not watchlists[edit]
Watchlists offer similar functionality to Reading Lists. The Reading Infrastructure team evaluated watchlist infrastructure before exploring other options. In general, the needs of watchlists differ from Reading Lists in a few key ways:
- Reading lists focus on Reading articles, not the monitoring of changes.
- Watchlists are focused on monitoring changes of pages/revisions.
- The Watchlist infrastructure is key to our contributor community for monitoring content changes manually and through the use of automated tools (bots). Because of these needs, expanding the scope of Watchlists to reading purposes will only make the project harder to maintain and add more constraints.
- By keeping the projects separate it is easier to scale resources. We can serve these two different audiences and prioritize the work accordingly. Reading Lists are, by their nature, less critical to the health of Wikipedia/MediaWiki.
- Multi-project support. Reading Lists are by design cross-wiki/project. Watchlists are tied to specific wikis. While there have been many discussion for making them cross-wiki, resolution is not in the near term.
More information can be found on MediaWiki.org where feedback and ideas are welcome.
Thank you
Changes to the global ban policy[edit]
New print to pdf feature for mobile web readers[edit]
New print to pdf feature for mobile web readers
The Readers web team will be deploying a new feature this week to make it easier to download PDF versions of articles on the mobile website.
Providing better offline functionality was one of the highlighted areas from the research done by the New Readers team in Mexico, Nigeria, and India. The teams created a prototype for mobile PDFs which was evaluated by user research and community feedback. The prototype evaluation received positive feedback and results, so development continued.
For the initial deployment, the feature will be available to Google Chrome browsers on Android. Support for other mobile browsers to come in the future. For Chrome, the feature will use the native Android print functionality. Users can choose to download a webpage as a PDF. Mobile print styles will be used for these PDFs to ensure optimal readability for smaller screens.
The feature is available starting Wednesday, Nov 15. For more information, see the project page on MediaWiki.org.
Thank you!
Call for Wikimania 2018 Scholarships[edit]
Hi all,
We wanted to inform you that scholarship applications for Wikimania 2018 which is being held in Cape Town, South Africa on July 18–22, 2018 are now being accepted. Applications are open until Monday, 22 January 2018 23:59 UTC.
Applicants will be able to apply for a partial or full scholarship. A full scholarship will cover the cost of an individual's round-trip travel, shared accommodation, and conference registration fees as arranged by the Wikimedia Foundation. A partial scholarship will cover conference registration fees and shared accommodation. Applicants will be rated using a pre-determined selection process and selection criteria established by the Scholarship Committee and the Wikimedia Foundation, who will determine which applications are successful. To learn more about Wikimania 2018 scholarships, please visit: wm2018:Scholarships.
To apply for a scholarship, fill out the multi-language application form on: https://scholarships.wikimedia.org/apply
It is highly recommended that applicants review all the material on the Scholarships page and the associated FAQ before submitting an application. If you have any questions, please contact: wikimania-scholarships at wikimedia.org or leave a message at: wm2018:Talk:Scholarships. Please help us spread the word and translate pages!
Best regards, David Richfield and Martin Rulsch for the Scholarship Committee ١٩:٢٤, ٢٠ ڈیٚسَمبَر ٢٠١٧ (UTC)
User group for Military Historians[edit]
Greetings,
"Military history" is one of the most important subjects when speak of sum of all human knowledge. To support contributors interested in the area over various language Wikipedias, we intend to form a user group. It also provides a platform to share the best practices between military historians, and various military related projects on Wikipedias. An initial discussion was has been done between the coordinators and members of WikiProject Military History on English Wikipedia. Now this discussion has been taken to Meta-Wiki. Contributors intrested in the area of military history are requested to share their feedback and give suggestions at Talk:Discussion to incubate a user group for Wikipedia Military Historians.
MediaWiki message delivery (talk) ١٠:٤٦, ٢١ ڈیٚسَمبَر ٢٠١٧ (UTC)
Editing News #1—2018[edit]
Read this in another language • Subscription list for this multilingual newsletter
Did you know that you can now use the visual diff tool on any page?
Sometimes, it is hard to see important changes in a wikitext diff. This screenshot of a wikitext diff (click to enlarge) shows that the paragraphs have been rearranged, but it does not highlight the removal of a word or the addition of a new sentence.
If you enable the Beta Feature for "Visual differences", you will have a new option. It will give you a new box at the top of every diff page. This box will let you choose either diff system on any edit.
Click the toggle button to switch between visual and wikitext diffs.
In the visual diff, additions, removals, new links, and formatting changes will be highlighted. Other changes, such as changing the size of an image, are described in notes on the side.
This screenshot shows the same edit as the wikitext diff. The visual diff highlights the removal of one word and the addition of a new sentence.
You can read and help translate the user guide, which has more information about how to use the visual editor.
Since the last newsletter, the Editing Team has spent most of their time supporting the 2017 wikitext editor mode, which is available inside the visual editor as a Beta Feature, and improving the visual diff tool. Their work board is available in Phabricator. You can find links to the work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor, and improving the visual diff tool.
Recent changes[edit]
- The 2017 wikitext editor is available as a Beta Feature on desktop devices. It has the same toolbar as the visual editor and can use the citoid service and other modern tools. The team have been comparing the performance of different editing environments. They have studied how long it takes to open the page and start typing. The study uses data for more than one million edits during December and January. Some changes have been made to improve the speed of the 2017 wikitext editor and the visual editor. Recently, the 2017 wikitext editor opened fastest for most edits, and the 2010 WikiEditor was fastest for some edits. More information will be posted at mw:Contributors/Projects/Editing performance.
- The visual diff tool was developed for the visual editor. It is now available to all users of the visual editor and the 2017 wikitext editor. When you review your changes, you can toggle between wikitext and visual diffs. You can also enable the new Beta Feature for "Visual diffs". The Beta Feature lets you use the visual diff tool to view other people's edits on page histories and Special:RecentChanges. [١]
- Wikitext syntax highlighting is available as a Beta Feature for both the 2017 wikitext editor and the 2010 wikitext editor. [٢]
- The citoid service automatically translates URLs, DOIs, ISBNs, and PubMed id numbers into wikitext citation templates. It is very popular and useful to editors, although it can be a bit tricky to set up. Your wiki can have this service. Please read the instructions. You can ask the team to help you enable citoid at your wiki.
Let's work together[edit]
- The team will talk about editing tools at an upcoming Wikimedia Foundation metrics and activities meeting.
- Wikibooks, Wikiversity, and other communities may have the visual editor made available by default to contributors. If your community wants this, then please contact Dan Garry.
- The
<references />block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. You can request multi-column support for your wiki. [٣] - If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Thank you!
Galicia 15 - 15 Challenge[edit]
Wikipedia:Galicia 15 - 15 Challenge is a public writing competition which will improve improve and translate this list of 15 really important articles into as many languages as possible. Everybody can help in any language to collaborate on writing and/or translating articles related to Galicia. To participate you just need to sign up here. Thank you very much.--Breogan2008 (talk) ١٤:١٥, ١٢ مارچ ٢٠١٨ (UTC)
Time to bring embedded maps (‘mapframe’) to most Wikipedias[edit]
Time to bring embedded maps (‘mapframe’) to most Wikipedias
Please help translate to your language
Mapframe is a feature that enables users to easily display interactive maps right on wiki pages. Currently, most Wikipedias don’t have mapframe. But fifteen Wikipedias, along with all the other Wikimedia projects, are using mapframe today to display maps on thousands of pages.
A little background: over the last few months, the Foundation’s Collaboration team has been working to improve the stability and user experience of the maps service. In addition, a question about long-term support for the maps service was recently settled, and a small team has been assigned for routine maintenance. Given these developments, bringing the benefits of mapframe to Wikipedias that lack the feature seems both safe and supportable. Nine Wikipedias that use a stricter version of Flagged Revisions will not get mapframe in this release.
Maps are a valuable form of visual data that can improve readers’ understanding across a wide range of topics. If you know of any reasons why mapframe shouldn’t be implemented on your Wikipedia, let us know on the project talk page. Unless we hear from you, we plan to release mapframe to most Wikipedias in May, 2018. So, if you foresee an issue, please let us hear from you. Otherwise, happy mapping!
AdvancedSearch[edit]
New Wikipedia Library Accounts Available Now (May 2018)[edit]
Hello Wikimedians!
The Wikipedia Library is announcing signups today for free, full-access, accounts to research and tools as part of our Publisher Donation Program. You can sign up for new accounts and research materials on the Library Card platform:
- Rock's Backpages – Music articles and interviews from the 1950s onwards - 50 accounts
- Invaluable – Database of more than 50 million auctions and over 500,000 artists - 15 accounts
- Termsoup – Translation tool
Expansions
- Fold3 – Available content has more than doubled, now including new military collections from the UK, Australia, and New Zealand.
- Oxford University Press – The Scholarship collection now includes Electronic Enlightenment
- Alexander Street Press – Women and Social Movements Library now available
- Cambridge University Press – Orlando Collection now available
Many other partnerships with accounts available are listed on our partners page, including Baylor University Press, Loeb Classical Library, Cairn, Gale and Bloomsbury.
Do better research and help expand the use of high quality references across Wikipedia projects: sign up today!
--The Wikipedia Library Team ١٨:٠٣, ٣٠ مٔی ٢٠١٨ (UTC)
- You can host and coordinate signups for a Wikipedia Library branch in your own language. Please contact Ocaasi (WMF).
- This message was delivered via the Global Mass Message tool to The Wikipedia Library Global Delivery List.
Update on page issues on mobile web[edit]
Update on page issues on mobile web
Please help translate to your language Hi everyone. The Readers web team has recently begun working on exposing issue templates on the mobile website. Currently, details about issues with page content are generally hidden on the mobile website. This leaves readers unaware of the reliability of the pages they are reading. The goal of this project is to improve awareness of particular issues within an article on the mobile web. We will do this by changing the visual styling of page issues.
So far, we have drafted a proposal on the design and implementation of the project. We were also able to run user testing on the proposed designs. The tests so far have positive results. Here is a quick summary of what we learned:
- The new treatment increases awareness of page issues among participants. This is true particularly when they are in a more evaluative/critical mode.
- Page issues make sense to readers and they understand how they work
- Readers care about page issues and consider them important
- Readers had overwhelmingly positive sentiments towards Wikipedia associated with learning about page issues
Our next step would be to start implementing these changes. We wanted to reach out to you for any concerns, thoughts, and suggestions you might have before beginning development. Please visit the project page where we have more information and mockups of how this may look. Please leave feedback on the talk page.
Global preferences are available[edit]
Global preferences are now available, you can set them by visiting your new global preferences page. Visit mediawiki.org for information on how to use them and leave feedback. -- Keegan (WMF) (talk)
Consultation on the creation of a separate user group for editing sitewide CSS/JS[edit]
(Please help translate to your language)
Hi all,
I'm preparing a change in who can edit sitewide CSS/JS pages. (These are pages like MediaWiki:Common.css and MediaWiki:Vector.js which are executed in the browser of all readers and editors.) Currently all administrators are able to edit these pages, which poses a serious and unnecessary security risk. Soon, a dedicated, smaller user group will take over this task. Your community will be able to decide who belongs in this group, so this should mean very little change for you. You can find out more and provide feedback at the consultation page on Meta. If you are involved in maintaining CSS/JS code, or policymaking around adminship requests, please give it a look!
Thanks!
Tgr (talk) ٠٨:٤٥, ١٢ جولائی ٢٠١٨ (UTC) (via global message delivery)
New user group for editing sitewide CSS/JS[edit]
(Please help translate to your language)
Hi all!
To improve the security of our readers and editors, permission handling for CSS/JS pages has changed. (These are pages like MediaWiki:Common.css and MediaWiki:Vector.js which contain code that is executed in the browsers of users of the site.)
A new user group, interface-admin, has been created.
Starting four weeks from now, only members of this group will be able edit CSS/JS pages that they do not own (that is, any page ending with .css or .js that is either in the MediaWiki: namespace or is another user's user subpage).
You can learn more about the motivation behind the change here.
Please add users who need to edit CSS/JS to the new group (this can be done the same way new administrators are added, by stewards or local bureaucrats). This is a dangerous permission; a malicious user or a hacker taking over the account of a careless interface-admin can abuse it in far worse ways than admin permissions could be abused. Please only assign it to users who need it, who are trusted by the community, and who follow common basic password and computer security practices (use strong passwords, do not reuse passwords, use two-factor authentication if possible, do not install software of questionable origin on your machine, use antivirus software if that's a standard thing in your environment).
Thanks!
Tgr (talk) ١٣:٠٨, ٣٠ جولائی ٢٠١٨ (UTC) (via global message delivery)
Enabling a helpful feature for Template editors[edit]
Hello.
The team working on TemplateStyles at the Wikimedia Foundation would like to enable TemplateStyles on this wiki.
TemplateStyles is a feature to allow non-administrators to write and manage CSS styles for templates. It allows contributors who edit templates to separate content and presentation. A good web practice that makes it easier to manage the layout of templates. If you don't edit templates, this will not have any impact on your contributions.
TemplateStyles is useful for a few reasons.
- It makes it possible for templates to work better on mobile.
- It cuts out confusion on where to apply CSS rules.
- Editing CSS is currently limited to administrators, which is a major barrier to participation.
- All stylesheets must be loaded on all pages (whether they actually use the page or not), which wastes bandwidth and makes debugging style rules more difficult.
You can learn more about TemplateStyles on MediaWiki.org. Technical documentation is also available.
This is an optional feature and no one must use it, but template contributors are encouraged to do so! Please discuss and let us know if there are any concerns. If there are no concerns we will proceed to deploy the feature on the 9th of August.
Thank you.
नागरी खोतिर सहयोग[edit]
सलाम ओ नमस्कार
नागरी के इस्तिमाल करने वाले कश्मीरियों (मुख्य तौर पर कश्मीरी पंडितों) के लिये कश्मीरी विकिपीडिया की फ़ोर्मेटिंग बेहद खराब है। हाल में लेख लिखने में बहुत तकलीफ आ रही है। इस समस्या को हल करने के लिये क्या राय है? हमें क्या करना चाहिये? अरबी लिपि के साथ साथ देवनागरी भी कश्मीरी भाषा की कंटेम्पररी लिपि है, कम से कम https://gom.wikipedia.org/wiki/ कोंकणी विकिपीडिया की तरह दोनों लिपियों का ही इस्तिमाल होना चाहिये और बराबरी का दर्जा मिलना चाहिये। "Language select" फीचर भी कश्मीरी विकिपीडिया पर उपलब्ध होना चाहिये। कश्मीरी देवनागरी कीबोर्ड भी नहीं मिल रहा हूँ।
इन सब पर जल्द कार्र्वाई किया जाएँ
ऐसा मेरा प्रसाव है, आमसहमति बनाने के लिये
Both Nagari and Arabic are contemporary scripts for the Kashmiri language, it is proposed that a dual format be applied here to allow for the option to read in one or the other, much like as has been done on the Konkani Wikipedia.
--ज़िन्द भुवनेश्वरी (talk) ١٧:٠٨, ٢٣ اَگست ٢٠١٨ (UTC)
प्रबंदकुक हक खॉतिर दरखॊस्थ[edit]
सलाम तॖ नमस्कार
बॖ छुस कोशुर ज़बानुक प्रेमी, मुहिब तॖ यॆह कॉशिरिस विकीपीडियाअस प्यठॖ सरगर्मी प्रबंदक (एड्मिन) इन कमी । लिहॊज़ॖ मॅ दयॗ प्रबंदकुक हक़ ।
शुक्रियॖ !
--ज़िन्द भुवनेश्वरी (talk) ١٧:٠٢, ٢٦ اَگست ٢٠١٨ (UTC)
समर्थन[edit]
खिलॊफ़[edit]
Editing of sitewide CSS/JS is only possible for interface administrators from now[edit]
(Please help translate to your language)
Hi all,
as announced previously, permission handling for CSS/JS pages has changed: only members of the interface-admin (Interface administrators) group, and a few highly privileged global groups such as stewards, can edit CSS/JS pages that they do not own (that is, any page ending with .css or .js that is either in the MediaWiki: namespace or is another user's user subpage). This is done to improve the security of readers and editors of Wikimedia projects. More information is available at Creation of separate user group for editing sitewide CSS/JS. If you encounter any unexpected problems, please contact me or file a bug.
Thanks!
Tgr (talk) ١٢:٤٠, ٢٧ اَگست ٢٠١٨ (UTC) (via global message delivery)
Read-only mode for up to an hour on 12 September and 10 October[edit]
Read this message in another language • Please help translate to your language
The Wikimedia Foundation will be testing its secondary data centre. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.
They will switch all traffic to the secondary data center on Wednesday, 12 September 2018. On Wednesday, 10 October 2018, they will switch back to the primary data center.
Unfortunately, because of some limitations in MediaWiki, all editing must stop when we switch. We apologize for this disruption, and we are working to minimize it in the future.
You will be able to read, but not edit, all wikis for a short period of time.
- You will not be able to edit for up to an hour on Wednesday, 12 September and Wednesday, 10 October. The test will start at 14:00 UTC (15:00 BST, 16:00 CEST, 10:00 EDT, 07:00 PDT, 23:00 JST, and in New Zealand at 02:00 NZST on Thursday 13 September and Thursday 11 October).
- If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.
Other effects:
- Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
- There will be code freezes for the weeks of 10 September 2018 and 8 October 2018. Non-essential code deployments will not happen.
This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. Any changes will be announced in the schedule. There will be more notifications about this. Please share this information with your community. /User:Johan(WMF) (talk)
