Колдонуучунун баарлашуулары:Bosogo

Архив

Баарлашуу архиви: 1

Эркюль Пуаро

Саламатсызбы!

Эркюль Пуаро барагы эмне үчүн өчүрүлдү?

Aiyanakk (баарлашуу) 20:52, 11 ноябрь 2024 (UTC)

@Aiyanakk саламатчылык. Мазмуну жок болгону үчүн. Bosogo (баарлашуу) 20:53, 11 ноябрь 2024 (UTC)

Tech News: 2024-46

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• On wikis with the Translate extension enabled, users will notice that the FuzzyBot will now automatically create translated versions of categories used on translated pages. [1]
• View all 29 community-submitted tasks that were resolved last week. For example, the submitted task to use the SecurePoll extension for English Wikipedia's special administrator election was resolved on time. [2]

Updates for technical contributors

• In 1.44.0-wmf-2, the logic of Wikibase function getAllStatements changed to behave like getBestStatements. Invoking the function now returns a copy of values which are immutable. [3]
• Wikimedia REST API users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. The API will be rerouting some page content endpoints from RESTbase to the newer MediaWiki REST API endpoints. The impacted endpoints include getting page/revision metadata and rendered HTML content. These changes will be available on testwiki later this week, with other projects to follow. This change should not affect existing functionality, but active users of the impacted endpoints should verify behavior on testwiki, and raise any concerns on the related Phabricator ticket.

In depth

• Admins and users of the Wikimedia projects where Automoderator is enabled can now monitor and evaluate important metrics related to Automoderator's actions. This Superset dashboard calculates and aggregates metrics about Automoderator's behaviour on the projects in which it is deployed. Thanks to the Moderator Tools team for this Dashboard; you can visit the documentation page for more information about this work. [4]

Meetings and events

• 21 November 2024 (8:00 UTC & 16:00 UTC) - Community call with Wikimedia Commons volunteers and stakeholders to help prioritize support efforts for 2025-2026 Fiscal Year. The theme of this call is how content should be organised on Wikimedia Commons.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 00:07, 12 ноябрь 2024 (UTC)

Tech News: 2024-47

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• Users of Wikimedia sites will now be warned when they create a redirect to a page that doesn't exist. This will reduce the number of broken redirects to red links in our projects. [5]
• View all 42 community-submitted tasks that were resolved last week. For example, Pywikibot, which automates work on MediaWiki sites, was upgraded to 9.5.0 on Toolforge. [6]

Updates for technical contributors

• On wikis that use the FlaggedRevs extension, pages created or moved by users with the appropriate permissions are marked as flagged automatically. This feature has not been working recently, and changes fixing it should be deployed this week. Thanks to Daniel and Wargo for working on this. [7][8]

In depth

• There is a new Diff post about Temporary Accounts, available in more than 15 languages. Read it to learn about what Temporary Accounts are, their impact on different groups of users, and the plan to introduce the change on all wikis.

Meetings and events

• Technical volunteers can now register for the 2025 Wikimedia Hackathon, which will take place in Istanbul, Turkey. Application for travel and accommodation scholarships is open from November 12 to December 10 2024. The registration for the event will close in mid-April 2025. The Wikimedia Hackathon is an annual gathering that unites the global technical community to collaborate on existing projects and explore new ideas.
• Join the Wikimedia Commons community calls this week to help prioritize support for Commons which will be planned for 2025–2026. The theme will be how content should be organised on Wikimedia Commons. This is an opportunity for volunteers who work on different things to come together and talk about what matters for the future of the project. The calls will take place November 21, 2024, 8:00 UTC and 16:00 UTC.
• A Language community meeting will take place November 29, 16:00 UTC to discuss updates and technical problem-solving.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 02:01, 19 ноябрь 2024 (UTC)

Викидеги саясат

1. Кыргыз Википедиясы кыргыз тилинин негизги куралдарынын бири. Сиздин саясатыңызга таң калып алып жатам же сиз жекечиликке өтүп мага "асылып" жатасызбы? "Көз жыргасын деп, кооздоо гана максатында жалган тууларды (жалган маалыматты) кошуп койгонуңуз — жол берилгис аракет" деп сиз эмне себептен мен үчүн жыйынтык чыгарып жатасыз же менин "Көз жыргасын" деген оюмду окуй алып жаткандай сезилип жатат.
2. Экинчи дүйнөлүк согуш барагы боюнча кайра-кайрадан эле жаза берүүнүн себеби эмнеде? Мен сизге чынын түшүндүрүп жаздым, желектердин тарыхый варианттын калыптарга кошууга камданып жатканымды. Дагы бир баса белгилей кеткен жери 5 сааттын ичинде мага сиз эскертме бердиңиз, башкаларга андай мамилеңизди тапкан жокмун! (Балким мен адашып жаткандырмын). Же баштаар замат аякта деген эреже барбы?
3. Дагы мир мисал мен Воркута барагын толуктап жаткан учурда, сиз 23 минуттун ичинде мен кошуп жаткан маалыматтарды жокко чыгырып койдуңуз. Мен бул учурда ал шаардын тарыхы боюнча маалыматтарды чогултуп жатканмын же кошуп жаткан маалыматтарды ар бир минут сайын сактоо керекпи?
4. Эскертмелерде Викинин принциптерине таянасыз, бирок ал жакта убакыт боюнча чектер коюлган эмес. Жада калса эрежелерде 23 минут ичинде баарын толуктап сал деген маалымат да жок!
5. Түштүк океаны деп атоонун себеби. Мен бул океандын аталышын Викидеги башка океандырдын аталышына окшотуруп бир стандартка келтирейин деген максатта кылганмын, себеби башка окендардын аталыштарын текшерип көрсөңуз: Атлантика океаны, Инди океаны, Түндүк Муз океаны. Мен эрежелердин "арал, жарым арал, кырка тоо, жер, деңиз, океан, кысык, дарыя, канал, булуң, көчө, аянт, айыл ж.б.у.с. сөздөр географиялык энчилүү аттарга айкаша келсе, кичине тамга менен бөлөк жазылат: Арал деңизи, Балкаш көлү, Суусамыр өрөөнү, Жазы дарыясы, Курил аралдары" пунктуна таянып жасадым, "Түштүк" деген термин бул океанга энчиленген аталыш эмеспи (дагы баса айтып коёюн мен суроо катары жазып жатам).
6. Мен азыр Викинин принциптериндеги "Википедияда бюракратизм жок" деген пункта таянып бул суроолорду берип жатам. Себиби сиздин кээ бир текстердин жекечилике шек келтирген деп кабыл алып жатам жана эмне себептен "Португалиянын Педро III" ушул сыктуу мааниси жок, аталышы туура эмес, булагы жок барактар сизде суроо туудурбай эле менин кошкондорум эле 23 минуттан баштап эле суроо туудуруп калат дегендей.
7. Чынын айтсам мен Викиге кошкон салымдарымды анализдедим жана жалпысынан жаман эмес, принциптерге жооп берген маалыматтарды кошуп жатам деген тыянакка келдим.
8. Эгер Викиде жарыяланган эрежелерди мен таппай жатсам шилтемелерди берип, багыттка салып коёт деген ниеттемин.

Artelow (баарлашуу) 21:41, 24 ноябрь 2024 (UTC)

@Artelow

1. "Сиздин саясатыңыз" дегенди кантип түшүнсө болот? Анда бул жазганыңыз менен мага асылып жатасызбы ошондо? Википедияда талаш маселе талкуу аркылуу чечилет. Билип туруп, жалган маалыматты жайгаштыруу — жол берилгис аракет, туура эле жаздым.
Жазганыңыз: "Бул туралуу маалыматтым бар болчу жана желектердин тарыхый варианттарын кошууга камданып жаткам...".

2. Биринчи жолу жазганымда: "Маалыматты текшерип кошуу керек!" деп турат. Ал учурда билип туруп, жалган маалымат кошконуңузду билген эмесмин. Аракетиңизди ачыктап бергениңизден кийин, анын жол берилгистиги анык болду, ошондо эскертме калтырдым. Эгеде "бул тууралуу маалыматым бар болчу" деп жазбасаңыз, жооп башкача болмок. Ошондуктан "5 сааттын ичинде эскертме бердиңиз" деп жазбай эле койсоңуз болот, эгер жалган маалыматты, анын жалган экендигин билип туруп (орус. заведомо зная) жайгаштырганыңызды эртерээк билип калсам, эртерээк бермекмин 5 саат күтпөй. Башка жагдайда берилмек эмес. Же жалган маалыматты атайын жайгаштыр деген эреже барбы?

3. Жокко чыгарылганын көргөн жокмун. Туура эмес маалыматты көрдүм — түзөттүм. Маалыматты жоготконуңуз — өз күнөөңүз. Мен түзөтүп жаткан учурда да башка бирөө баракты түзөтүп, сактап койгон учурлар болгон, бирок маалыматым эч өчкөн эмес. Кунт койсоңуз, балким өчмөк эмес.
Дагы бир мисал: балким макаланын аталышын гана карабай, мазмунун окусаңыз, мындай болмок эмес: https://w.wiki/CBL$.

4. 1, 2-пункттарды караңыз.

5. Энчилүү ат деген эмне экенин окусаңыз. Сиздики оп-оңой экен: "бир стандартка келтирүү". Башка факторлорду эске албайт экенсиз. Анда "Түндүк Америка" дегенди "Түндүк Америкасы" деп өзгөртмөк экенсиз. "Түштүк Кыргызстан" → "түштүк Кыргызстаны"? Кыргыз Википедиясы кыргыз тилинин грамматикасына ылайык жазылат. Грамматикага ылайык ар кандай варианттар болот: "Түштүк океан", "Атлантика океаны". "Түштүк океан" — энчилүү ат, "түштүк" — катардагы сөз. "Түштүк океан" деген энчилүү атта "түштүк" — зат атооч. "Атлантика океаны" деген энчилүү атта "Атлантика" зат атооч эмес. Бул элементардуу грамматика. Мындан тышкары сиз булактарга таянышыңыз керек болчу, урдура бербей.

6. "Португалиянын Педро III" макаласын өз убагында көргөнүмдү далилдей аласызбы же жөн эле тийшип жатасызбы? Же Википедиянын админдери робот, жеке жашоосу жок, түзөткөн сайын, соңку түзөтүүлөрдү текшеришет же Википедиядагы ар бир макаланы карап чыгышкан деген ойдосузбу? Эмнеге сиз башкаларга караганда көбүрөөк түзөтүп жатасыз деп сураган жокмунго. Жанагы "Түштүк океан" же каталары көп домендер тууралуу дароо жазмакмын анда 1 жыл күтпөй.

Кошумча: "Португалиянын Педро III" макаласы качан түзүлгөн? Жооп: 2022-ж. 3-июлунда. Эми ошол маалдагы салымымды карап чыгыңыз (мен карап чыктым), сурооңуз өзү чечилет. Муну да алдын ала бир текшерип койгон жоксуз...

7. Сыр ачайын: Википедияда 20 жыл салым кошуп жүргөндөргө да жазышат, сындашат ж.б. нерселерди кылышат. Негизи салымыңыз жакшы болгону үчүн сизге эми эч ким эч бир маселе боюнча жаза албайт бекен? Bosogo (баарлашуу) 23:36, 24 ноябрь 2024 (UTC)

Бул текстеги баардык сындарды кабыл алдым.

Маселенин баары сиздин нейтралдуу эмес жазганыңыздан келип чыгып жатат, бир нерсе десе эле беттен алып "Көз жыргасын деп", "урдура бербей" деген терминдерди колдонууну мен мазактоо деп кабыл алам жана ага жараша жооп бериш керек деп ойлоймун. Анан башканын жазганын бурмалоо дагы туура эмес "Чынын айтсам мен Викиге кошкон салымдарымды анализдедим жана жалпысынан жаман эмес, принциптерге жооп берген маалыматтарды кошуп жатам деген тыянакка келдим." десем, дагы бурмалап "Негизи салымыңыз жакшы болгону үчүн сизге эми эч ким эч бир маселе боюнча жаза албайт бекен?" деп жатасыз. Мен, мага жазбасын же эскертме бербесин деп жаздымбы же кайрылдымбы? Жок, баардыгы сылык негизде болуусу зарыл. Тескерисинче мен адам баласы болгондугумдан мени туура жолго салып, каталарымды айтып туурса кубанычта боломун жана келечекте андай каталарды кайталабашка болгон аракетимди жумшаймын.

Сиздин аргументтүү берген эскертмелериңизди туура кабыл алып, эске алып, суроолор болсо сизге кайрылып эле жүрөмүн. Болочокто да суроо туулса кайрыламын жана жазамын.

Сизден дагы бир жолу өтүнүч, ката кетирсем ток этер жерин белгилеңиз жана жекечиликке өтүп "урдура бербей" деген сымал терминдерди колдонуудан алыс болушуңузду суранам. ""Сиздин саясатыңыз" дегенди кантип түшүнсө болот?" деген текст сиздин кыжырыңызга кандай тийсе, мага менин кылгандарымды бир нерсе менен байланыштырып сыпаттоо, ошондой эле кыжырыма тийет. Artelow (баарлашуу) 09:04, 25 ноябрь 2024 (UTC)

@Artelow

1. "Сиздин саясатыңыз" дегениңиз кыжырыма тийген жок. Болгону, жазганыңызды кандай түшүнсө болот деп сурап жатам. Сизге грамматика ж.б. белгилүү бир нерселер боюнча жазылган болсо, сиз "сиздин саясатыңызга таң калып алып жатам" деп жатасыз. Бул жердин каеринде саясатты көрдүңүз — түшүнүксүз. Мен гана эмес, каалаган ошол маселелер боюнча жаза алмак сизге.

2. Жок, маселе аракеттериңизден чыгып жатат. Википедиянын негизги иш принциптери сизге бир нече жолу жакшы түшүндүрүлүп берилген. Википедия энциклопедия экенин унутпашыңыз керек.

Ошондо жалган маалыматты кошконуңузду кантип түшүнүш керек? Жалган маалыматты кошуу максатын өзүңүз түшүндүрүп берген жоксуз. Тескеринче ак ниетиңизди болжолдоп, "желектердин тарыхый варианттарын кошууга камданып жаткам..." дегениңиздин негизинде: "туулар жалган болсо да, калыптарым даяр болгуча макаланы кооздоп турсун" десе керек дегенге келдим. Же "адаштыруу максатында" десем туура болмокпу?

Ар кандай кылсаңыз болмок, аларды талкуу барагыңызга жазгам:
1) мамлекеттердин өзүн гана кошсо болмок;
2) мамлекеттердин жанына тарыхый тууларды гана кошсо болмок;
3) тийбесе болмок.

Жогорудагы варианттарынын бирин кылсаңыз эмне болот эле? Жооп: 1, 3-варантта калыптын/макаланын көркү бузулмак эмес, 1-варантта болгону туулар кошулмак эмес. 1-жыйынтык: тууларды кошууну көздөгөнсүз. 2-вариантта калыптын/макаланын көркү бузулмак (туусу коюлбаган мамлекеттердин аталыштары калыптын чектери боюнча тегизделмек, туусу барлар туу боюнча тезизделмек). 2-жыйынтык: көрктү көздөгөсүз. Баарын (жообуңузду да) эске алганда эскертмеде жазганыма келебиз.

3. "Негизи салымыңыз жакшы болгону үчүн сизге эми эч ким эч бир маселе боюнча жаза албайт бекен?". Ал сүйлөмдүн маңызы — кандай гана, качантан бери салым кошпоңуз, сизге баары бир жазышат. Ошондо бурмалоо эмнеде? Түшүндүрө бере аласызбы? Муну негизсиз айыптоо деп эсептесе болот.

"Чынын айтсам мен Викиге кошкон салымдарымды анализдедим жана жалпысынан жаман эмес, принциптерге жооп берген маалыматтарды кошуп жатам деген тыянакка келдим" — муну кандай максатта жаздыңыз? Туура эмес түшүнүп калышыңыз мүмкүн деп, ушул жазганыңызга жооп бербешим керек беле? Ошол жазганыңыз боюнча эмне дешим керек эле? Жазганымдын баары "бурмалоо", "мазактоо" экен.

4. Жазганыңызды окуп чыксаңыз биринчиден: "нейтралдуу эмес" (негизсиз айыптоо), "бурмалоо" (негизсиз айыптоо), "мазактоо" (негизсиз айыптоо), "жекечиликке өтүп мага "асылып" жатасызбы" (негизсиз айыптоо), "ага жараша жооп бериш керек деп ойлоймун" (бул сөз кыжырыма тийди дегендин ордуна эскалация), "сизде суроо туудурбай" (тастыкталган жок), "кошуп жаткан маалыматтарды жокко чыгырып койдуңуз" (тастыкталган жок).

5. "Тескерисинче мен адам баласы болгондугумдан мени туура жолго салып, каталарымды айтып туурса кубанычта боломун жана келечекте андай каталарды кайталабашка болгон аракетимди жумшаймын." Артыңыздан эч ким текшерүүгө милдеттүү эмес. Википедиянын негизги принциптери сизге белгилүү. Катышып жатканыңызга салыштырмалуу көп болду. Салымыңызды ошол принциптерге ылайык келтирсеңиз кемчиликтер азаймак. Ошол негизги ката. Иш принцибин өзгөртүү керек деп бир жолу эмес айтылган. Мисал: макалалар булактар менен коштолушу керек деп 2023-ж. 6-майында жазгам, анан 2023-ж. 26-декабрында бир да булагы жок "‎Кыргыз Республикасынын Жогорку Кеңешинин VII чакырылышынын депутаттары" макаласы сыяктуу бир нече макала түзгөнсүз, машиналык котормо аркылуу көптөгөн макала түздүңүз. Муну кантип түшүнүү керек?
Өзүңүздү биринчи кезекте өзүңүз текшеришиңиз керек! Bosogo (баарлашуу) 12:25, 25 ноябрь 2024 (UTC)

1. Кабыл алдым.

2. Жалган менен туура эместин айырмасы ар башкача го. Туунун туура эмес вариантын кошуптурмун аны моюнга алышым зарыл жана алам. Жалган деген тыянак туура эмес, мен Тывага Гондурастын же Кениянын желегин кошкон жерим жок да.

Дагы бир жолу тактоо максатында жооп берип койсоңуз эмне үчүн кээ бир макалалар ушундай суроолорду жана талаш-тартыштарды жаратпайт? Мисалы Улуу Ата-Мекендик согуш барагында сиз жазгандай "жалган" туулар узак убакыт бою колбашчылардын жанында туруп суроо жараткан эмес (Герман империясынын желеги турган)

3. "Чынын айтсам мен Викиге кошкон салымдарымды анализдедим жана жалпысынан жаман эмес, принциптерге жооп берген маалыматтарды кошуп жатам деген тыянакка келдим." бул ой толгоо, сиз аны буруп туруп "бул мага жазбаш керек" дептир деген жыйынтыкка келип, анысы аз келгенсип "Муну негизсиз айыптоо" деп эсептеп жатасыз. Негизсиз айыптоо, деги эле айыктоо экенинин бир дагы изи жок. Сиз Шашып эптеп-септеп түзөтпөңүз! деп жатсаңыз анан жасам да жооп катары, себеби мен эптеп-септеп деген мен такыр макул эмесмин, кандай сапаттагы барактарды кошуп жатканымды да билем!

Дагы деле сиз мен үчүн "Туура эмес түшүнөсүз деп" жазган деп жыйынтык чыгарып жатасыз. Бул менин оюмда дагы жок нерсе эле. Сиз башка бирөө үчүн жыйынтык чыгаруудан алыс болсоңуз.

"Көз жыргасын деп", "урдура бербей" деген терминдерди колдонууну мен мазактоо деп кабыл алам жана ага жараша жооп бериш керек деп ойлоймун деп так жазып жатсам, кайрадан "Жазганымдын баары "бурмалоо", "мазактоо" экен" деп дагы буруп койдуңуз же мен калп айтып жатамбы? Качан мен администратордун жазганынын баары мазактоо же бурмалоо деп кайрылдым эле? Сиз теманын нугун такыр башка жакка буруп салып жатасыз! Бул маалыматтын контекстинен чымчып алып, аны бурмалоо деп эсептелет. Бакырайып эле көрүнүп турат го, адамдын жекечилигин сыпаттоо экени.

4. "нейтралдуу эмес", "бурмалоо", "мазактоо", "асылып жатасызбы", "ага жараша жооп бериш керек деп ойлоймун", "сизде суроо туудурбай" - так эле ушундай, "Көз жыргасын деп", "урдура бербей" деген сиздин кайрылууңуз адамгерчиликке жатабы же мени сиз урдура берген алдамчы катары кабыл алып жатасызбы? Мен сизге кайрылганда бир дагы жолу жекечиликке өткөн жерим жок жана сиздин ар бир кадамга баа же сыпаттоо берген жерим жок.

Так жана нейтралдуу болуш керек! Даги бир жолу Википедия жеке баракчаңыз эмес деп ороңдогонуңуз эмнеси же сиздикиби? Бул басмырлоо же мен калп айтып жатамбы?

5. Дагы деле сиз башка нукка салып кетип жатасыз, эч ким менин артыман текшерүүгө милдеттүү эмес, сиз айтпасаңыз деле мен аны билем же сураныч катары кайрылуу Викинин негизги принциптерине каршы келип калды беле?

Химба макаласын булагы жок түзгөн да мен, сиз айткан сынды кабыл алып ага булак кошуп оңдогон да мен. Депуттар туралуу барактарга булак кошпогон мен, алар ушул себептен башка мейкиндике которулган. Мен тараптан булагы жок экенин билип, сиздин сынды кабыл алдым го. Artelow (баарлашуу) 14:12, 25 ноябрь 2024 (UTC)

@Artelow

2. Бул контекстте айырмасы жок. Маалыматтын жалган экенин билип туруп аны тараттыңыз. Сөздөр менен ойносо болот, бирок бул аракетиңизди өзгөртпөйт. Жообуңуз менен ынанган жокмун, жол берилгис аракеттериңизди актап эле жатасыз. Сиз өз кылганыңыз үчүн жооп бериңиз биринчи кезекте.

3.Жазганыңыздын максаты эмнеде деген суроо берилген. Жооп берген жоксуз. Жооп берсеңиз же жооптон качып жатасызбы?

Өз түшүнүгүм боюнча жооп бердим репликага. Бирөөнүн түшүнүгү бурмалоо эмес, билип алыңыз. Эч бир жаман жери жок репликаларга таарына бересизби? Бирок, таарындым деп, башкаларды негизсиз айыптабашыңыз керек.
Шашып эптеп-септеп түзөткөн болсоңуз (жетим тоолор, домендер, Түштүк океан ж.б.), ошону жазам да. Эч ким антип жазбашы үчүн өзүңүздү жөнгө салыңыз, жоопкерчиликти башкаларга жүктөбөй. Факт менен жооп берген жоксуз. "Аргументтериңиз" жеке оюңуз менен чектелип жатат, бир да шилтеме келтирип, сөзүңүздү далилдей алган жоксуз. Тескеринче негизсиз айыптооңуз аныкталды (Воркута макаласында түзөтүүмдү жокко чыгардыңыз деген, "Португалиянын Педро III" макаласы боюнча). Шилтеме келтирип айптарыңызды жокко чыгардым. Дагы бир жолу мындай көрүнүш кайталанса, чаралар көрүлөт. Өз сөзүңүздү далилдешиңиз керек, далилдей албасаңыз жазбай койгонуңуз оң.

4. Ынанган жокмун, сөздөрдү далилдегенди үйрөнүңүз. Конкреттүү шилтемелерди келтирдим, аларга комментарий берген жоксуз, жооптон качып жатасыз. Бир да жарактуу аргумент уккан жокмун.

5. Википедия бул эксперименттер үчүн аянтчаңыз эмес, эгерде грамматиканы жакшы түшүнө элек болсоңуз, булактарга таянбасаңыз массалык түрдө макалаларды кайра атабаңыз. Мындай көрүнүш боюнча эскертме бердим.

6. Демек туура эмес/жалган маалыматты кошуп жатканыңызды билип туруп, аны кошуп жатасызбы ошондо? Билсеңиз кошпоңуз, дагы бир жолу атайлап жалган маалымат кошулса чаралар көрүлөт. Кабыл алдым деп улам айта берет экенсиз, бирок бир нече айдан кийин кайра эле башталат экен. Bosogo (баарлашуу) 16:33, 25 ноябрь 2024 (UTC)

Мына эми сиздин репликаңыз эми репликага окшоп келе жатат. Бул тексте мен дагы кичине сыпаттоо терминдерин колдондум. Бирок дагы бир жолу кайталап жатам сиз бөйрөктөн шыйрак чыгарып башка адамдардын сөздөрүн бурмалоодон алыс болушуңузду суранам. Дагы башка адамдын акыбалын сыпаттоого такыр эле укук берилген эмес. Мага кайрадан дагы таарынды деп диагноз коюп жатасыз. Мен таарынгандай Вики менин мурасым эмес. Сиз ток этер жерин жазышыңыз керек. Мен сизден айырмаланып, сиздин кылган иштериңизге эптеп-септеп деп баа берген жерим жок, бирок администратордун кылып жатканы нукуралуктун үлгүсү дегендей эреже да, принцип да жок.

Сиз айткан шилтемелердин баарына жооп берип, туура эмес деп табылган пункттар менен макул болсом ал дагы сизге жакпай жатат. Кабыл алам деп айтып кайра кайталана берет деп, кабыл албаймын деп анан сизге окшоп айтышып жатып калышым туура эмес деп мен моюнга алып жатсам, дагы сизде суроо туудуруп жатат.

Ката болгон, азыр дагы каталар Викиде толтура, келечекте да боло берет же идеалдуу түптөлгөн Вики бар бекен.

Туура эмес кылган нерсени мен моюнга алгандан кийин сиз так ошолорго жармашып улам-улам баса белгилей беришиңиз мен үчүн такыр түшүнүксүз болуп турат.

Мен стандарт боюнча суроо берсем аларды буйтап өтүп көз жаздымда калтырып коюп жатасыз жана өзүңүзгө ыңгайлуу жерлерин гана билгилеп. Мисал катары экинчи дүйнөлүк согуштун ажыртылгыс бөлүгү болгон Ата Мекендик согуштагы кол башчылардын жалган туулары, башка тилдеги текстер эмнеге сизде суроо жаратпаган жана жаратпайт, бул дагы мен үчүн түшүнүксүз.

Же мен тарыхый тууларды кошуп жатканда чындыкты айтпай, ий мен билбей калыптырмын десем туура болот беле? Мен сизге ката кетиргенимди так айтсам, туулар калыбы боюнча пландалып жаткан иштерим менен бөлүшкөндү так айтсам ошого жармаштыңыз да калдыңыз. Калп айттып, мен билген эмесмин десем бали дегендей эле көз карашта болуп жатасыз.

Менин кайрылууларымдын эң негизги себеби сиз басмырлап сыпаттоо менен эскертүү калтырууңуз болуп жатат.

Баланча баракта баланча маалыматты туура эмес же жалган деген форматтоо берүү зарыл, сиздин формат баланча баракта баланча маалыматты эптеп-септеп көзгө жакшы көрүнсүн деп жалгандарды кошуп коюптурсуз дегендей болуп жатат.

Сиз башка адам катасын мойнуна алып жатса аны алсыздык деп балабаңыз, мен деле сизге окшоп сөз жедирбей, менин кылганым нукуралуктун эталону дегендей көз карашты кармана алам.

Домендер, жетим тоолор, туулар, океан ж.б. кабыл алдым, туура эмес маалыматтарды оңдодум, келечекте мындай каталарды кетирбегенге аракет кылам деген маанидеги жоопту жазып жатсам эмнеси сизге жакпай жатат. Кайра кайра аргументсиз жооп катары белгилөөнүн себеби түшүнүксүз. Катаны моюнга алуу аргумент эмей анан эмне?

Мен макалаларды кошкондо толук категориясы менен кошууга аракет кылам. Мисалы домендер, сиз аны массалык кошуу дегениңиз менен макулмун. Бул Викинин тереңдик статистикасына терс таасирин тийгизерин түшүнүп турам. Бирок түптөлү этабындагы Викилерде мындай көрүнүштөр болуп келет.

Кептин баары, сиз жекечиликке өтүп, адамдын психологиялык кабыл алуусун божомолдоп жана анын ниетин билбей туруп, билгендей жазганыңызда болуп жатат. Орусча айтканда: вы не должны переходить на личность, не должны оценивать намерение и внутреннее состояние участника в негативном ключе, не зная реальное намерение участника. Artelow (баарлашуу) 18:22, 25 ноябрь 2024 (UTC)

@Artelow

1) "Бурмалоо" боюнча суроого жооп берген жоксуз. Кайра-кайра эле бир репликаны кайтала бергениңиз сизге жардам бербейт.

2) Тоо этер жерин жаздым, өз кемчиликтериңизди моюнга албай, шылтоолорду ойлоп табып жатасыз. Бир да сөзүңүздү шилтеме, талдоо менен негиздей албадыңыз. Ошондуктан бул талкуудан жыйынтык чыгара албай жатасыз. Айтканыңызды негиздегенди үйрөнүшүңүз керек.

3) Дагы бир жолу жазганымды окуп чыгып, суроолорума жооп бериңиз жакшы болмок. Жообуңузду алмайынча, суроолорума жооп алдым деп эсептей албайм. Жообуңузда конкретика жок, баарын аралыштырып, суроомду келтирип жооп бере албай жатасыз/жооп бергиңиз келбей жатат.

4) Жабылган темаларды өзүңүз кайра-кайра демилгелеп жатпайсызбы. Жазып жатпайсызбы: "Көз жыргасын" деген оюмду окуй алып жаткандай сезилип жатат."

Жообум:

Ошондо жалган маалыматты кошконуңузду кантип түшүнүш керек? Жалган маалыматты кошуу максатын өзүңүз түшүндүрүп берген жоксуз. Тескеринче ак ниетиңизди болжолдоп, "желектердин тарыхый варианттарын кошууга камданып жаткам..." дегениңиздин негизинде: "туулар жалган болсо да, калыптарым даяр болгуча макаланы кооздоп турсун" десе керек дегенге келдим. Же "адаштыруу максатында" десем туура болмокпу?

Ар кандай кылсаңыз болмок, аларды талкуу барагыңызга жазгам:

1) мамлекеттердин өзүн гана кошсо болмок;

2) мамлекеттердин жанына тарыхый тууларды гана кошсо болмок;

3) тийбесе болмок.

Жогорудагы варианттарынын бирин кылсаңыз эмне болот эле? Жооп: 1, 3-варантта калыптын/макаланын көркү бузулмак эмес, 1-варантта болгону туулар кошулмак эмес. 1-жыйынтык: тууларды кошууну көздөгөнсүз. 2-вариантта калыптын/макаланын көркү бузулмак (туусу коюлбаган мамлекеттердин аталыштары калыптын чектери боюнча тегизделмек, туусу барлар туу боюнча тезизделмек). 2-жыйынтык: көрктү көздөгөсүз. Баарын (жообуңузду да) эске алганда эскертмеде жазганыма келебиз."Көз жыргасын" деген оюмду окуй алып жаткандай сезилип жатат."

Демек, жыйынтыгым туура чыгыптыр да. Анткени сиз "жок андай эмес", "жок башкача болгон" дегендин ордуна конкретикадан качып, актанып баштадыңыз.

5) Тескеринче, ар бир сурооңузга жооп бердим. Сиз болсо болбогон нерселерди ойлоп чыгып, анын далилдей албай, кайтарым суроолордон баш тартып жатасыз. Бир темадан экинчи темага секирип, берилген суроолорго жооп бергендин ордуна, кайра-кайра эле шилтемесиз, негиздемесиз айыптап жатасыз.

6) Улуу Ата Мекендик согушту жөн коюп, эмне үчүн жалган маалыматты атайын жайгаштырдыңыз, мына ушул суроого жооп бериңиз биринчи, жооптон качпай. Мектепте эмеспиз, "Ваняны карыңыз эмнеге аныкы мындай эмнеге мага болбойт" дегенге жеттиңиз.

7) Эскертме боюнча репликаңызга жооп: 4-пунктта. Негиздеменин пункттары боюнча комментарий бере алган жоксуз, аны менен сөздөрүмдү ырастап жатасыз. Демек эскертме туура берилди, "басмырлоо" дегениңиз эскертмени жактырбай жатканыңыздан чыгып жатат, ошол эле.

8) Ар бир катаңызды чыгара баштасам, таарынасыз кайра. + унутуп калсаңыз талкуу барагыңызды кайрадан окуп чыгыңыз. Баары жазылуу, канча баракта ката, кандай ката ж.б. Домендерден баштап, жетим тоолор менен бүтүп. Кунт коюп түзөтпөгөнүңүздүн кесепети, бул жерден да аны далилдеп жатасыз.

9) Сөз жедирбегенге аргументтериңиз жок, аргументтерди келтиргенди билбей жатасыз. Сөз жедирбегениңиз кайра-кайра кайталоо менен бүтүп жатат. Мындай учурда сиз менен эч ким талкууну улантпайт. Википедия тууралуу түшүнүгүңүз төмөн экен: "эталон", "стандарт". Аргумент келтириңиз деп жатышса, сөз жедирбейм деп жатасыз. Бул мектептин деңгээли.

10) Википедиянын негизги принциптери бар, калганы өзүңүздү актоо. Машиналык котормо, машиналык тормо бойдон кала берет.

11) Акыркы сөздөрүңүздү өзүңүзгө айтыңыз. Мен сизге караганда сөздөрүмдү шилтеме, анализ менен негиздеп бергем, сизде эч нерсе жок. Кеңеш: берилген суроолорго дароо жооп берсеңиз, баш тартпай, ошондо талкуу натыйжалуу болот. Bosogo (баарлашуу) 19:23, 25 ноябрь 2024 (UTC)

Tech News: 2024-48

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• A new version of the standard wikitext editor-mode syntax highlighter will be available as a beta feature later this week. This brings many new features and bug fixes, including right-to-left support, template folding, autocompletion, and an improved search panel. You can learn more on the help page.
• The 2010 wikitext editor now supports common keyboard shortcuts such Ctrl+B for bold and Ctrl+I for italics. A full list of all six shortcuts is available. Thanks to SD0001 for this improvement. [9]
• Starting November 28, Flow/Structured Discussions pages will be automatically archived and set to read-only at the following wikis: bswiki, elwiki, euwiki, fawiki, fiwiki, frwikiquote, frwikisource, frwikiversity, frwikivoyage, idwiki, lvwiki, plwiki, ptwiki, urwiki, viwikisource, zhwikisource. This is done as part of StructuredDiscussions deprecation work. If you need any assistance to archive your page in advance, please contact Trizek (WMF).
• View all 25 community-submitted tasks that were resolved last week. For example, a user creating a new AbuseFilter can now only set the filter to "protected" if it includes a protected variable.

Updates for technical contributors

• The CodeEditor, which can be used in JavaScript, CSS, JSON, and Lua pages, now offers live autocompletion. Thanks to SD0001 for this improvement. The feature can be temporarily disabled on a page by pressing Ctrl+, and un-selecting "Live Autocompletion".
• Tool-maintainers who use the Graphite system for tracking metrics, need to migrate to the newer Prometheus system. They can check this dashboard and the list in the Description of the task T350592 to see if their tools are listed, and they should claim metrics and dashboards connected to their tools. They can then disable or migrate all existing metrics by following the instructions in the task. The Graphite service will become read-only in April. [10]
• The New PreProcessor parser performance report has been fixed to give an accurate count for the number of Wikibase entities accessed. It had previously been resetting after 400 entities. [11]

Meetings and events

• A Language community meeting will take place November 29 at 16:00 UTC. There will be presentations on topics like developing language keyboards, the creation of the Mooré Wikipedia, the language support track at Wiki Indaba, and a report from the Wayuunaiki community on their experiences with the Incubator and as a new community over the last 3 years. This meeting will be in English and will also have Spanish interpretation.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 22:42, 25 ноябрь 2024 (UTC)

Tech News: 2024-49

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• Two new parser functions were added this week. The {{#interwikilink}} function adds an interwiki link and the {{#interlanguagelink}} function adds an interlanguage link. These parser functions are useful on wikis where namespaces conflict with interwiki prefixes. For example, links beginning with MOS: on English Wikipedia conflict with the mos language code prefix of Mooré Wikipedia.
• Starting this week, Wikimedia wikis no longer support connections using old RSA-based HTTPS certificates, specifically rsa-2048. This change is to improve security for all users. Some older, unsupported browser or smartphone devices will be unable to connect; Instead, they will display a connectivity error. See the HTTPS Browser Recommendations page for more-detailed information. All modern operating systems and browsers are always able to reach Wikimedia projects. [12]
• Starting December 16, Flow/Structured Discussions pages will be automatically archived and set to read-only at the following wikis: arwiki, cawiki, frwiki, mediawikiwiki, orwiki, wawiki, wawiktionary, wikidatawiki, zhwiki. This is done as part of StructuredDiscussions deprecation work. If you need any assistance to archive your page in advance, please contact Trizek (WMF). [13]
• This month the Chart extension was deployed to production and is now available on Commons and Testwiki. With the security review complete, pilot wiki deployment is expected to start in the first week of December. You can see a working version on Testwiki and read the November project update for more details.
• View all 23 community-submitted tasks that were resolved last week. For example, a bug with the "Download as PDF" system was fixed. [14]

Updates for technical contributors

• In late February, temporary accounts will be rolled out on at least 10 large wikis. This deployment will have a significant effect on the community-maintained code. This is about Toolforge tools, bots, gadgets, and user scripts that use IP address data or that are available for logged-out users. The Trust and Safety Product team wants to identify this code, monitor it, and assist in updating it ahead of the deployment to minimize disruption to workflows. The team asks technical editors and volunteer developers to help identify such tools by adding them to this list. In addition, review the updated documentation to learn how to adjust the tools. Join the discussions on the project talk page or in the dedicated thread on the Wikimedia Community Discord server (in English) for support and to share feedback.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 22:23, 2 декабрь 2024 (UTC)

Tech News: 2024-50

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• Technical documentation contributors can find updated resources, and new ways to connect with each other and the Wikimedia Technical Documentation Team, at the Documentation hub on MediaWiki.org. This page links to: resources for writing and improving documentation, a new #wikimedia-techdocs IRC channel on libera.chat, a listing of past and upcoming documentation events, and ways to request a documentation consultation or review. If you have any feedback or ideas for improvements to the documentation ecosystem, please contact the Technical Documentation Team.

Updates for editors

Layout change for the Edit Check feature

• Later this week, Edit Check will be relocated to a sidebar on desktop. Edit check is the feature for new editors to help them follow policies and guidelines. This layout change creates space to present people with new Checks that appear while they are typing. The initial results show newcomers encountering Edit Check are 2.2 times more likely to publish a new content edit that includes a reference and is not reverted.
• The Chart extension, which enables editors to create data visualizations, was successfully made available on MediaWiki.org and three pilot wikis (Italian, Swedish, and Hebrew Wikipedias). You can see a working examples on Testwiki and read the November project update for more details.
• Translators in wikis where the mobile experience of Content Translation is available, can now discover articles in Wikiproject campaigns of their interest from the "All collection" category in the articles suggestion feature. Wikiproject Campaign organizers can use this feature, to help translators to discover articles of interest, by adding the <page-collection> </page-collection> tag to their campaign article list page on Meta-wiki. This will make those articles discoverable in the Content Translation tool. For more detailed information on how to use the tool and tag, please refer to the step-by-step guide. [15]
• The Nuke feature, which enables administrators to mass delete pages, now has a multiselect filter for namespace selection. This enables users to select multiple specific namespaces, instead of only one or all, when fetching pages for deletion.
• The Nuke feature also now provides links to the userpage of the user whose pages were deleted, and to the pages which were not selected for deletion, after page deletions are queued. This enables easier follow-up admin-actions. Thanks to Chlod and the Moderator Tools team for both of these improvements. [16]
• The Editing Team is working on making it easier to populate citations from archive.org using the Citoid tool, the auto-filled citation generator. They are asking communities to add two parameters preemptively, archiveUrl and archiveDate, within the TemplateData for each citation template using Citoid. You can see an example of a change in a template, and a list of all relevant templates. [17]
• One new wiki has been created: a Wikivoyage in Indonesian (voy:id:) [18]
• Last week, all wikis had problems serving pages to logged-in users and some logged-out users for 30–45 minutes. This was caused by a database problem, and investigation is ongoing. [19]
• View all 19 community-submitted tasks that were resolved last week. For example, a bug in the Add Link feature has been fixed. Previously, the list of sections which are excluded from Add Link was partially ignored in certain cases. [20][21]

Updates for technical contributors

• Codex, the design system for Wikimedia, now has an early-stage implementation in PHP. It is available for general use in MediaWiki extensions and Toolforge apps through Composer, with use in MediaWiki core coming soon. More information is available in the documentation. Thanks to Doğu for the inspiration and many contributions to the library. [22]
• Wikimedia REST API users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. On December 4, the MediaWiki Interfaces team began rerouting page/revision metadata and rendered HTML content endpoints on testwiki from RESTbase to comparable MediaWiki REST API endpoints. The team encourages active users of these endpoints to verify their tool's behavior on testwiki and raise any concerns on the related Phabricator ticket before the end of the year, as they intend to roll out the same change across all Wikimedia projects in early January. These changes are part of the work to replace the outdated RESTBase system.
• The 2024 Developer Satisfaction Survey is seeking the opinions of the Wikimedia developer community. Please take the survey if you have any role in developing software for the Wikimedia ecosystem. The survey is open until 3 January 2025, and has an associated privacy statement.
• There is no new MediaWiki version this week. [23]

Meetings and events

• The next meeting in the series of Wikimedia Foundation discussions with the Wikimedia Commons community will take place on December 12 at 8:00 UTC and at 16:00 UTC. The topic of this call is new media and new contributors. Contributors from all wikis are welcome to attend.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 22:16, 9 декабрь 2024 (UTC)

Tech News: 2024-51

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• Interested in improving event management on your home wiki? The CampaignEvents extension offers organizers features like event registration management, event/wikiproject promotion, finding potential participants, and more - all directly on-wiki. If you are an organizer or think your community would benefit from this extension, start a discussion to enable it on your wiki today. To learn more about how to enable this extension on your wiki, visit the deployment status page.

Updates for editors

• Users of the iOS Wikipedia App in Italy and Mexico on the Italian, Spanish, and English Wikipedias, can see a personalized Year in Review with insights based on their reading and editing history.
• Users of the Android Wikipedia App in Sub-Saharan Africa and South Asia can see the new Rabbit Holes feature. This feature shows a suggested search term in the Search bar based on the current article being viewed, and a suggested reading list generated from the user’s last two visited articles.
• The global reminder bot is now active and running on nearly 800 wikis. This service reminds most users holding temporary rights when they are about to expire, so that they can renew should they want to. See the technical details page for more information.
• The next issue of Tech News will be sent out on 13 January 2025 because of the end of year holidays. Thank you to all of the translators, and people who submitted content or feedback, this year.
• View all 27 community-submitted tasks that were resolved last week. For example, a bug was fixed in the Android Wikipedia App which had caused translatable SVG images to show the wrong language when they were tapped.

Updates for technical contributors

• There is no new MediaWiki version next week. The next deployments will start on 14 January. [24]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 22:25, 16 декабрь 2024 (UTC)

Қарақалпақстан

досым, Каракалпакстан туралы макалада менин редактировкамды артка кайтарган себебин билсем болама Qaraqalpaq patriyotı (баарлашуу) 05:18, 5 январь 2025 (UTC)

Tech News: 2025-03

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• The Single User Login system is being updated over the next few months. This is the system which allows users to fill out the login form on one Wikimedia site and get logged in on all others at the same time. It needs to be updated because of the ways that browsers are increasingly restricting cross-domain cookies. To accommodate these restrictions, login and account creation pages will move to a central domain, but it will still appear to the user as if they are on the originating wiki. The updated code will be enabled this week for users on test wikis. This change is planned to roll out to all users during February and March. See the SUL3 project page for more details and a timeline.

Updates for editors

• On wikis with PageAssessments installed, you can now filter search results to pages in a given WikiProject by using the inproject: keyword. (These wikis: Arabic Wikipedia, English Wikipedia, English Wikivoyage, French Wikipedia, Hungarian Wikipedia, Nepali Wikipedia, Turkish Wikipedia, Chinese Wikipedia) [25]
• One new wiki has been created: a Википедия in Tigre (w:tig:) [26]
• View all 35 community-submitted tasks that were resolved last week. For example, there was a bug with updating a user's edit-count after making a rollback edit, which is now fixed. [27]

Updates for technical contributors

• Wikimedia REST API users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. Starting the week of January 13, we will begin rerouting some page content endpoints from RESTbase to the newer MediaWiki REST API endpoints for all wiki projects. This change was previously available on testwiki and should not affect existing functionality, but active users of the impacted endpoints may raise issues directly to the MediaWiki Interfaces Team in Phabricator if they arise.
• Toolforge tool maintainers can now share their feedback on Toolforge UI, an initiative to provide a web platform that allows creating and managing Toolforge tools through a graphic interface, in addition to existing command-line workflows. This project aims to streamline active maintainers’ tasks, as well as make registration and deployment processes more accessible for new tool creators. The initiative is still at a very early stage, and the Cloud Services team is in the process of collecting feedback from the Toolforge community to help shape the solution to their needs. Read more and share your thoughts about Toolforge UI.
• For tool and library developers who use the OAuth system: The identity endpoint used for OAuth 1 and OAuth 2 returned a JSON object with an integer in its sub field, which was incorrect (the field must always be a string). This has been fixed; the fix will be deployed to Wikimedia wikis on the week of January 13. [28]
• Many wikis currently use Cite CSS to render custom footnote markers in Parsoid output. Starting January 20 these rules will be disabled, but the developers ask you to not clean up your MediaWiki:Common.css until February 20 to avoid issues during the migration. Your wikis might experience some small changes to footnote markers in Visual Editor and when using experimental Parsoid read mode, but if there are changes these are expected to bring the rendering in line with the legacy parser output. [29]

Meetings and events

• The next meeting in the series of Wikimedia Foundation Community Conversations with the Wikimedia Commons community will take place on January 15 at 8:00 UTC and at 16:00 UTC. The topic of this call is defining the priorities in tool investment for Commons. Contributors from all wikis, especially users who are maintaining tools for Commons, are welcome to attend.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 01:42, 14 январь 2025 (UTC)

Tech News: 2025-04

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• Administrators can mass-delete multiple pages created by a user or IP address using Extension:Nuke. It previously only allowed deletion of pages created in the last 30 days. It can now delete pages from the last 90 days, provided it is targeting a specific user or IP address. [30]
• On wikis that use the Patrolled edits feature, when the rollback feature is used to revert an unpatrolled page revision, that revision will now be marked as "manually patrolled" instead of "autopatrolled", which is more accurate. Some editors that use filters on Recent Changes may need to update their filter settings. [31]
• View all 31 community-submitted tasks that were resolved last week. For example, the Visual Editor's "Insert link" feature did not always suggest existing pages properly when an editor started typing, which has now been fixed.

Updates for technical contributors

• The Structured Discussion extension (also known as Flow) is being progressively removed from the wikis. This extension is unmaintained and causes issues. It will be replaced by DiscussionTools, which is used on any regular talk page. The last group of wikis (Catalan Wikiquote, Wikimedia Finland, Goan Konkani Wikipedia, Kabyle Wikipedia, Portuguese Wikibooks, Wikimedia Sweden) will soon be contacted. If you have questions about this process, please ping Trizek (WMF) at your wiki. [32]
• The latest quarterly Technical Community Newsletter is now available. This edition includes: updates about services from the Data Platform Engineering teams, information about Codex from the Design System team, and more.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 01:37, 21 январь 2025 (UTC)

Thank you for being a medical contributors!

The 2024 Cure Award

In 2024 you were one of the top medical editors in your language. Thank you from Wiki Project Med for helping bring free, complete, accurate, up-to-date health information to the public. We really appreciate you and the vital work you do! Wiki Project Med Foundation is a thematic organization whose mission is to improve our health content. Consider joining for 2025, there are no associated costs. Additionally one of our primary efforts revolves around translating health content. We invite you to try our new workflow if you have not already. Our dashboard automatically collects statistics of your efforts and we are working on tools to automatically improve formating.

Thanks again :-) -- Doc James along with the rest of the team at Wiki Project Med Foundation 06:24, 26 январь 2025 (UTC)

Tech News: 2025-05

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• Patrollers and admins - what information or context about edits or users could help you to make patroller or admin decisions more quickly or easily? The Wikimedia Foundation wants to hear from you to help guide its upcoming annual plan. Please consider sharing your thoughts on this and 13 other questions to shape the technical direction for next year.

Updates for editors

• iOS Wikipedia App users worldwide can now access a personalized Year in Review feature, which provides insights based on their reading and editing history on Wikipedia. This project is part of a broader effort to help welcome new readers as they discover and interact with encyclopedic content.
• Edit patrollers now have a new feature available that can highlight potentially problematic new pages. When a page is created with the same title as a page which was previously deleted, a tag ('Recreated') will now be added, which users can filter for in Атайын:RecentChanges and Атайын:NewPages. [33]
• Later this week, there will be a new warning for editors if they attempt to create a redirect that links to another redirect (a double redirect). The feature will recommend that they link directly to the second redirect's target page. Thanks to the user SomeRandomDeveloper for this improvement. [34]
• Wikimedia wikis allow WebAuthn-based second factor checks (such as hardware tokens) during login, but the feature is fragile and has very few users. The MediaWiki Platform team is temporarily disabling adding new WebAuthn keys, to avoid interfering with the rollout of SUL3 (single user login version 3). Existing keys are unaffected. [35]
• View all 30 community-submitted tasks that were resolved last week.

Updates for technical contributors

• For developers that use the MediaWiki History dumps: The Data Platform Engineering team has added a couple of new fields to these dumps, to support the Temporary Accounts initiative. If you maintain software that reads those dumps, please review your code and the updated documentation, since the order of the fields in the row will change. There will also be one field rename: in the mediawiki_user_history dump, the anonymous field will be renamed to is_anonymous. The changes will take effect with the next release of the dumps in February. [36]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 22:15, 27 январь 2025 (UTC)

Tech News: 2025-06

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• Editors who use the "Special characters" editing-toolbar menu can now see the 32 special characters you have used most recently, across editing sessions on that wiki. This change should help make it easier to find the characters you use most often. The feature is in both the 2010 wikitext editor and VisualEditor. [37]
• Editors using the 2010 wikitext editor can now create sublists with correct indentation by selecting the line(s) you want to indent and then clicking the toolbar buttons.[38] You can now also insert <code> tags using a new toolbar button.[39] Thanks to user stjn for these improvements.
• Help is needed to ensure the citation generator works properly on each wiki.
  • (1) Administrators should update the local versions of the page MediaWiki:Citoid-template-type-map.json to include entries for preprint, standard, and dataset; Here are example diffs to replicate for 'preprint' and for 'standard' and 'dataset'.
  • (2.1) If the citoid map in the citation template used for these types of references is missing, one will need to be added. (2.2) If the citoid map does exist, the TemplateData will need to be updated to include new field names. Here are example updates for 'preprint' and for 'standard' and 'dataset'. The new fields that may need to be supported are archiveID, identifier, repository, organization, repositoryLocation, committee, and versionNumber. [40]
• One new wiki has been created: a Wikipedia in Central Kanuri (w:knc:) [41]
• View all 27 community-submitted tasks that were resolved last week. For example, the OCR (optical character recognition) tool used for Wikisource now supports a new language, Church Slavonic. [42]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 00:09, 4 февраль 2025 (UTC)

Tech News: 2025-07

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• The Product and Technology Advisory Council (PTAC) has published a draft of their recommendations for the Wikimedia Foundation's Product and Technology department. They have recommended focusing on mobile experiences, particularly contributions. They request community feedback at the talk page by 21 February.

Updates for editors

• The "Special pages" portlet link will be moved from the "Toolbox" into the "Navigation" section of the main menu's sidebar by default. This change is because the Toolbox is intended for tools relating to the current page, not tools relating to the site, so the link will be more logically and consistently located. To modify this behavior and update CSS styling, administrators can follow the instructions at T385346. [43]
• As part of this year's work around improving the ways readers discover content on the wikis, the Web team will be running an experiment with a small number of readers that displays some suggestions for related or interesting articles within the search bar. Please check out the project page for more information.
• Template editors who use TemplateStyles can now customize output for users with specific accessibility needs by using accessibility related media queries (prefers-reduced-motion, prefers-reduced-transparency, prefers-contrast, and forced-colors). Thanks to user Bawolff for these improvements. [44]
• View all 22 community-submitted tasks that were resolved last week. For example, the global blocks log will now be shown directly on the Атайын:CentralAuth page, similarly to global locks, to simplify the workflows for stewards. [45]

Updates for technical contributors

• Wikidata now supports a special language as a "default for all languages" for labels and aliases. This is to avoid excessive duplication of the same information across many languages. If your Wikidata queries use labels, you may need to update them as some existing labels are getting removed. [46]
• The function getDescription was invoked on every Wiki page read and accounts for ~2.5% of a page's total load time. The calculated value will now be cached, reducing load on Wikimedia servers. [47]
• As part of the RESTBase deprecation effort, the /page/related endpoint has been blocked as of February 6, 2025, and will be removed soon. This timeline was chosen to align with the deprecation schedules for older Android and iOS versions. The stable alternative is the "morelike" action API in MediaWiki, and a migration example is available. The MediaWiki Interfaces team can be contacted for any questions. [48]

In depth

• The latest quarterly Language and Internationalization newsletter is available. It includes: Updates about the "Contribute" menu; details on some of the newest language editions of Wikipedia; details on new languages supported by the MediaWiki interface; updates on the Community-defined lists feature; and more.
• The latest Chart Project newsletter is available. It includes updates on the progress towards bringing better visibility into global charts usage and support for categorizing pages in the Data namespace on Commons.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 00:12, 11 февраль 2025 (UTC)

Википедиялар макалаларындагы “Логотип” сөзү маселеси.

Саламатсызбы! Мен темага тиешелүү макалаларды жазып жатып, “логотип” сөзүн колдонгонмун. Кийин кимдир бирөө “логотип” сөзүн “эн белги” деп өзгөртүрдү. Буга мен булак таба албадым. Бирок ошол убакта Кыргыз Википедиясы барагында “Эн белги” деп жазылып турганын көрдүм. Кыргыз Википедиясынын Телеграм тайпасына ушул маселе боюнча жазып сурадым, “логотип” сөзү “эн белги” деп аталышын алар жазышты. Соңунда бардык жазган макалалардагы “логотип” сөзүн “эн белги” деп өзгөртүрүп чыктым. Эми сиз болсо кайра “логотип” деп атап жатыптырсыз. Эртең бирөө келип “эмблема” деп өзгөртүрүп койсо таң калбайм. Baydastann 23:11, 11 февраль 2025 (UTC)

@Baydastann Википедия сурамжылоо боюнча жазылбайт. Википедияны ар ким түзөтө берет, кимдир бирөө бирдеме десе эле аныкы туура боло бербейт. Макалаларды жазганда да, кайра атаганда да булактарга гана таянуу керек!

Логотип менен эн белгинин (эмблеманын; башка мааниде да колдонулат, мисалы :"ички өндүрүштө жасалган, ошондой эле сатуу үчүн сырттан алынып келинген баалуу металлдардын эритиндилеринен жасалган зергердик жана башка буюмдарды мамлекеттик эн белги менен эн тамгалоону, анализдөөнү жана пробалоону жүргүзөт") деген түшүнүктөрдүн айырмасы бар. "Мейдин Кыргызстан” деген эн белги чапталып..." – мына дагы бир мисал. Ошондуктан, биринчиден сөздүн маанисин түшүнүп, түзөтүү керек.

Кыргыз Википедиясынын талкуу барагында кеңири маалымат бердим. Bosogo (баарлашуу) 23:52, 11 февраль 2025 (UTC)

Википедиялар макалаларындагы тышкы шилтемелер

@Bosogo Сиз айткандай баарын “логотип” деп өзгөртүрүп чыктым. Бул маселе түшүнүктүү. Мен башка маселе боюнча. Кыргыз Википедиясы барагы түшүнүктүү. Бирок башка википедияларга байланыштуу макалаларда калыптын ичинде башкы баракка шилтеме бар деп, макаланын шилтемелер бөлүмүндөгү башкы баракка шилтемени өчүрбөй эле койгон жакшы деп ойлойм. Себеби мен башка википедияларды да карап чыктым. Алар дагы шилтемелер бөлүмүндө башкы баракка шилтеме беришкен, түркчө айтканда zaten калыптын ичинде шилтеме бар болсо да. Жадакалса Англис Википедиясы дагы берген. Baydastann 13:49, 12 февраль 2025 (UTC)

Анда кала берсин. Bosogo (баарлашуу) 12:27, 13 февраль 2025 (UTC)

Tech News: 2025-08

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• Communities using growth tools can now showcase one event on the Атайын:Homepage for newcomers. This feature will help newcomers to be informed about editing activities they can participate in. Administrators can create a new event to showcase at Атайын:CommunityConfiguration. To learn more about this feature, please read the Diff post, have a look at the documentation, or contact the Growth team.

Updates for editors

Highlighted talk pages improvements

• Starting next week, talk pages at these wikis – Spanish Wikipedia, French Wikipedia, Italian Wikipedia, Japanese Wikipedia – will get a new design. This change was extensively tested as a Beta feature and is the last step of talk pages improvements. [49]
• You can now navigate to view a redirect page directly from its action pages, such as the history page. Previously, you were forced to first go to the redirect target. This change should help editors who work with redirects a lot. Thanks to user stjn for this improvement. [50]
• When a Cite reference is reused many times, wikis currently show either numbers like "1.23" or localized alphabetic markers like "a b c" in the reference list. Previously, if there were so many reuses that the alphabetic markers were all used, an error message was displayed. As part of the work to modernize Cite customization, these errors will no longer be shown and instead the backlinks will fall back to showing numeric markers like "1.23" once the alphabetic markers are all used.
• The log entries for each change to an editor's user-groups are now clearer by specifying exactly what has changed, instead of the plain before and after listings. Translators can help to update the localized versions. Thanks to user Msz2001 for these improvements.
• A new filter has been added to the Атайын:Nuke tool, which allows administrators to mass delete pages, to enable users to filter for pages in a range of page sizes (in bytes). This allows, for example, deleting pages only of a certain size or below. [51]
• Non-administrators can now check which pages are able to be deleted using the Атайын:Nuke tool. Thanks to user MolecularPilot for this and the previous improvements. [52]
• View all 25 community-submitted tasks that were resolved last week. For example, a bug was fixed in the configuration for the AV1 video file format, which enables these files to play again. [53]

Updates for technical contributors

• Parsoid Read Views is going to be rolling out to most Wiktionaries over the next few weeks, following the successful transition of Wikivoyage to Parsoid Read Views last year. For more information, see the Parsoid/Parser Unification project page. [54][55]
• Developers of tools that run on-wiki should note that mw.Uri is deprecated. Tools requiring mw.Uri must explicitly declare mediawiki.Uri as a ResourceLoader dependency, and should migrate to the browser native URL API soon. [56]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 21:17, 17 февраль 2025 (UTC)

Tech News: 2025-09

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• Administrators can now customize how the Babel feature creates categories using Атайын:CommunityConfiguration/Babel. They can rename language categories, choose whether they should be auto-created, and adjust other settings. [57]
• The wikimedia.org portal has been updated – and is receiving some ongoing improvements – to modernize and improve the accessibility of our portal pages. It now has better support for mobile layouts, updated wording and links, and better language support. Additionally, all of the Wikimedia project portals, such as wikibooks.org, now support dark mode when a reader is using that system setting. [58][59][60]
• One new wiki has been created: a Wiktionary in Santali (wikt:sat:) [61]
• View all 30 community-submitted tasks that were resolved last week. For example, a bug was fixed that prevented clicking on search results in the web-interface for some Firefox for Android phone configurations. [62]

Meetings and events

• The next Language Community Meeting is happening soon, February 28th at 14:00 UTC. This week's meeting will cover: highlights and technical updates on keyboard and tools for the Sámi languages, Translatewiki.net contributions from the Bahasa Lampung community in Indonesia, and technical Q&A. If you'd like to join, simply sign up on the wiki page.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 00:41, 25 февраль 2025 (UTC)

Tech News: 2025-10

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• All logged-in editors using the mobile view can now edit a full page. The "Edit full page" link is accessible from the "Көбүрөөк" menu in the toolbar. This was previously only available to editors using the Advanced mobile contributions setting. [63]
• Interface administrators can now help to remove the deprecated Cite CSS code matching "mw-ref" from their local MediaWiki:Common.css. The list of wikis in need of cleanup, and the code to remove, can be found with this global search and in this example, and you can learn more about how to help on the CSS migration project page. The Cite footnote markers ("[1]") are now rendered by Parsoid, and the deprecated CSS is no longer needed. The CSS for backlinks ("mw:referencedBy") should remain in place for now. This cleanup is expected to cause no visible changes for readers. Please help to remove this code before March 20, after which the development team will do it for you.
• When editors embed a file (e.g. [[File:MediaWiki.png]]) on a page that is protected with cascading protection, the software will no longer restrict edits to the file description page, only to new file uploads.[64] In contrast, transcluding a file description page (e.g. {{:File:MediaWiki.png}}) will now restrict edits to the page.[65]
• When editors revert a file to an earlier version it will now require the same permissions as ordinarily uploading a new version of the file. The software now checks for 'reupload' or 'reupload-own' rights,[66] and respects cascading protection.[67]
• When administrators are listing pages for deletion with the Nuke tool, they can now also list associated talk pages and redirects for deletion, alongside pages created by the target, rather than needing to manually delete these pages afterwards. [68]
• The previously noted update to Single User Login, which will accommodate browser restrictions on cross-domain cookies by moving login and account creation to a central domain, will now roll out to all users during March and April. The team plans to enable it for all new account creation on Group0 wikis this week. See the SUL3 project page for more details and an updated timeline.
• Since last week there has been a bug that shows some interface icons as black squares until the page has fully loaded. It will be fixed this week. [69]
• One new wiki has been created: a Wikipedia in Sylheti (w:syl:) [70]
• View all 23 community-submitted tasks that were resolved last week. For example, a bug was fixed with loading images in very old versions of the Firefox browser on mobile. [71]

Updates for technical contributors

• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 02:31, 4 март 2025 (UTC)

Tech News: 2025-11

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• Editors who use password managers at multiple wikis may notice changes in the future. The way that our wikis provide information to password managers about reusing passwords across domains has recently been updated, so some password managers might now offer you login credentials that you saved for a different Wikimedia site. Some password managers already did this, and are now doing it for more Wikimedia domains. This is part of the SUL3 project which aims to improve how our unified login works, and to keep it compatible with ongoing changes to the web-browsers we use. [72][73]
• The Wikipedia Apps Team is inviting interested users to help improve Wikipedia’s offline and limited internet use. After discussions in Afrika Baraza and the last ESEAP call, key challenges like search, editing, and offline access are being explored, with upcoming focus groups to dive deeper into these topics. All languages are welcome, and interpretation will be available. Want to share your thoughts? Join the discussion or email aramadan@wikimedia.org!
• All wikis will be read-only for a few minutes on March 19. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks.
• View all 27 community-submitted tasks that were resolved last week.

Updates for technical contributors

• Detailed code updates later this week: MediaWiki

In depth

• The latest quarterly Growth newsletter is available. It includes: the launch of the Community Updates module, the most recent changes in Community Configuration, and the upcoming test of in-article suggestions for first-time editors.
• An old API that was previously used in the Android Wikipedia app is being removed at the end of March. There are no current software uses, but users of the app with a version that is older than 6 months by the time of removal (2025-03-31), will no longer have access to the Suggested Edits feature, until they update their app. You can read more details about this change.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 23:09, 10 март 2025 (UTC)

Tech News: 2025-12

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• Twice a year, around the equinoxes, the Wikimedia Foundation's Site Reliability Engineering (SRE) team performs a datacenter server switchover, redirecting all traffic from one primary server to its backup. This provides reliability in case of a crisis, as we can always fall back on the other datacenter. Thanks to the Listen to Wikipedia tool, you can hear the switchover take place: Before it begins, you'll hear the steady stream of edits; Then, as the system enters a brief read-only phase, the sound stops for a couple of minutes, before resuming after the switchover. You can read more about the background and details of this process on the Diff blog. If you want to keep an ear out for the next server switchover, listen to the wikis on March 19 at 14:00 UTC.

Updates for editors

• The improved Content Translation tool dashboard is now available in 10 Wikipedias and will be available for all Wikipedias soon. With the unified dashboard, desktop users can now: Translate new sections of an article; Discover and access topic-based article suggestion filters (initially available only for mobile device users); Discover and access the Community-defined lists filter, also known as "Collections", from wiki-projects and campaigns.
• On Wikimedia Commons, a new system to select the appropriate file categories has been introduced: if a category has one or more subcategories, users will be able to click on an arrow that will open the subcategories directly within the form, and choose the correct one. The parent category name will always be shown on top, and it will always be possible to come back to it. This should decrease the amount of work for volunteers in fixing/creating new categories. The change is also available on mobile. These changes are part of planned improvements to the UploadWizard.
• The Community Tech team is seeking wikis to join a pilot for the Multiblocks feature and a refreshed Special:Block page in late March. Multiblocks enables administrators to impose multiple different types of blocks on the same user at the same time. If you are an admin or steward and would like us to discuss joining the pilot with your community, please leave a message on the project talk page.
• Starting March 25, the Editing team will test a new feature for Edit Check at 12 Wikipedias: Multi-Check. Half of the newcomers on these wikis will see all Reference Checks during their edit session, while the other half will continue seeing only one. The goal of this test is to see if users are confused or discouraged when shown multiple Reference Checks (when relevant) within a single editing session. At these wikis, the tags used on edits that show References Check will be simplified, as multiple tags could be shown within a single edit. Changes to the tags are documented on Phabricator. [74]
• The Global reminder bot, which is a service for notifying users that their temporary user-rights are about to expire, now supports using the localized name of the user-rights group in the message heading. Translators can see the listing of existing translations and documentation to check if their language needs updating or creation.
• The GlobalPreferences gender setting, which is used for how the software should refer to you in interface messages, now works as expected by overriding the local defaults. [75]
• View all 26 community-submitted tasks that were resolved last week. For example, the Wikipedia App for Android had a bug fixed for when a user is browsing and searching in multiple languages. [76]

Updates for technical contributors

• Later this week, the way that Codex styles are loaded will be changing. There is a small risk that this may result in unstyled interface message boxes on certain pages. User generated content (e.g. templates) is not impacted. Gadgets may be impacted. If you see any issues please report them. See the linked task for details, screenshots, and documentation on how to fix any affected gadgets.
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 23:48, 17 март 2025 (UTC)

Tech News: 2025-13

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• The Wikimedia Foundation is seeking your feedback on the drafts of the objectives and key results that will shape the Foundation's Product and Technology priorities for the next fiscal year (starting in July). The objectives are broad high-level areas, and the key-results are measurable ways to track the success of their objectives. Please share your feedback on the talkpage, in any language, ideally before the end of April.

Updates for editors

• The CampaignEvents extension will be released to multiple wikis (see deployment plan for details) in April 2025, and the team has begun the process of engaging communities on the identified wikis. The extension provides tools to organize, manage, and promote collaborative activities (like events, edit-a-thons, and WikiProjects) on the wikis. The extension has three tools: Event Registration, Collaboration List, and Invitation Lists. It is currently on 13 Wikipedias, including English Wikipedia, French Wikipedia, and Spanish Wikipedia, as well as Wikidata. Questions or requests can be directed to the extension talk page or in Phabricator (with #campaigns-product-team tag).
• Starting the week of March 31st, wikis will be able to set which user groups can view private registrants in Event Registration, as part of the CampaignEvents extension. By default, event organizers and the local wiki admins will be able to see private registrants. This is a change from the current behavior, in which only event organizers can see private registrants. Wikis can change the default setup by requesting a configuration change in Phabricator (and adding the #campaigns-product-team tag). Participants of past events can cancel their registration at any time.
• Administrators at wikis that have a customized MediaWiki:Sidebar should check that it contains an entry for the Атайын барактар listing. If it does not, they should add it using * specialpages-url|specialpages. Wikis with a default sidebar will see the link moved from the page toolbox into the sidebar menu in April. [77]
• The Minerva skin (mobile web) combines both Notice and Alert notifications within the bell icon (). There was a long-standing bug where an indication for new notifications was only shown if you had unseen Alerts. This bug is now fixed. In the future, Minerva users will notice a counter atop the bell icon when you have 1 or more unseen Notices and/or Alerts. [78]
• View all 23 community-submitted tasks that were resolved last week.

Updates for technical contributors

• VisualEditor has introduced a new client-side hook for developers to use when integrating with the VisualEditor target lifecycle. This hook should replace the existing lifecycle-related hooks, and be more consistent between different platforms. In addition, the new hook will apply to uses of VisualEditor outside of just full article editing, allowing gadgets to interact with the editor in DiscussionTools as well. The Editing Team intends to deprecate and eventually remove the old lifecycle hooks, so any use cases that this new hook does not cover would be of interest to them and can be shared in the task.
• Developers who use the mw.Api JavaScript library, can now identify the tool using it with the userAgent parameter: var api = new mw.Api( { userAgent: 'GadgetNameHere/1.0.1' } );. If you maintain a gadget or user script, please set a user agent, because it helps with library and server maintenance and with differentiating between legitimate and illegitimate traffic. [79][80]
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 22:43, 24 март 2025 (UTC)

Tech News: 2025-14

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• The Editing team is working on a new Edit check: Peacock check. This check's goal is to identify non-neutral terms while a user is editing a wikipage, so that they can be informed that their edit should perhaps be changed before they publish it. This project is at the early stages, and the team is looking for communities' input: in this Phabricator task, they are gathering on-wiki policies, templates used to tag non-neutral articles, and the terms (jargon and keywords) used in edit summaries for the languages they are currently researching. You can participate by editing the table on Phabricator, commenting on the task, or directly messaging Trizek (WMF).
• Single User Login has now been updated on all wikis to move login and account creation to a central domain. This makes user login compatible with browser restrictions on cross-domain cookies, which have prevented users of some browsers from staying logged in.
• View all 35 community-submitted tasks that were resolved last week.

Updates for technical contributors

• Starting on March 31st, the MediaWiki Interfaces team will begin a limited release of generated OpenAPI specs and a SwaggerUI-based sandbox experience for MediaWiki REST APIs. They invite developers from a limited group of non-English Wikipedia communities (Arabic, German, French, Hebrew, Interlingua, Dutch, Chinese) to review the documentation and experiment with the sandbox in their preferred language. In addition to these specific Wikipedia projects, the sandbox and OpenAPI spec will be available on the on the test wiki REST Sandbox special page for developers with English as their preferred language. During the preview period, the MediaWiki Interfaces Team also invites developers to share feedback about your experience. The preview will last for approximately 2 weeks, after which the sandbox and OpenAPI specs will be made available across all wiki projects.
• Detailed code updates later this week: MediaWiki

In depth

• Sometimes a small, one line code change can have great significance: in this case, it means that for the first time in years we're able to run all of the stack serving maps.wikimedia.org - a host dedicated to serving our wikis and their multi-lingual maps needs - from a single core datacenter, something we test every time we perform a datacenter switchover. This is important because it means that in case one of our datacenters is affected by a catastrophe, we'll still be able to serve the site. This change is the result of extensive work by two developers on porting the last component of the maps stack over to kubernetes, where we can allocate resources more efficiently than before, thus we're able to withstand more traffic in a single datacenter. This work involved a lot of complicated steps because this software, and the software libraries it uses, required many long overdue upgrades. This type of work makes the Wikimedia infrastructure more sustainable.

Meetings and events

• MediaWiki Users and Developers Workshop Spring 2025 is happening in Sandusky, USA, and online, from 14–16 May 2025. The workshop will feature discussions around the usage of MediaWiki software by and within companies in different industries and will inspire and onboard new users. Registration and presentation signup is now available at the workshop's website.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 00:05, 1 апрель 2025 (UTC)

Tech News: 2025-15

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• From now on, interface admins and centralnotice admins are technically required to enable two-factor authentication before they can use their privileges. In the future this might be expanded to more groups with advanced user-rights. [81]
• View all 20 community-submitted tasks that were resolved last week.

Updates for technical contributors

• The Design System Team is preparing to release the next major version of Codex (v2.0.0) on April 29. Editors and developers who use CSS from Codex should see the 2.0 overview documentation, which includes guidance related to a few of the breaking changes such as font-size, line-height, and size-icon.
• The results of the Developer Satisfaction Survey (2025)  are now available. Thank you to all participants. These results help the Foundation decide what to work on next and to review what they recently worked on.
• Detailed code updates later this week: MediaWiki

Meetings and events

• The 2025 Wikimedia Hackathon will take place in Istanbul, Turkey, between 2–4 May. Registration for attending the in-person event will close on 13 April. Before registering, please note the potential need for a visa or e-visa to enter the country.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 18:53, 7 апрель 2025 (UTC)

Tech News: 2025-16

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• Later this week, the default thumbnail size will be increased from 220px to 250px. This changes how pages are shown in all wikis and has been requested by some communities for many years, but wasn't previously possible due to technical limitations. [82]
• File thumbnails are now stored in discrete sizes. If a page specifies a thumbnail size that's not among the standard sizes (20, 40, 60, 120, 250, 330, 500, 960), then MediaWiki will pick the closest larger thumbnail size but will tell the browser to downscale it to the requested size. In these cases, nothing will change visually but users might load slightly larger images. If it doesn't matter which thumbnail size is used in a page, please pick one of the standard sizes to avoid the extra in-browser down-scaling step. [83][84]

Updates for editors

• The Wikimedia Foundation are working on a system called Edge Uniques which will enable A/B testing, help protect against Distributed denial-of-service attacks (DDoS attacks), and make it easier to understand how many visitors the Wikimedia sites have. This is so that they can more efficiently build tools which help readers, and make it easier for readers to find what they are looking for.
• To improve security for users, a small percentage of logins will now require that the account owner input a one-time password emailed to their account. It is recommended that you check that the email address on your account is set correctly, and that it has been confirmed, and that you have an email set for this purpose. [85]
• "Are you interested in taking a short survey to improve tools used for reviewing or reverting edits on your Wiki?" This question will be asked at 7 wikis starting next week, on Recent Changes and Watchlist pages. The Moderator Tools team wants to know more about activities that involve looking at new edits made to your Wikimedia project, and determining whether they adhere to your project's policies.
• On April 15, the full Wikidata graph will no longer be supported on query.wikidata.org. After this date, scholarly articles will be available through query-scholarly.wikidata.org, while the rest of the data hosted on Wikidata will be available through the query.wikidata.org endpoint. This is part of the scheduled split of the Wikidata Graph, which was announced in September 2024. More information is available on Wikidata.
• The latest quarterly Wikimedia Apps Newsletter is now available. It covers updates, experiments, and improvements made to the Wikipedia mobile apps.
• View all 30 community-submitted tasks that were resolved last week.

Updates for technical contributors

• The latest quarterly Technical Community Newsletter is now available. This edition includes: an invitation for tool maintainers to attend the Toolforge UI Community Feedback Session on April 15th; recent community metrics; and recent technical blog posts.
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 00:25, 15 апрель 2025 (UTC)

Tech News: 2025-17

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• Wikifunctions is now integrated with Dagbani Wikipedia since April 15. It is the first project that will be able to call functions from Wikifunctions and integrate them in articles. A function is something that takes one or more inputs and transforms them into a desired output, such as adding up two numbers, converting miles into metres, calculating how much time has passed since an event, or declining a word into a case. Wikifunctions will allow users to do that through a simple call of a stable and global function, rather than via a local template. [86]
• A new type of lint error has been created: Empty headings (documentation). The Linter extension's purpose is to identify wikitext patterns that must or can be fixed in pages and provide some guidance about what the problems are with those patterns and how to fix them. [87]
• View all 37 community-submitted tasks that were resolved last week.

Updates for technical contributors

• Following its publication on HuggingFace, the "Structured Contents" dataset, developed by Wikimedia Enterprise, is now also available on Kaggle. This Beta initiative is focused on making Wikimedia data more machine-readable for high-volume reusers. They are releasing this beta version in a location that open dataset communities already use, in order to seek feedback, to help improve the product for a future wider release. You can read more about the overall Structured Contents project, and about the first release that's freely usable.
• There is no new MediaWiki version this week.

Meetings and events

• The Editing and Machine Learning Teams invite interested volunteers to a video meeting to discuss Peacock check, which is the latest Edit check that will detect "peacock" or "overly-promotional" or "non-neutral" language whilst an editor is typing. Editors who work with newcomers, or help to fix this kind of writing, or are interested in how we use artificial intelligence in our projects are encouraged to attend. The meeting will be on April 28, 2025 at 18:00–19:00 UTC and hosted on Zoom.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 21:00, 21 апрель 2025 (UTC)

Tech News: 2025-18

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• Event organizers who host collaborative activities on multiple wikis, including Bengali, Japanese, and Korean Wikipedias, will have access to the CampaignEvents extension this week. Also, admins in the Wikipedia where the extension is enabled will automatically be granted the event organizer right soon. They won't have to manually grant themselves the right before they can manage events as requested by a community.
• View all 19 community-submitted tasks that were resolved last week.

Updates for technical contributors

• The release of the next major version of Codex, the design system for Wikimedia, is scheduled for 29 April 2025. Technical editors will have access to the release by the week of 5 May 2025. This update will include a number of breaking changes and minor visual changes. Instructions on handling the breaking and visual changes are documented on this page. Pre-release testing is reported in T386298, with post-release issues tracked in T392379 and T392390.
• Users of Wiki Replicas will notice that the database views of ipblocks, ipblocks_ipindex, and ipblocks_compat are now deprecated. Users can query the block and block_target new views that mirror the new tables in the production database instead. The deprecated views will be removed entirely from Wiki Replicas in June, 2025.
• Detailed code updates later this week: MediaWiki

In depth

• The latest quarterly Language and Internationalization Newsletter is now available. This edition includes an overview of the improved Content Translation Dashboard Tool, support for new languages, highlights from the Wiki Loves Ramadan campaign, results from the Language Onboarding Experiment, an analysis of topic diversity in articles, and information on upcoming community meetings and events.

Meetings and events

• The Let's Connect Learning Clinic will take place on April 29 at 14:30 UTC. This edition will focus on "Understanding and Navigating Conflict in Wikimedia Projects". You can register now to attend.
• The 2025 Wikimedia Hackathon, which brings the global technical community together to connect, brainstorm, and hack existing projects, will take place from May 2 to 4th, 2025, at Istanbul, Turkey.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 19:32, 28 апрель 2025 (UTC)

Tech News: 2025-19

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• The Wikimedia Foundation has shared the latest draft update to their annual plan for next year (July 2025–June 2026). This includes an executive summary (also on Diff), details about the three main goals (Infrastructure, Volunteer Support, and Effectiveness), global trends, and the budget and financial model. Feedback and questions are welcome on the talk page until the end of May.

Updates for editors

• For wikis that have the CampaignEvents extension enabled, two new feature improvements have been released:
  • Admins can now choose which namespaces are permitted for Event Registration via Community Configuration (documentation). The default setup is for event registration to be permitted in the Event namespace, but other namespaces (such as the project namespace or WikiProject namespace) can now be added. With this change, communities like WikiProjects can now more easily use Event Registration for their collaborative activities.
  • Editors can now transclude the Collaboration List on a wiki page (documentation). The Collaboration List is an automated list of events and WikiProjects on the wikis, accessed via Атайын:AllEvents (example). Now, the Collaboration List can be added to all sorts of wiki pages, such as: a wiki mainpage, a WikiProject page, an affiliate page, an event page, or even a user page.
• View all 27 community-submitted tasks that were resolved last week.

Updates for technical contributors

• Developers who use the moment library in gadgets and user scripts should revise their code to use alternatives like the Intl library or the new mediawiki.DateFormatter library. The moment library has been deprecated and will begin to log messages in the developer console. You can see a global search for current uses, and ask related questions in this Phabricator task.
• Developers who maintain a tool that queries the Wikidata term store tables (wbt_*) need to update their code to connect to a separate database cluster. These tables are being split into a separate database cluster. Tools that query those tables via the wiki replicas must be adapted to connect to the new cluster instead. Documentation and related links are available. [88]
• Detailed code updates later this week: MediaWiki

In depth

• The latest Chart Project newsletter is available. It includes updates on preparing to expand the deployment to additional wikis as soon as this week (starting May 6) and scaling up over the following weeks, plus exploring filtering and transforming source data.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 00:15, 6 май 2025 (UTC)

Tech News: 2025-20

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• The "Get shortened URL" link on the sidebar now includes a QR code. Wikimedia site users can now use it by scanning or downloading it to quickly share and access shared content from Wikimedia sites, conveniently.

Updates for editors

• The Wikimedia Foundation is working on a system called Edge Uniques, which will enable A/B testing, help protect against distributed denial-of-service attacks (DDoS attacks), and make it easier to understand how many visitors the Wikimedia sites have. This is to help more efficiently build tools which help readers, and make it easier for readers to find what they are looking for. Tech News has previously written about this. The deployment will be gradual. Some might see the Edge Uniques cookie the week of 19 May. You can discuss this on the talk page.
• Starting May 19, 2025, Event organisers in wikis with the CampaignEvents extension enabled can use Event Registration in the project namespace (e.g., Wikipedia namespace, Wikidata namespace). With this change, communities don't need admins to use the feature. However, wikis that don't want this change can remove and add the permitted namespaces at Special:CommunityConfiguration/CampaignEvents.
• The Wikipedia project now has a Wikipedia in Nupe (w:nup:). This is a language primarily spoken in the North Central region of Nigeria. Speakers of this language are invited to contribute to new Wikipedia.
• View all 27 community-submitted tasks that were resolved last week.

Updates for technical contributors

• Developers can now access pre-parsed Dutch Wikipedia, amongst others (English, German, French, Spanish, Italian, and Portuguese) through the Structured Contents snapshots (beta). The content includes parsed Wikipedia abstracts, descriptions, main images, infoboxes, article sections, and references.
• The /page/data-parsoid REST API endpoint is no longer in use and will be deprecated. It is scheduled to be turned off on June 7, 2025.
• Detailed code updates later this week: MediaWiki

In depth

• The IPv6 support is a newly introduced Cloud virtual network that significantly boosts Wikimedia platforms' scalability, security, and readiness for the future. If you are a technical contributor eager to learn more, check out this blog post for an in-depth look at the journey to IPv6.

Meetings and events

• The 2nd edition of 2025 of Afrika Baraza, a virtual platform for African Wikimedians to connect, will take place on May 15 at 17:00 UTC. This edition will focus on discussions regarding Wikimedia Annual planning and progress.
• The MENA Connect Community Call, a virtual meeting for MENA Wikimedians to connect, will take place on May 17 at 17:00 UTC. You can register now to attend.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 22:38, 12 май 2025 (UTC)

Tech News: 2025-21

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• The Editing Team and the Machine Learning Team are working on a new check for newcomers: Peacock check. Using a prediction model, this check will encourage editors to improve the tone of their edits, using artificial intelligence. We invite volunteers to review the first version of the Peacock language model for the following languages: Arabic, Spanish, Portuguese, English, and Japanese. Users from these wikis interested in reviewing this model are invited to sign up at MediaWiki.org. The deadline to sign up is on May 23, which will be the start date of the test.

Updates for editors

• From May 20, 2025, oversighters and checkusers will need to have their accounts secured with two-factor authentication (2FA) to be able to use their advanced rights. All users who belong to these two groups and do not have 2FA enabled have been informed. In the future, this requirement may be extended to other users with advanced rights. Learn more.
• Multiblocks will begin mass deployment by the end of the month: all non-Wikipedia projects plus Catalan Wikipedia will adopt Multiblocks in the week of May 26, while all other Wikipedias will adopt it in the week of June 2. Please contact the team if you have concerns. Administrators can test the new user interface now on your own wiki by browsing to Атайын:Block?usecodex=1, and can test the full multiblocks functionality on testwiki. Multiblocks is the feature that makes it possible for administrators to impose different types of blocks on the same user at the same time. See the help page for more information. [89]
• Later this week, the Атайын:SpecialPages listing of almost all special pages will be updated with a new design. This page has been redesigned to improve the user experience in a few ways, including: The ability to search for names and aliases of the special pages, sorting, more visible marking of restricted special pages, and a more mobile-friendly look. The new version can be previewed at Beta Cluster now, and feedback shared in the task. [90]
• The Chart extension is being enabled on more wikis. For a detailed list of when the extension will be enabled on your wiki, please read the deployment timeline.
• Wikifunctions will be deployed on May 27 on five Wiktionaries: Hausa, Igbo, Bengali, Malayalam, and Dhivehi/Maldivian. This is the second batch of deployment planned for the project. After deployment, the projects will be able to call functions from Wikifunctions and integrate them in their pages. A function is something that takes one or more inputs and transforms them into a desired output, such as adding up two numbers, converting miles into metres, calculating how much time has passed since an event, or declining a word into a case. Wikifunctions will allow users to do that through a simple call of a stable and global function, rather than via a local template.
• Later this week, the Wikimedia Foundation will publish a hub for experiments. This is to showcase and get user feedback on product experiments. The experiments help the Wikimedia movement understand new users, how they interact with the internet and how it could affect the Wikimedia movement. Some examples are generated video, the Wikipedia Roblox speedrun game and the Discord bot.
• View all 29 community-submitted tasks that were resolved last week. For example, there was a bug with creating an account using the API, which has now been fixed. [91]

Updates for technical contributors

• Gadgets and user scripts that interact with Атайын:Block may need to be updated to work with the new manage blocks interface. Please review the developer guide for more information. If you need help or are unable to adapt your script to the new interface, please let the team know on the talk page. [92]
• The mw.title object allows you to get information about a specific wiki page in the Lua programming language. Starting this week, a new property will be added to the object, named isDisambiguationPage. This property allows you to check if a page is a disambiguation page, without the need to write a custom function. [93]
• User script developers can use a new reverse proxy tool to load javascript and css from gitlab.wikimedia.org with mw.loader.load. The tool's author hopes this will enable collaborative development workflows for user scripts including linting, unit tests, code generation, and code review on gitlab.wikimedia.org without a separate copy-and-paste step to publish scripts to a Wikimedia wiki for integration and acceptance testing. See Tool:Gitlab-content on Wikitech for more information.
• Detailed code updates later this week: MediaWiki

Meetings and events

• The 12th edition of Wiki Workshop 2025, a forum that brings together researchers that explore all aspects of Wikimedia projects, will be held virtually on 21-22 May. Researchers can register now.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 23:13, 19 май 2025 (UTC)

Tech News: 2025-22

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• A community-wide discussion about a very delicate issue for the development of Abstract Wikipedia is now open on Meta: where to store the abstract content that will be developed through functions from Wikifunctions and data from Wikidata. The discussion is open until June 12 at Abstract Wikipedia/Location of Abstract Content, and every opinion is welcomed. The decision will be made and communicated after the consultation period by the Foundation.

Updates for editors

• Since last week, on all wikis except the largest 20, people using the mobile visual editor will have additional tools in the menu bar, accessed using the new + toolbar button. To start, the new menu will include options to add: citations, hieroglyphs, and code blocks. Deployment to the remaining wikis is scheduled to happen in June.
• The #ifexist parser function will no longer register a link to its target page. This will improve the usefulness of Атайын:WantedPages, which will eventually only list pages that are the target of an actual red link. This change will happen gradually as the source pages are updated. [94]
• This week, the Moderator Tools team will launch a new filter to Recent Changes, starting at Indonesian Wikipedia. This new filter highlights edits that are likely to be reverted. The goal is to help Recent Changes patrollers identify potentially problematic edits. Other wikis will benefit from this filter in the future.
• Upon clicking an empty search bar, logged-out users will see suggestions of articles for further reading. The feature will be available on both desktop and mobile. Readers of Catalan, Hebrew, and Italian Wikipedias and some sister projects will receive the change between May 21 and mid-June. Readers of other wikis will receive the change later. The goal is to encourage users to read the wikis more. Learn more.
• Some users of the Wikipedia Android app can use a new feature for readers, WikiGames, a daily trivia game based on real historical events. The release has started as an A/B test, available to 50% of users in the following languages: English, French, Portuguese, Russian, Spanish, Arabic, Chinese, and Turkish.
• The Newsletter extension that is available on MediaWiki.org allows the creation of various newsletters for global users. The extension can now publish new issues as section links on an existing page, instead of requiring a new page for each issue. [95]
• View all 32 community-submitted tasks that were resolved last week.

Updates for technical contributors

• The previously deprecated ipblocks views in Wiki Replicas will be removed in the beginning of June. Users are encouraged to query the new block and block_target views instead.
• Detailed code updates later this week: MediaWiki

Meetings and events

• Wikidata and Sister Projects is a multi-day online event that will focus on how Wikidata is integrated to Wikipedia and the other Wikimedia projects. The event runs from May 29 – June 1. You can read the Program schedule and register.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 20:05, 26 май 2025 (UTC)

Tech News: 2025-23

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• The Chart extension is now available on all Wikimedia wikis. Editors can use this new extension to create interactive data visualizations like bar, line, area, and pie charts. Charts are designed to replace many of the uses of the legacy Graph extension.

Updates for editors

• It is now easier to configure automatic citations for your wiki within the visual editor's citation generator. Administrators can now set a default template by using the _default key in the local MediaWiki:Citoid-template-type-map.json page (example diff). Setting this default will also help to future-proof your existing configurations when new item types are added in the future. You can still set templates for individual item types as they will be preferred to the default template. [96]
• View all 20 community-submitted tasks that were resolved last week.

Updates for technical contributors

• Starting the week of June 2, bots logging in using action=login or action=clientlogin will fail more often. This is because of stronger protections against suspicious logins. Bots using bot passwords or using a loginless authentication method such as OAuth are not affected. If your bot is not using one of those, you should update it; using action=login without a bot password was deprecated in 2016. For most bots, this only requires changing what password the bot uses. [97]
• From this week, Wikimedia wikis will allow ES2017 features in JavaScript code for official code, gadgets, and user scripts. The most visible feature of ES2017 is async/await syntax, allowing for easier-to-read code. Until this week, the platform only allowed up to ES2016, and a few months before that, up to ES2015. [98]
• Detailed code updates later this week: MediaWiki

Meetings and events

• Scholarship applications to participate in the GLAM Wiki Conference 2025 are now open. The conference will take place from 30 October to 1 November, in Lisbon, Portugal. GLAM contributors who lack the means to support their participation can apply here. Scholarship applications close on June 7th.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 23:55, 2 июнь 2025 (UTC)

Tech News: 2025-24

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• The Trust and Safety Product team is finalizing work needed to roll out temporary accounts on large Wikipedias later this month. The team has worked with stewards and other users with extended rights to predict and address many use cases that may arise on larger wikis, so that community members can continue to effectively moderate and patrol temporary accounts. This will be the second of three phases of deployment – the last one will take place in September at the earliest. For more information about the recent developments on the project, see this update. If you have any comments or questions, write on the talk page, and join a CEE Catch Up this Tuesday.

Updates for editors

• The watchlist expiry feature allows editors to watch pages for a limited period of time. After that period, the page is automatically removed from your watchlist. Starting this week, you can set a preference for the default period of time to watch pages. The preferences also allow you to set different default watch periods for editing existing pages, pages you create, and when using rollback. [99]

Example of a talk page with the new design, in French.

• The appearance of talk pages will change at almost all Wikipedias (some have already received this design change, a few will get these changes later). You can read details about the changes on Diff. It is possible to opt out of these changes in user preferences ("Show discussion activity"). [100][101]
• Users with specific extended rights (including administrators, bureaucrats, checkusers, oversighters, and stewards) can now have IP addresses of all temporary accounts revealed automatically during time-limited periods where they need to combat high-speed account-hopping vandalism. This feature was requested by stewards. [102]
• This week, the Moderator Tools and Machine Learning teams will continue the rollout of a new filter to Recent Changes, releasing it to several more Wikipedias. This filter utilizes the Revert Risk model, which was created by the Research team, to highlight edits that are likely to be reverted and help Recent Changes patrollers identify potentially problematic contributions. The feature will be rolled out to the following Wikipedias: Afrikaans Wikipedia, Belarusian Wikipedia, Bengali Wikipedia, Welsh Wikipedia, Hawaiian Wikipedia, Icelandic Wikipedia, Kazakh Wikipedia, Simple English Wikipedia, Turkish Wikipedia. The rollout will continue in the coming weeks to include the rest of the Wikipedias in this project. [103]
• View all 27 community-submitted tasks that were resolved last week.

Updates for technical contributors

• AbuseFilter editors active on Meta-Wiki and large Wikipedias are kindly asked to update AbuseFilter to make it compatible with temporary accounts. A link to the instructions and the private lists of filters needing verification are available on Phabricator.
• Lua modules now have access to the name of a page's associated thumbnail image, and on some wikis to the WikiProject assessment information. This is possible using two new properties on mw.title objects, named pageImage and pageAssessments. [104][105]
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 01:17, 10 июнь 2025 (UTC)