Durante la tua navigazione o la modifica delle nostre pagine hai incontrato un malfunzionamento o un errore del software di Wikipedia (vedi WP:Mercoledì)
Pensi che Wikipedia possa essere migliorata con qualche funzionalità tecnica che aiuti utenti e contributori
Non usare questa pagina se:
Hai domande generiche sull'uso di Wikipedia (ad esempio: "come inserisco un'immagine in una voce?", "cos'è template?", "come si crea un progetto?"): chiedi in Aiuto:Sportello informazioni;
Per comodità, puoi consultare qui sotto le ultime notizie tecniche:
Ultime notizie tecniche
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 Wikipedia Apps team is preparing to launch Year in Review in early December. Year in Review gives app users a personalized recap of how they read and engaged with Wikipedia throughout the year. The team is looking for volunteers to help make it available in as many languages as possible. Translators can contribute through translatewiki.net. For Android, search for yir under the "Untranslated" tab, and for iOS, search for year-in-review under the "Untranslated" tab.
Following the release of Reading Lists to all Wikipedias in September, logged-in users will soon be able to organize articles saved in their lists into customizable categories. This will enable readers to create collections and revisit saved articles based on their interests, potentially encouraging frequent visits to Wikipedia. The update will roll out to all Wikipedia users between November 9 and 16.
The Wikipedia Apps team is preparing to launch the first of two notification experiments for English Wikipedia readers on Android who have opted in to notifications. The three-week experiment will send notifications suggesting personalized Discover reading lists which are collections of Wikipedia articles recommended based on articles the reader has previously viewed. The goal is to understand whether these recommendations help readers discover relevant content and encourage them to return to the app. No action is required, and users can manage their notification preferences in the app settings. Learn more and share feedback.
A bug in the Global Watchlist was causing the page to fail to load for users who have unseen changes on Wikimedia Commons. The bug has now been fixed. If you temporarily removed commons.wikimedia.org from your personal Global Watchlist settings due to the bug, you can restore it there.
A new Beta feature called "Home" will be deployed to 10 Wikipedias for a limited test. This new feature aims to replace Special:Homepage for newcomers, with additional modules planned for the future to improve upon the current experience. If you want to participate in the test, please sign up. "Home" will be released to all users later this month.
On English and Russian Wikipedias, Source Verification is now available as an experimental Suggestion for experienced editors within Suggestion Mode. It uses an LLM hosted on LiftWing to try to check whether a cited source supports the claim it’s attached to. To try it out, please see these testing instructions. If you are at another language Wikipedia and your community is interested in trying it out, please express your interest.
View all 35 community-submitted tasks that were resolved last week. For example, an issue where dates passed as blank parameters to functions in wikitext were incorrectly interpreted using the month-day-year format instead of the day-month-year format, has now been fixed.
Updates for technical contributors
Starting on 1 December 2026, hCaptcha will be required for edits made via the API by non-autoconfirmed users. If your tool, gadget, or user script makes edits on behalf of newcomer users, see how to update it.
Toolforge has introduced two new beta features. "Toolforge alerts" send email notifications when a tool becomes unavailable, returns errors, or restarts frequently. "Extended logging" makes it easier to investigate problems by providing logs for events such as job creation, deletion, and deployment failures through the toolforge logs command. Both features are opt-in and help tool maintainers become aware of and resolve problems with their tools more quickly. Maintainers can enable alerts and learn how to access extended logs. They are also encouraged to try the features and provide feedback.
A proposal to change how we currently organize the Wikimedia Hackathon has been shared. It explores making the event more accessible to technical communities in different regions. Share your feedback on the proposal’s talk page; the deadline has been extended to November 13th.
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
Starting October 13, wikis can change the default pattern for auto-generated reference names in VisualEditor (currently <refname=":1"/>). They will be able to use human-readable, content-based reference names that are more helpful to contributors using the source editor (e.g. <refname="Miller2026-1"/>). VisualEditor reference name patterns can be defined using MediaWiki system messages, JSON, templates and modules (more information). Admins can enable these changes via community configuration. This is a community wish implemented by WMDE Technical Wishes.
Sub-referencing is a new MediaWiki feature that allows editors to reuse references with different details. It will be deployed to English Wikipedia on October 14 and to remaining Wikimedia Foundation wikis by end of October (likely October 21). The FAQ lists possible actions to take on your wiki to support the deployment. This is a long-standing community wish implemented by WMDE Technical Wishes.
Updates for editors
Moderator Tools will be removing the list view of the Watchlist and defaulting everyone to the changelog view. Previously, there were two versions of how the Watchlist is shown to mobile web users: the list view, where editors could see watched articles in a list format, and the changelog view, where editors could see changes to watched articles in a log format, controlled by a user's Advanced Mobile Control settings. This has created issues for code-base maintenance: two different displays means two sets of code to manage. By defaulting to the changelog view, we are simplifying the codebase and avoiding the likelihood of missing bugs.
The Wikipedia Android app is testing a way to listen to article introductions in the “For you” feed. A text-to-speech model reads the existing article text aloud without rewriting it or adding any content. The 30-day experiment will begin in the Wikipedia Beta app during the third week of September, then move to the regular Wikipedia Android app in October for a limited group of eligible users. A small portion of app users (those with English feeds and at least one topic interest) will have access to the feature. This experiment is part of broader efforts to give app readers options in how they consume content in order to deepen engagement and user retention. Learn more and share feedback.
CodeMirror syntax highlighting was enabled by default for all logged out and newly registered users on the English Wikipedia on September 14. With no signs of adverse effects, the same change is being proposed to be made globally across all wikis in a few weeks. If you have concerns or feedback, or if your wiki would like to opt out, please see the help page.
Last week, language link changes were removed from Recent Changes and Watchlist feeds on Wikivoyage, Wikisource, Wikiversity, Wikiquote and Wiktionary. As no adverse effects have been observed, the Wikidata For Wikimedia Projects plans to roll out this change globally to all Wikipedias. This is scheduled for October 13 at 07:00 UTC, after which editors will no longer see when a link to another language version of a page is added, removed, or changed in its Wikidata item. Editors who rely on these notifications can read more on the project page and share feedback or ask to opt out their wiki on the talk page.
View all 28 community-submitted tasks that were resolved last week. For example, an issue where accidentally touching the graph while scrolling on the Pageviews tool on mobile could unintentionally zoom in has now been fixed. Click-and-drag zoom is now disabled on touch devices.
Updates for technical contributors
There are three major changes coming to dumps: the legacy content dumps deprecated in January 2026 will now be sunset, the replacement MediaWiki Content File Exports will be delayed to implement a “safety buffer”, and they are now also available as 7zip-compressed files. Users will need to switch the URL they download their dump from. For more information, timeline and migration instructions, see Legacy content dumps sunset.
The Wikimedia Foundation discovered unauthorized activity by OpenAI agents on Wikimedia projects, including edits to wikis, attempts to exploit a public note-taking tool, and heavy automated traffic. Read the blog post on Diff for more details about the activity and the Foundation’s response.
Meetings and events
Save the date for the next Wikimedia Hackathon! We’ll be meeting in lovely Tirana, Albania for the 2027 Wikimedia Hackathon from April 9–11, 2027. Scholarship and staff sponsorship applications are currently being accepted through Pretix and will close on October 30, 2026. General registration will open in January 2027.
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
To measure the impact of incorporating some community-requested features on logged-out reader retention, a test for Image Carousel will be pushed to logged-out readers. With the Image Carousel feature, readers browse community-uploaded images, selected by editors as relevant to specific articles. The test starts on November 20.
An experimental notice will be pushed to 0.5% of logged-out mobile readers who come to English Wikipedia from Google, asking them to add Wikipedia as a Google Preferred Source. The test is to see if this notice increases reader retention and encourages people who use Google Search to visit Wikipedia more often. It will run from October 15–29 and will be assessed for its impact on retention and referrals.
View all 26 community-submitted tasks that were resolved last week. For example, an issue where Quarry returned an “Access denied” error when users tried to run SQL queries, preventing queries from running normally, has now been fixed.
Updates for technical contributors
Due to a long-standing bug, applications that use the OAuth 2 client credentials flow to act on their owners’ behalf are treated as if they are logged out. This will be fixed for new applications registered on or after Monday, October 19. Some affected applications need to re-register.
A proposal to hold the Wikimedia Hackathon every three years, with regional hackathons in between, has been shared. It explores making the event more accessible to technical communities in different regions. Share your feedback on the proposal’s talk page before November 6.
Aspettatevi molti/tutti i tool non funzionanti --Bozz (msg) 14:02, 21 ott 2026 (CEST)
@Valerio Bozzolan nei giorni scorsi infatti mi sono beccato un 500 Internal Server Error da una buildback di GitLab su Toolforge. Non so se è correlato a questo incidente. Per mia fortuna comunque non scrivo in PHP. 💪🏽—super nabla(🪰 msg) 14:05, 21 ott 2026 (CEST)
ne approfitto del thread per segnalare che nei giorni scorsi ci sono stati diversi attacchi alla supply chain (tra cui ovhclient e altri) e c'è il tema dei certificati HTTPS compromessi. invito tutti a controllare al link se il vostro browser/dispositivo/etc. sia aggiornato e in caso scaricare le ultime versioni dei certificati per l'ambiente/software/linguaggio che state utilizzando. --valepert 15:09, 21 ott 2026 (CEST)
Il mio bot su Toolforge è fermo e lo stesso accesso a Toolforge è impossibile, e suppongo la stessa sorte sia per tutti i bot (però @Valerio Bozzolan BotCancellazioni funziona ancora, hai un hosting di riserva?) --IndyJr (Tracce nella foresta) 16:22, 22 ott 2026 (CEST)
[@ IndyJr] in realtà è fermo anche il BotCancellazioni... L'elenco delle cancellazioni è stato aggiornato a mano--Parma1983 17:02, 22 ott 2026 (CEST)
Segnalo che Toolforge è stato riavviato, ma restano disabilitati tutti i tool e i bot in PHP, come i nostri BotCancellazioni e OrfanizzaBot. --Sakretsu (炸裂) 23:09, 22 ott 2026 (CEST)
Per il mio bot ho dovuto rifare i token OAuth. @Valerio Bozzolan Ho clonato il tuo bot sul mio PC e ho fatto un paio di aggiornamenti sulle pagine da cancellare, controlla se puoi farlo ripartire da toolforge, forse dovrai generare nuovi token. --IndyJr (Tracce nella foresta) 00:45, 23 ott 2026 (CEST)
Per quanto riguarda Utente:OrfanizzaBot e Utente:BotCancellazioni, token rigenerati, e fatto hardening spostandoli in tool separati, funziona, aggiornata documentazione Fattoooooooooooooooo voglio lanciarmi dalla finestra asd. Se avete tempo, segnate una spunta su cosa avete controllato: phabricator:T442455 --Bozz (msg) 22:12, 26 ott 2026 (CET)
Tech News: 2026-44
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
An experiment launched on September 29 is testing article recommendations for new account holders who also identify as readers. By suggesting articles to read, similar to recommendations in the Wikipedia app for logged-in readers, the experiment aims to encourage new account holders to read and return to the website regularly, with the goal of increasing internal referrals by 1%. See the related Community Wishlist proposal.
Several Wikimedia services were taken offline last week because of a security vulnerability in PHP. This is because they need to be updated before they are safe to put back online. This is not a problem just for the Wikimedia movement but affects a lot of websites. You can follow updates on Wikitech. Cloud VPS and Toolforge will take longer to bring back online. This is to make sure that applications which run on Cloud VPS or Toolforge are not affected. Tool developers can see updates and more information on the Cloud-announce mailing list.
Last week we shared that to measure the impact of incorporating some community-requested features on logged-out reader retention, a test for the Image Carousel feature would be pushed to logged-out readers. Due to an issue, we will be restarting the test, but it will be live on October 26, not November 20 as initially announced.
Updates for editors
A new bot detection system to better identify automated traffic that disguises itself as human visitors, is coming to the Wikimedia wikis. This might cause sudden changes to visitor statistics starting from 26 October, going back to 20 June 2026.
The Score extension which renders musical notation inside wiki pages, has been temporarily disabled on all wikis due to a security issue. Affected pages will display a notice instead of musical scores, but the underlying code remains intact. No action is needed from editors, and a fix is in progress. A separate announcement will follow when the extension is re-enabled. Read more on Phabricator.
View all 18 community-submitted tasks that were resolved last week. For example, the issue where CodeMirror syntax highlighter appears to have been enabled in error for existing editors has been fixed.
Updates for technical contributors
All wikis will be read-only for a few minutes on Wednesday, October 28 2026 at 15:00 UTC. This is for the datacenter server switchover backup tests, which happen twice a year. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies.
Scholarship and sponsorship applications for the 2027 Wikimedia Hackathon will close on Friday, October 30th. Submit your application through Pretix before the deadline!
MediaWiki:Gadget-codexTabs con contenuto "CodexTabs. Permette di attivare una visione a schede, utile per documentare funzionalità che variano in base alla skin."
Credo che sia anche da verificare MediaWiki:Gadget-dark-mode-toggle-pagestyles (primo dei nascosti) visto che c'è un mismatch tra le skin che sembra supportare (Vector legacy (2010), Vector (2022), MinervaNeue, MonoBook) e quelle dell'accessorio che ne fa uso (Timeless, MonoBook, Vector legacy (2010)). — $ZandDev ↩ 20:01, 29 ott 2026 (CET)
ho aggiornato il primo messaggio, non ho capito il secondo ("visione a schede"? anche la voce che parla di tab parla di "navigazione", cosa significa "visione"? è una traduzione dall'inglese? non riesco a trovare documentazione oltre al codice stesso). --valepert 20:46, 29 ott 2026 (CET)
Non c'è bisogno di creare i messaggi di sistema in quanto accessori nascosti, imho. --valcio••• 21:59, 29 ott 2026 (CET)
In quanto al mismatch di dark-mode-toggle, sistemato grazie --valcio••• 22:04, 29 ott 2026 (CET)
In realtà l'ho scritto per fornire un minimo di documentazione, che, come notato involontariamente da Valepert, serve. — $ZandDev ↩ 19:40, 31 ott 2026 (CET)
[@ Valepert] In realtà la descrizione me la sono inventata io di sana pianta. Beh "navigazione a schede" va anche meglio. — $ZandDev ↩ 19:36, 31 ott 2026 (CET)
Errore Lua
Segnalo un errore Lua nella pagina Tangaza: Errore Lua in Modulo:Conversione alla linea 59: unità di misura incompatibili: weight e area.Jihaim (msg) 11:27, 30 ott 2026 (CET)
Fatto c'era una superficie indicata in chilogrammi invece che in chilometri quadrati su Wikidata. --valepert 11:31, 30 ott 2026 (CET)
in questo caso l'unità di misura era centimetri invece che km². --valepert 11:40, 30 ott 2026 (CET)
SimilarTitles
Visto che questo è il posto delle cose tecniche, informo che il @SuperBozzolan, da non confondersi con SuperBeton, ha appena aggiornato la versione in fase di prova dell'accessorio MediaWiki:Gadget-SimilarTitles, il cui codice JS attuale è qui. Come ho già scritto in pagina di discussione, penso che sia necessario che qualcun'altro lo provi prima di applicare pubblicamente le modifiche, e per qualsiasi evenienza o segnalazione la pagina di discussione è sempre aperta;) — $ZandDev ↩ 17:09, 1 nov 2026 (CET)
VisualEditor auto-generated reference names
Hi, I'm Johannes from Wikimedia Germany's Technical Wishes team. Apologies for writing in English, please support us by translating this message or providing a short summary in your language.
Our team has been working on a community wish to improve VisualEditor's auto-generated reference names in recent months. When re-using a reference in VisualEditor that doesn't have a name yet, VisualEditor automatically assigns a name lik <refname=":1">. Editors on many wikis have long requested for these names to be human-readable and meaningful.
We've now implemented a mechanism for wikis to configure automatic reference names. Configuration is a multi-step process as described in mw:Help:Cite/VisualEditor reference names:
You can create template to define how content-based names should be created (e.g. if you prefer names like <refname="LastnameYear-1"> or <refname="example.com-1">, your autoname template would define which citation template parameters to use for creating such names). test2wiki:Template:Autoname is a simple example of such a template.
Many wikis probably want to extract content from citation template parameters (e.g. the year from |date=) – in that case you can create a Lua module to get even better names (see e.g. en:Module:Autoname, fr:Module:NomRefAuto or de:Modul:VisualEditorRef).
Once you've create one (or multiple) autoname templates (and a module if you'd like that) you need to create MediaWiki:Cite-autoname-template-map.json to map which autoname template(s) to use for which citation template(s) (example). The easiest way is just using a single autoname template as a default for all citation templates.
Even when configuring content-based reference names there will be instances where VisualEditor cannot create such a name (e.g. if it's a basic reference that doesn't use citation template) – in that case a fallback name will be created based on MediaWiki:Cite-ve-dialogbutton-reference-title and some other messages. The default fallback is usually something like <refname="Reference-1"> in your wiki's language. You can configure these fallback names as well
If you're done configuring everything (or if you just want to get rid of <refname=":1"> without configuring content-based names) you can enable the improved reference names at Special:CommunityConfiguration/Cite-VisualEditor-Autonames
See our help page for more information on technical details and examples.
Let me know if you have any questions or if there's something we can help you with if you're interested in configuring improved VisualEditor reference names! --Johannes Richter (WMDE) (msg) 12:38, 3 nov 2026 (CET)
Tech News: 2026-45
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
Many Wikimedia tools were taken offline last week because of a security vulnerability in PHP. This affected many websites worldwide. Toolforge and Cloud VPS have been back up since October 22. Many important tools have been gradually restored. Some tools need the respective volunteer maintainers to restart them. Others still need to upgrade to a patched PHP version. Some tools were using older versions of PHP which are not supported by the recent security patches. They will require maintainers to upgrade to a more recent version. This might require additional effort. You can follow the work on Wikitech.
Updates for editors
A new optional search experiment is running in the Wikipedia Android and iOS apps for Arabic, French, and Japanese Wikipedias. Participating readers can search inside articles and open quoted passages directly in their source articles, no answers or summaries are generated. This is the first of four experiments in Phase 2 of Semantic Search. It began on October 22 and runs for 20 days. Feedback is welcome on the project’s discussion page.
The Future Audiences team is planning to bring Share Cards to Wikipedia on mobile. This feature gives users the option to share a visually appealing card with friends, based on the article they are reading. The card contains the article’s title, image, opening text, and related attribution, and links back to the article for full reading. Editors are invited to try out this feature by adding ?useformat=mobile&sharecard=1 to any article URL from October 29 to November 8. Share any thoughts on the project talk page and report any bugs on Phabricator.
The default renderer for math formulas will change on November 2. After the change, the server sends the formula as MathML, and your browser uses MathJax to show it. This is the last step towards the Mathoid/RESTBase deprecation process, for sustainability and security reasons. You can ask questions or report problems.
Disgraziatamente, dopo avere completata la traduzione, da integraere per i collegamenti e per altre minuzie, appena riordinati alfabeticamente i paragrafi per ragioni che non comprendo alcuni di essi sono stati inseriti fuori posto (nelle note). In particolare nella nota 58 dopo il testo vero e proprio della nota sono state inserite una parte del paragrafo sulla Nuova Zelanda e quello sulla Polonia.
Miei tentativi di risolvere il problema annullando le mie ultime modifiche non hanno dato esito.
Pertanto mi permetto chiederVi una valutazione o, se impossibilitati, di indicarmi a chi chiedere un aiuto.
RingraziandoVi anticipatamente, Vi saluto cordialmente, --Alessandro Crisafulli (msg) 10:53, 5 nov 2026 (CET)
Modifica di vecchia versione per ripristino
Mi capita spesso di ripristinare le vecchie versioni di una pagina per patrolling. Da ieri pomeriggio ho notato di non avere più tale possibilità perché la vecchia versione si apre in sola visualizzazione. Preciso che uso quasi esclusivamente il browser da dispositivo mobile. Saluti Giuseppe --GIUSEPPEPEPIS 12:11, 5 nov 2026 (CET)
Tech News: 2026-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.
Weekly highlight
The Wikipedia Apps team is preparing to launch Year in Review in early December. Year in Review gives app users a personalized recap of how they read and engaged with Wikipedia throughout the year. The team is looking for volunteers to help make it available in as many languages as possible. Translators can contribute through translatewiki.net. For Android, search for yir under the "Untranslated" tab, and for iOS, search for year-in-review under the "Untranslated" tab.
Following the release of Reading Lists to all Wikipedias in September, logged-in users will soon be able to organize articles saved in their lists into customizable categories. This will enable readers to create collections and revisit saved articles based on their interests, potentially encouraging frequent visits to Wikipedia. The update will roll out to all Wikipedia users between November 9 and 16.
The Wikipedia Apps team is preparing to launch the first of two notification experiments for English Wikipedia readers on Android who have opted in to notifications. The three-week experiment will send notifications suggesting personalized Discover reading lists which are collections of Wikipedia articles recommended based on articles the reader has previously viewed. The goal is to understand whether these recommendations help readers discover relevant content and encourage them to return to the app. No action is required, and users can manage their notification preferences in the app settings. Learn more and share feedback.
A bug in the Global Watchlist was causing the page to fail to load for users who have unseen changes on Wikimedia Commons. The bug has now been fixed. If you temporarily removed commons.wikimedia.org from your personal Global Watchlist settings due to the bug, you can restore it there.
A new Beta feature called "Home" will be deployed to 10 Wikipedias for a limited test. This new feature aims to replace Special:Homepage for newcomers, with additional modules planned for the future to improve upon the current experience. If you want to participate in the test, please sign up. "Home" will be released to all users later this month.
On English and Russian Wikipedias, Source Verification is now available as an experimental Suggestion for experienced editors within Suggestion Mode. It uses an LLM hosted on LiftWing to try to check whether a cited source supports the claim it’s attached to. To try it out, please see these testing instructions. If you are at another language Wikipedia and your community is interested in trying it out, please express your interest.
View all 35 community-submitted tasks that were resolved last week. For example, an issue where dates passed as blank parameters to functions in wikitext were incorrectly interpreted using the month-day-year format instead of the day-month-year format, has now been fixed.
Updates for technical contributors
Starting on 1 December 2026, hCaptcha will be required for edits made via the API by non-autoconfirmed users. If your tool, gadget, or user script makes edits on behalf of newcomer users, see how to update it.
Toolforge has introduced two new beta features. "Toolforge alerts" send email notifications when a tool becomes unavailable, returns errors, or restarts frequently. "Extended logging" makes it easier to investigate problems by providing logs for events such as job creation, deletion, and deployment failures through the toolforge logs command. Both features are opt-in and help tool maintainers become aware of and resolve problems with their tools more quickly. Maintainers can enable alerts and learn how to access extended logs. They are also encouraged to try the features and provide feedback.
A proposal to change how we currently organize the Wikimedia Hackathon has been shared. It explores making the event more accessible to technical communities in different regions. Share your feedback on the proposal’s talk page; the deadline has been extended to November 13th.
Segnalo che il tool in oggetto non funziona (dà sempre 0 edit); temo sia ancora bloccato per la problematica PHP. Si può fare qualcosa? --Antonio1952 (msg) 15:38, 9 nov 2026 (CET)
Ordina categorie
sfruttando una funzionalità segnalata qualche numero fa di Tech News, in seguito a sessione "Chiedi all'IntAdmin" tenuta ad itWikiCon 2026, ho creato l'accessorio Ordina categorie, attivabile dalle preferenze, che aggiunge due link per organizzare le categorie in ordine temporale (ascendente o discendente). --valepert 20:44, 9 nov 2026 (CET)
Prossimo test sulla visibilità della modalità suggerimento
La finestra di dialogo di benvenuto che apparirà ai nuovi contributori sugli articoli per cui sono disponibili suggerimenti durante la fase di test. Il testo dell'esempio include: “Scopri come migliorare questo articolo”; “Ci sono 7 suggerimenti per migliorare questo articolo. Si tratta di attività guidate facoltative che puoi completare o ignorare.”; “Visualizza i suggerimenti”; “Non ora”
Ciao a tutti! Il team di Editing sta continuando a lavorare sulla Modalità Suggerimenti e volevamo informarvi di un esperimento che stiamo pianificando di avviare a breve.
Contesto
Ricordiamo che abbiamo sviluppato la Modalità Suggerimenti in risposta al risultato secondo cui un gran numero di lettori clicca sul pulsante di modifica perché curioso di provare a modificare, ma poi chiude l'editor quando non trova modifiche interessanti da fare. La Modalità Suggerimenti individua opportunità per migliorare l’articolo, come la rimozione di un link duplicato, e poi guida i lettori nel processo di modifica. Vediamo segnali che questo può portare sia a contributi utili sia a una prima esperienza di modifica positiva per i nuovi arrivati, incoraggiandoli a tornare e a diventare futuri editor esperti. Al momento è disponibile come funzionalità beta, quindi puoi provarla di persona! Basta andare in le tue impostazioni beta per attivarla e poi modificare usando il VisualEditor. Puoi vedere i tipi di suggerimento attualmente disponibili visitando Speciale:EditChecks (sono configurabili dagli amministratori). Stiamo lavorando ad altri e speriamo anche che aggiungiate i vostri usando la funzione TextMatch.”
Risultati dell'esperimento
Nei mesi di maggio e giugno abbiamo condotto un test A/B su 15 wiki, in cui abbiamo attivato la Modalità Suggerimenti per metà dei nuovi utenti. Tra gli utenti che hanno interagito con i suggerimenti, abbiamo riscontrato indicatori positivi su metriche come il tasso di completamento delle modifiche e la fidelizzazione. Tuttavia, abbiamo rilevato che solo circa un quarto del gruppo di test ha cliccato o toccato per visualizzare un suggerimento nelle voci in cui era disponibile. La nostra ipotesi di lavoro è che questo significhi che c'è un problema di reperibilità.
Test di reperibilità
Per verificare questa ipotesi, vorremmo provare un’esperienza utente che renda i suggerimenti più evidenti, tra cui accogliere gli editor che hanno effettuato l'accesso e che hanno pubblicato fino a 100 modifiche con una finestra a comparsa con Baby Globe, se stanno modificando una voce che ha dei suggerimenti. L’idea è che questa esperienza di onboarding compaia solo la prima volta che qualcuno avvia una sessione di modifica in cui è disponibile almeno un suggerimento. Nelle sessioni di modifica successive l’onboarding non verrà mostrato, anche se sono disponibili suggerimenti di modifica. L’esperimento è previsto a partire da giovedì 19 novembre e durerà 4-6 settimane. Mentre l’esperimento è attivo, il 50% dei nuovi utenti che hanno effettuato l'accesso (≤100 modifiche totali) vedrà l’onboarding della Modalità Suggerimenti la prima volta che tocca “modifica”, mentre l’altro 50% vedrà la normale esperienza della Modalità Suggerimenti. Puoi provare questa esperienza utente tramite questo prototipo (in inglese). Aprilo su un dispositivo mobile e tocca “modifica”.
Dopo questo test analizzeremo i risultati per capire se questa esperienza utente porta a un aumento complessivo delle stesse metriche che abbiamo monitorato nell’esperimento di inizio anno. Questo ci aiuterà a decidere i prossimi passi.
Come sempre, siamo curiosi di sapere cosa ne pensate! Grazie per la vostra continua collaborazione sulla Modalità Suggerimenti!
dopo Ordina categorie, altro accessorio che va aggiungersi alla nostra cassetta degli attrezzi è Voci da tradurre (disponibile sotto Ricerca e strumenti tra gli accessori attivabili dalle preferenze). il gadget è basato sul tool di Jalo non più mantenuto e segnalatomi da [@ Superchilum] e [@ Civvì] a cui sono state fatte alcune piccole migliorie (anche grazie al betatesting di [@ Mastrocom]). immaginatelo come una versione ridotta di PetScan (che fa molte più cose e ve lo consiglio se avete in mente ricerche complicatissime :D ). --valepert 20:41, 12 nov 2026 (CET)