Movatterモバイル変換

[0]ホーム
URL:

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview
List overview
Download

Wikitech-lApril 2025

wikitech-l@lists.wikimedia.org
  • 52 participants
  • 44 discussions
Start a nNew thread
Hey everyone,I’ve noticed a lot of students (including myself) struggling with the pressure of online classes, deadlines, and quizzes — especially with platforms like Capella FlexPath, WGU, and others.If you're overwhelmed, there’s a service I recently came across called Online Classes Help. They assist with everything from discussion posts and assignments to full course completion. Super helpful for those juggling jobs or other responsibilities!Whether you need one-time help or ongoing support, this could really reduce your stress and help you maintain a good GPA. Just make sure to use it ethically — as a support tool, not a shortcut!Has anyone else tried such services? Would love to hear your experiences.Cheers! fpr more info :https://coursefpx.com/online-class-help/
2 2
0 0
Hi all,we're movingirc.wikimedia.org to a new infrastructure [1]. Thisservice is unrelated to the IRC network (Libera) we use for real timediscussions. Insteadirc.wikimedia.org is an IRC service forbroadcasting recent changes events from public Wikimedia wikis to beused by various bots connected to per-wiki IRC channels.irc.wikimedia.org should not be used for any new bots (which shouldrather use Eventstreams[2]), but we still have various important botsrelying on the legacy IRC-based infrastructure.The current setup is full of technical debt and ultimately based on apatched version of a very old release of ircd-ratbox with a relayservice written in Python 2.We are replacing it with a modern standalone implementation in Python,which broadcasts IRC notifications in a format compatible to what iscurrently in use by the legacy setup:https://github.com/paravoid/ircstreamLast week during the SRE Infrastructure Foundations hackathon theircstream production setup was created. All our tests have beensuccessful, so on Thursday October 10 at 08:00 UTC we'll switch theirc.wikimedia.org DNS name to the new setup.No changes are needed to any bots, but if you run into any issuesafter the switch, please notify us in the #wikimedia-sre-foundationsIRC channel or leave a note athttps://phabricator.wikimedia.org/T376014.Cheers,Luca, Simon and MoritzFootnotes:[1]https://wikitech.wikimedia.org/wiki/Irc.wikimedia.org[2]https://wikitech.wikimedia.org/wiki/Event_Platform/EventStreams_HTTP_Service
4 3
0 0
Greetings-With the security/maintenance release of MediaWiki 1.39.11/1.41.5/1.42.4,we would also like to provide this supplementary announcement of MediaWikiextensions and skins with now-public Phabricator tasks, security patchesand backports [1]:SocialProfile+ (T373265 <https://phabricator.wikimedia.org/T373265>, CVE-2025-23074) -Special:EditProfile exposes the contents of profile fields marked"hidden"/friends or "friends of friends" when the privileged user isn't afriend of the user whose profile they edit(ed)https://gerrit.wikimedia.org/r/q/I4b77ced314bc6cea0ef3657a82e7467d3661fe2aGlobalBlocking+ (T377855 <https://phabricator.wikimedia.org/T377855>, CVE-2025-23073) -API list=globalblocks can reveal IP of autoblock if username and IP areincluded in the bgtargets parameterhttps://gerrit.wikimedia.org/r/q/I2a2d32aedf6328be0a9f1b4e04a6567a25f19486RefreshSpecial+ (T378885 <https://phabricator.wikimedia.org/T378885>, CVE-2025-23072) -XSS in Special:RefreshSpecialhttps://gerrit.wikimedia.org/r/q/Ic9547e80a8296d707ad8a157eb8ba7aa26fb08dcDataTransfer+ (T379749 <https://phabricator.wikimedia.org/T379749>, CVE-2025-23081) -Various security vulnerabilities in Extension:DataTransferhttps://gerrit.wikimedia.org/r/q/I773c616db781d2f3f30893ad01ef503bf251a2b3https://gerrit.wikimedia.org/r/q/I7c9de4c8dcdb3276ba923c6bc7c8eef3531324c7https://gerrit.wikimedia.org/r/q/I9223c31f02f31f1e06e1a8cddf7d539cc8d3a3d9https://gerrit.wikimedia.org/r/q/I5e1538a3bf66378810f905834c05626e1d2c82f0https://gerrit.wikimedia.org/r/c/mediawiki/extensions/DataTransfer/+/1093931https://gerrit.wikimedia.org/r/c/mediawiki/extensions/DataTransfer/+/1080451OpenBadges+ (T381220 <https://phabricator.wikimedia.org/T381220>, CVE-2025-23080) -XSSes in Special:BadgeViewhttps://gerrit.wikimedia.org/r/q/Ic9448312fa7f1cbc8feac3f852bc8720568522e2ArticleFeedbackv5+ (T381753 <https://phabricator.wikimedia.org/T381753>, CVE-2025-23079) -XSSes in Extension:ArticleFeedbackv5https://gerrit.wikimedia.org/r/q/I6ee51c8b518bda41739fd666fa2891cc12e79ac3BreadCrumbs2+ (T382043 <https://phabricator.wikimedia.org/T382043>, CVE-2025-23078) -XSS in BreadCrumbs2https://gerrit.wikimedia.org/r/q/I7878f8f7bc067080f80427b90f8d85337f172711The Wikimedia Security Team recommends updating these extensions and/orskins to the current master branch or relevant, supported release branch[2] as soon as possible. Some of the referenced Phabricator tasks above_may_ still be private. Unfortunately, when security issues are reported,sometimes sensitive information is exposed and since Phabricator ishistorical, we cannot make these tasks public without exposing thissensitive information. If you have any additional questions or concernsregarding this update, please feel free to contact security(a)wikimedia.orgor file a security task within Phabricator [3].[1]https://phabricator.wikimedia.org/T375631[2]https://www.mediawiki.org/wiki/Version_lifecycle[3]https://www.mediawiki.org/wiki/Reporting_security_bugs
1 0
0 0

23 Jul '25
Hi all,With MediaWiki at the WMF moving to Kubernetes, it's now time to startrunning manual maintenance scripts there. Any time you would previously SSHto a mwmaint host and run mwscript, follow these steps instead. The old waywill continue working for a little while, but it will be going away.What's familiar:Starting a maintenance script looks like this: rzl@deploy2002:~$ mwscript-k8s --comment="T341553" -- Version.php--wiki=enwikiAny options for the mwscript-k8s tool, as described below, go before the --.After the --, the first argument is the script name; everything else ispassed to the script. This is the same as you're used to passing tomwscript.What's different:- Run mwscript-k8s on a deployment host, not the maintenance host. Eitherdeployment host will work; your job will automatically run in whicheverdata center is active, so you no longer need to change hosts when there’s aswitchover.- You don't need a tmux. By default the tool launches your maintenancescript and exits immediately, without waiting for your job to finish. Ifyou log out of the deployment host, your job keeps running on theKubernetes cluster.- Kubernetes saves the maintenance script's output for seven days aftercompletion. By default, mwscript-k8s prints a kubectl command that you (oranyone else) can paste and run to monitor the output or save it to a file.- As a convenience, you can pass -f (--follow) to mwscript-k8s to immediatelybegin tailing the script output. If you like, you can do this inside a tmuxand keep the same workflow as before. Either way, you can safely disconnectand your script will continue running on Kubernetes. rzl@deploy2002:~$ mwscript-k8s -f -- Version.php --wiki=testwiki [...] MediaWiki version: 1.43.0-wmf.24 LTS (built: 22:35, 23 September 2024)- For scripts that take input on stdin, you can pass --attach tomwscript-k8s, either interactively or in a pipeline. rzl@deploy2002:~$ mwscript-k8s --attach -- shell.php --wiki=testwiki [...] Psy Shell v0.12.3 (PHP 7.4.33 — cli) by Justin Hileman > $wmgRealm = "production" > rzl@deploy2002:~$ cat example_url.txt | mwscript-k8s --attach --purgeList.php [...] Purging 1 urls Done!- Your maintenance script runs in a Docker container which will not outliveit, so it can't save persistent files to disk. Ensure your script logs itsimportant output to stdout, or persists it in a database or other remotestorage.- The --comment flag sets an optional (but encouraged) descriptive label,such as a task number.- Using standard kubectl commands[1][2], you can check the status, and viewthe output, of your running jobs or anyone else's. (Example: `kube_envmw-script codfw; kubectl get pod -l username=rzl`)[1]:https://wikitech.wikimedia.org/wiki/Kubernetes/Kubectl[2]:https://kubernetes.io/docs/reference/kubectl/quick-reference/What's not supported yet:- Maintenance scripts launched automatically on a timer. We're working onmigrating them -- for now, this is for one-off scripts launched by hand.- If your job is interrupted (e.g. by hardware problems), Kubernetes canautomatically move it to another machine and restart it, babysitting ituntil it completes. But we only want to do that if your job is safe torestart. So by default, if your job is interrupted, it will stay stoppeduntil you restart it yourself. Soon, we'll add an option to declare "thisis idempotent, please restart it as needed" and that design is recommendedfor new scripts.- No support yet for mwscriptwikiset, foreachwiki, foreachwikiindblist,etc, but we'll add similar functionality as flags to mwscript_k8s.Your feedback:Let me know by email or IRC, or on Phab (T341553<https://phabricator.wikimedia.org/T341553>). If mwscript-k8s doesn't workfor you, for now you can fall back to using the mwmaint hosts as before --but they will be going away. Please report any problems sooner rather thanlater, so that we can ensure the new system meets your needs before thathappens.Thanks,Reuven, for Service Ops SRE
9 23
0 0
*My apologies for writing in English. Please help translate to yourlanguage.*Hello everyone!We're excited to announce that the next *Language Community Meeting* ishappening soon, *May 30th at 15:00 UTC*! If you’d like to join, simply *signup on the wiki page*<https://www.mediawiki.org/wiki/Wikimedia_Language_and_Product_Localization/…>.This is a participant-driven meeting where we share updates onlanguage-related projects, discuss technical challenges in language wikis,and collaborate on solutions. In our upcoming meeting, we plan to coverresults from a recent language onboarding experiment and hear experiencesfrom a Nigerian contributor who contributes to the Obolo wiki, which waspart of this experiment.*Got a topic to share?* Whether it’s a technical update from your project,a challenge you need help with, or a request for interpretation support,we’d love to hear from you! Feel free to reply to this message or addagenda items to *the document here*<https://etherpad.wikimedia.org/p/language-community-meeting-may-2025>.Also, we wanted to highlight that the 7th edition of the *Language &Internationalization newsletter (April 2025)* is available here: *WikimediaLanguage and Product Localization/Newsletter/2025/April*<https://www.mediawiki.org/wiki/Special:MyLanguage/Wikimedia_Language_and_Pr…>.This newsletter provides updates from the January–March 2025 quarter on newfeature development, improvements in various language-related technicalprojects and support efforts, details about community meetings, and ideasfor contributing to projects. To stay updated, you can subscribe to thenewsletter on its wiki page: *Wikimedia Language and ProductLocalization/Newsletter*<https://www.mediawiki.org/wiki/Special:MyLanguage/Newsletter:Language_and_I…>.Would you be interested in contributing to the technical workaroundlanguage development? There is a newcomer-friendly core namespace-relatedtask waiting for your contribution: *T391725*<https://phabricator.wikimedia.org/T391725>.We look forward to your ideas and participation at the Language CommunityMeeting, see you there!OscarLanguage Diversity Hub
2 2
0 0
Upcoming Codex 2.0 release
by Anne Tomasevich 28 May '25

28 May '25
The Design System Team (DST)[0] is preparing to release the next majorversion of Codex, the design system for Wikimedia. Codex has evolvedsignificantly since the first major version release in late 2023: expandingthe toolkit with a number of new components[1], tokens[2] and icons[3],introducing alternative color modes[4], adding a proper i18n system[5],refactoring components to be compatible with native browser validation[6],supporting the creation of a PHP implementation of the componentlibrary[7], refreshing the documentation, and (finally) getting a uniquelogo. With the upcoming introduction of a revised typography scale andcustomizable font modes[8] along with a handful of other breaking changes,DST has determined this to be an appropriate time for another major versionrelease.==== Timeline ====DST plans to first release a release candidate (rc) of version 2.0.0 thatwill include all known breaking changes. It is anticipated that only one rcversion will be released, but if major issues are discovered, there will beadditional rcs until the build is considered stable enough to be theofficial major version.- v2.0.0-rc.1 will be released on 29 April 2025 and ride the deploymenttrain the week of 5 May 2025- v2.0.0 will be released on 13 May 2025 and ride the train the week of 19May 2025==== Breaking Changes ====Codex 2.0 will include a number of breaking changes that need to beaddressed in downstream code to avoid compatibility issues. These aredetailed in full along with guidance on how to prepare for the release athttps://www.mediawiki.org/wiki/Codex/Release_Timeline/2.0#Breaking_changes.If you are using Codex for a feature actively deployed in Wikimediaproduction, please check to see if the breaking changes apply to your code.DST has already opened Phabricator tasks for known areas that need to beupdated based on codesearch but this is likely not comprehensive.Thank you to everyone who has contributed to the development of Codexthroughout its 1.0 lifespan! We look forward to seeing its use in Wikimediaprojects continue to grow as it further evolves through this next majoriteration.Anne Tomasevich, on behalf of the Design System Team[0]https://www.mediawiki.org/wiki/Design_System_Team[1]https://doc.wikimedia.org/codex/latest/components/overview.html[2]https://doc.wikimedia.org/codex/latest/design-tokens/overview.html[3]https://doc.wikimedia.org/codex/latest/icons/overview.html[4]https://doc.wikimedia.org/codex/latest/using-codex/adrs/08-adr-color-modes.…[5]https://doc.wikimedia.org/codex/latest/using-codex/adrs/10-adr-i18n-for-com…[6]https://doc.wikimedia.org/codex/latest/using-codex/adrs/12-adr-native-const…[7]https://doc.wikimedia.org/codex/latest/using-codex/adrs/11-adr-codex-php.ht…[8]https://doc.wikimedia.org/codex/latest/using-codex/adrs/13-adr-font-modes.h…[9]https://codesearch-beta.wmcloud.org/search-- Anne Tomasevich (she/her)Staff Software Engineer, Design SystemWikimedia Foundation
4 3
0 0
FYI: Edge Uniques
by Brandon Black 13 May '25

13 May '25
Hi everyone,If you follow any technical Wikimedia news, you might have read about thisin Tech News or on Diff already, but in case you missed it: The WikimediaFoundation is working on a system called Edge Uniques which will enable A/Btesting, help mitigate DDoS attacks, and eventually give better visitormetrics.We’re doing this by adding a first-party cookie named "WMF-Uniq" which ishandled *only* on our CDN edge servers directly. This cookie contains arandomly-generated unique identifier and a few bits of minimal metadataabout site visit history. We've explicitly designed this system such thatwe do *not* need to or intend to store these cookies or their identifiersin any databases or logs anywhere on our servers, or forward them to anyother complex parts of our internal server-side infrastructure where therisks of accidental leakage or storage might be higher.It's a fairly unique system, and one that we've tried to design for maximalprivacy preservation and data minimization for Wikimedians while alsomeeting our needs around both A/B testing of reader-oriented features andhelping to control the server load from botnets of various kinds withresource-abusive patterns.The A/B testing portion of this design can record relevant, specific,pre-defined metrics into our analytics databases for those agents selectedfor testing (e.g. "an agent in Test123/GroupA clicked the new bluebutton"), but these metrics records use a temporary, per-experimentderivative identifier created by a one-way hash, making them non-reversibleback to the original cookie identifiers.You can read more details on Meta:https://meta.wikimedia.org/wiki/Edge_UniquesIf you want to talk to us about this, we’re happy to discuss it on theproject talk page:https://meta.wikimedia.org/wiki/Talk:Edge_UniquesWe’re also hosting an office hours/community call to answer questions ordiscuss the topic further on April 29, 14:00 UTC. See more info here:https://meta.wikimedia.org/wiki/Edge_Uniques#Next_steps-- Brandon BlackPrincipal Site Reliability Engineer, SRE Traffic TeamWikimedia Foundation
3 3
0 0

07 May '25
Hello all!The Search Platform Team usually holds an open meeting on the firstWednesday of each month. Come talk to us about anything related toWikimedia search, Wikidata Query Service (WDQS), Wikimedia Commons QueryService (WCQS), etc.!Feel free to add your items to the Etherpad Agenda for the next meeting.Details for our next meeting: Date: Wednesday, May 7, 2025 Time: 15:00-16:00 UTC / 08:00 PST / 11:00 EST / 17:00 CET Etherpad:https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours Google Meet link:https://meet.google.com/vgj-bbeb-uyi Join by phone:https://tel.meet/vgj-bbeb-uyi?pin=8118110806927Have fun and see you soon! Guillaume-- *Guillaume Lederrey* (he/him)Engineering ManagerWikimedia Foundation <https://wikimediafoundation.org/>
1 1
0 0
Gerrit is down for troubleshooting
by Lukasz Sobanski 01 May '25

01 May '25
Hi,Following the Gerrit switchover from gerrit2002 to gerrit1003 earlier todaywe noticed missing changes in the Gerrit interface. We shut down Gerrit toprevent further complications and are troubleshooting in T393034<https://phabricator.wikimedia.org/T393034>.-- Lukasz SobanskiSRE
1 3
0 0

30 Apr '25
Dear Wikidata Community,As part of Wikimedia Deutschland’s 2030 Strategic Direction and in closecollaboration with the Wikimedia Foundation (WMF), the Wikidata team hasset its priorities for 2025 around 4 core themes: ensuring Wikidata cancontinue to grow sustainably, strengthening the diverse community ofeditors who steward and reuse our data, and refining the underlyingplatform services that power everything we build together.We chose these focuses because, first, as Wikidata’s size and impactexpand, it’s crucial that we build systems and policies that keep ourinfrastructure healthy and our data dependable. Second, our communityremains at the heart of everything we do -- whether someone contributes thefirst statement to a brand new Item or runs complex queries that powerresearch and apps. Finally, by refining data access methods “as a service”across our ecosystem, we’ll open the door for all our product teams andthird-party developers to build meaningful services and applications thatcreate positive impact.Supporting sustainable growth means two things this year.We’ll partner with the Wikibase teams to improve federated SPARQL queries.This would allow you pull data seamlessly from multiple Wikibase instanceslowering the barrier to hosting some data in other parts of the WikibaseEcosystem, ensuring everyone can continue to access and edit data reliably.At the same time, we’ll have conversations about data governance guidelinestogether with the Cloud and Suite teams and the wider Wikidata community.This way it's always obvious where different kinds of data belong. Thatclarity helps editors make confident decisions, reduces duplicate work, andlays the foundation for new projects that can flourish alongside Wikidataitself.Strengthening the Wikidata community means making every step ofcontribution easier and more rewarding.Mobile editing has grown in recent years, yet adding or updating statementson a phone still forces many users into “desktop view.” We’ll roll out aprototype that will make editing statements on mobile phones easier. Tohelp more advanced editors and tool builders, we’ll continue growing thevisibility and documentation around EntitySchemas, so that editorseverywhere can adopt these powerful templates and can integrate them out ofthe box. And of course, we’ll bring people together through online andin-person events such as WikidataCon, regional capacity‑building campaignsin Africa, meetups at Wikimania and other conferences, XXX Days events likeData Reuse Days and Lexico Days, and more. By connecting newcomers withexperienced mentors, by highlighting local hubs where editors can supporteach other, and by linking each Item back to its relevant WikiProjects,we’ll nurture more active, diverse, and resilient communities.Our third focus area is Increasing mission-aligned data reuseThe Wikidata For Wikimedia Projects<https://meta.wikimedia.org/wiki/Wikidata_For_Wikimedia_Projects> team willimprove the editing experience and increase productivity of Wikipediacontributors by making it easier for editors to monitor, understand, andact on changes to their watchlisted articles when the edit comes fromWikidata. Displaying Wikidata edits in Watchlist and Recent Changes pagesis an opt-in feature of the user preferences; our aim is to increaseawareness, adoption, and utility of this function by summer 2026.In parallel, we will raise awareness and contributors’ understanding of theWikidata integrations currently being used in the Wikimedia Projectsthrough a community outreach project by hosting an online conference, Wikidataand Sister Projects<https://www.wikidata.org/wiki/Event:Wikidata_and_Sister_Projects>,dedicated to celebrating and informing Wikimedians of the many waysWikidata currently supports the Wikimedia Projects. Additionally, we arereviewing the available documentation on Wikidata integrations to ensure itis updated, comprehensive, and available in multiple core languages.Refining platform services “as a service” is our fourth focus area.We’ll refine data access methods so Wikidata's data can be reused to buildmeaningful services and applications. Specifically, we'll build out searchcapabilities in the REST API so developers can discover and query data moreeasily. We’ll ensure the Wikidata Query Service (WDQS) is optimized for itscore strength of supporting queries that need the graph -- keeping it fastand reliable under complex workloads. Finally, we’ll improve our data dumpsto provide more accessible snapshots and subsets of Wikidata’s data.What does this mean for you?If you’re a mobile‑first contributor, editing from your phone will becomesmooth and straightforward. If you’re a developer or researcher, you’llgain powerful new search endpoints in the REST API, a finely tuned WikidataQuery Service for graph-centric queries, and cleaner, more timely datadumps to build on. If you organize or participate in events, you’ll findmore support and clearer pathways to grow local hubs and share bestpractices. If you’re leveraging Wikidata’s data to support your workflowsand content in other Wikimedia projects, you’ll have access to currentuse-cases, examples and better documentation to refer to. Ultimately, everyupdate we make in this period is designed to give you more confidence, morechoice, and more impact as you add, improve, and reuse the world’s freestructured knowledge.We’ll keep you posted on progress throughout the year and as always,welcome your questions and feedback on the talk page<https://www.wikidata.org/wiki/Wikidata_talk:Development_plan/Wikidata_2025-…>.Thank you for your efforts to drive Wikidata forward.Best regards,The Wikidata TeamWikimedia Deutschland-- *Danny Benjafield*Community Communications ManagerWikidata For Wikimedia ProjectsWikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 BerlinPhone: +49 (0)30-577 11 62-0https://wikimedia.deKeep up to date! Current news and exciting stories about Wikimedia,Wikipedia and Free Knowledge in our newsletter (in German): Subscribe now.<https://www.wikimedia.de/newsletter/>Imagine a world in which every single human being can freely share in thesum of all knowledge. Help us to achieve our vision!https://spenden.wikimedia.deWikimedia Deutschland — Gesellschaft zur Förderung Freien Wissens e. V.Eingetragen im Vereinsregister des Amtsgerichts Charlottenburg, VR 23855 B.Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin,Steuernummer 27/029/42207. Geschäftsführende Vorstände: Franziska Heine
1 0
0 0
Results per page:
[8]ページ先頭
©2009-2025 Movatter.jp