Discussioni Wikipedia:CommonsTicker

message: Duesentrieb sta mettendo punto un nuovo "attrezzo" chiamato CommonsTicker - si tratta di un algoritmo che filtra le modifiche recenti di Commons e le instrada su ciascuna Wikipedia interessata alla modifica; una sorta di "modifiche recenti" di Commons personalizzata per ogni Wikipedia.
Il progetto è meglio spiegato su meta :m:User:Duesentrieb/CommonsTicker ed un prototipo è in funzione sulla Wiki tedesca :de:Wikipedia:CommonsTicker. Pensavo di inserire anche la nostra Wikipedia nel giro e di offrirmi come "admin di collegamento" per la fase di implementazione. Obiezioni? Procedo? --Paginazero - Ø 16:18, 19 mag 2006 (CEST)
replies: text: Vedo che Lp è stato bold e non ha perso tempo a chiedere... come non detto. --Paginazero - Ø 16:33, 19 mag 2006 (CEST)
replies: text: Az... ti stavo rispondendo :o) Va be' Allora mi limito alla domanda: esattamente cosa fa? Non capisco una parola di tedesco e ho capito poco, per limite mio, dalla tua spiegazione. Kal - El 16:38, 19 mag 2006 (CEST)
replies: text: Sì, sì ... diteci, diteci (no kartoffen pliiz but almost english ... :)) --Twice25 • (disc.) 16:51, 19 mag 2006 (CEST)

text: In pratica è un bot che passa ogni 4 ore ad aggiornare una pagina di ciascuna Wiki locale, segnalandovi tutte le modifiche importanti ai file di Commons utilizzati da quel progetto: nuove versioni, modifiche ai template di licenza, richieste di cancellazione, ecc. Per ora esiste solo in tedesco perché Duesentrieb sta ancora stabilizzandolo; ci vorrà alncora qualche giorno per andare a regime. Possiamo spostarci nella discussione di Wikipedia:CommonsTicker per approfondire il tema e vedere cosa c'è da fare. --Lp ↤ 18:19, 19 mag 2006 (CEST)
thread_title:  CommonsTicker 

message: Come spiegato nella homepage del progetto, CommonsTicker è un sistema di avviso in tempo quasi-reale che segnala tutte le modifiche importanti ai file di Commons utilizzati dalle varie Wikipedie: nuove versioni, modifiche ai template di licenza, richieste di cancellazione, ecc. dovrebbe consentire di migliorare la comunicazione tra i vari progetti locali e Commons, evitando incomprensioni e inconvenienti dovuti alla "lontananza" tra le comunità coinvolte. L'autore è Duesentrieb, admin sia su de.wiki che su Commons, che ha già realizzato numerosi tool per rendere più facile il lavoro sui progetti Wikimedia.
Nel momento in cui scrivo questo messaggio il sistema è ancora sperimentale e l'autore ha chiesto ancora qualche giorno di pazienza per affinare il meccanismo prima di partire ufficialmente. Nel frattempo, ho cominciato a prepararne lo scheletro sulla falsariga di :de:Wikipedia:CommonsTicker.
Cose già fatte (grazie a Civvi per la verifica del tedesco):
* Aperta la pagina del progetto e adattato l'incipit.
* Realizzato il template per le segnalazioni 
* Realizzato il template per il tipo di segnalazione 
Cose da fare:
* Tradurre o adattare la legenda dei tipi di segnalazione
* Decidere e attivare gli stili da usare per i vari tipi di segnalazione
Ad esempio, su de.wiki dopo una prima prova con le immagini "stile votazione" (+ - = ecc.) sono passati a un più sobrio stile "a pallini" corrispondente a queste classi di CSS:
 /* CommonsTicker styles */
 .tickerList ul    { list-style: none; text-indent:-1.5em; margin-left:2em;   text-align:left; }
 .tickerList ul ul { list-style: none; text-indent:0;      margin-left:1.5em; text-align:left; }
 .tickerAction_deleted:before     { content:" ✴ "; color: #FF0000; font-family:monospace; font-weight:bold; font-size:150%; }  
 .tickerAction_replaced:before    { content:" • "; color: #CC88FF; font-family:monospace; font-weight:bold; font-size:150%; }  
 .tickerAction_addedTag:before    { content:" • "; color: #FF8800; font-family:monospace; font-weight:bold; font-size:150%; }  
 .tickerAction_removedTag:before  { content:" • "; color: #00BB00; font-family:monospace; font-weight:bold; font-size:150%; }  
 .tickerAction_addedBad:before    { content:" • "; color: #FF8800; font-family:monospace; font-weight:bold; font-size:150%; }  
 .tickerAction_removedBad:before  { content:" • "; color: #00BB00; font-family:monospace; font-weight:bold; font-size:150%; }  
 .tickerAction_addedGood:before   { content:" • "; color: #00BB00; font-family:monospace; font-weight:bold; font-size:150%; }  
 .tickerAction_removedGood:before { content:" • "; color: #FF8800; font-family:monospace; font-weight:bold; font-size:150%; }
 .tickerUsage  { font-size:80%; }  /* ticker usage list */
 .tickerTemplateEntry    { font-weight: bold; } /* entry applies to a template used by multiple images */
--Lp ↤ 18:43, 19 mag 2006 (CEST)
thread_title: Spiega

message: Come annunciato qualche giorno fa, dovremmo essere pronti a partire. Sono stato contattato da Duesentrieb e salvo imprevisti stasera potremmo avviare la sperimentazione. 
Si possono scegliere alcune opzioni di configurazione per il bot:
* ordine delle voci : le più recenti si possono aggiungere in fondo o in testa
* modalità di aggiornamento : si possono aggiungere le nuove segnalazioni o riscrivere da capo
* modifiche minori : si possono nascondere le cancellazioni di vecchie versioni e le sostituzioni fatte da chi ha caricato l'immagine
Se non ci sono obiezioni, pensavo di proporre le seguenti impostazioni:
* Ordine: cronologico, nuove voci aggiunte in fondo alla pagina
* Aggiornamento: aggiunta, archiviando dopo un periodo da decidere
* Modifiche minori: ignorate, altrimenti si allunga troppo 
--Lp ↤ 18:22, 31 mag 2006 (CEST)
thread_title:  Opzioni 

message: Riporto il messaggio di spiegazione di Duesentrieb sui malfunzionamenti degli ultimi due giorni (segnalazioni non pervenute e fuori sequenza), che purtroppo al momento non sono risolvibili in modo efficace.
:Hi - the problems you see on the CommonsTicker page are caused by the massive replication lag on the toolserver - it's currently more than a day behind the live servers. Because the bot extracts "tagging" from the RSS feed of the live site, but uploads and deletions from the toolserver database, they may become "known" to the toolserver at different times - that is, a deletion from yesterday may pop up in today's report, because it was not yet "known" on the toolserver before.
:I'm working on fixing this, at least so that no entries are dropped entirely; I can't think of a good way to handle "latecomer" entries in append-mode, though :/
--Lp ↤ 13:47, 19 giu 2006 (CEST)
thread_title:  Malfunzionamenti 

message: e replication lag we currently see on the toolserver (it's more than a day behind). While I hope this will not happen again in the future, I have been working on improving CommonsTicker so it handles out-of-sync entries gracefully.
I plan to activate a new version of CommonsTicker tonight or tomorrow - so look out for any new problems. Here are the most relevant changes:
* fix handling of out-of-sync records (see above); added "latecomer" parameter to TickerEntry template (may be ignored)
id=377144 like this].
ikimedia.org/w/index.php?title=User%3ADuesentrieb%2FCommonsTicker&diff=377180&oldid=377144 here] for an example that strikes out the entry if status is set to "done".
For the future, I'm planning to let CommonsTicker post warnings to the talk page of articles that use an image das is (about to be) deleted. I'll post another announcement when that feature is ready.
This message was posted automatically by the CommonsTicker bot. For feedback and discussion, please go to meta:User talk:Duesentrieb/CommonsTicker -- CommonsTickerBot 16:15, 20 giu 2006 (CEST)
thread_title:  CommonsTicker: new version to fix some problems 

message: Hello - sorry, the privious message was a bit broken. Below is a full repost. Sorry again -- CommonsTickerBot 16:48, 20 giu 2006 (CEST)
thread_title:  CommonsTicker: new version to fix some problems 

message: Come si attiva il commonsticker su altri progetti? Siccome di là usiamo solo Commons, credo che questo tool ci sia più che utile... --Toobycome ti chiami?Need for news? 00:58, 28 lug 2006 (CEST)
thread_title:  Come si attiva? 

message: CommonsTicker was unable to post the latest update to the ticker page. This may happen
if there is a temporary problem with the servers or the network, or if the page has 
grown verry big. 
If you use "append" mode, please keep the page reasonably short, perhaps
by moving old entries that still need attention to a separate page, which could be included
in the main ticker page. Note that CommonsTicker will re-try to post the update on
the next run.
If you use "replace" mode, please consider requesting a shorter interval (less days) to watch.
CommonsTicker will not try to re-post the update, since it will replace the entire page
on the next run anyway.
(this is an automated message) -- CommonsTickerBot 17:54, 3 ott 2006 (CEST)
thread_title:  CommonsTicker failed to post update: it-wikipedia-org.ticker.wiki.20061003154112.pending 

message: CommonsTicker was unable to post the latest update to the ticker page. This may happen
if there is a temporary problem with the servers or the network, or if the page has 
grown verry big. 
If you use "append" mode, please keep the page reasonably short, perhaps
by moving old entries that still need attention to a separate page, which could be included
in the main ticker page. Note that CommonsTicker will re-try to post the update on
the next run.
If you use "replace" mode, please consider requesting a shorter interval (less days) to watch.
CommonsTicker will not try to re-post the update, since it will replace the entire page
on the next run anyway.
(this is an automated message) -- CommonsTickerBot 17:42, 9 ott 2006 (CEST)
thread_title:  CommonsTicker failed to post update: it-wikipedia-org.ticker.wiki.20061009153004.pending 

message: Diventa difficile gestire gli archivi superata la metà del mese (quello di settembre è di 532 KB, quello di ottobre è già a 182). Se ne facciamo 2, o 3? --.anaconda 04:38, 12 ott 2006 (CEST)
replies: text: Sì, oltretutto verso la fine trovano il limite sull'espansione dei template. Il problema era già stato sollevato da Kal-El, che aveva proposto uno split giornaliero. Per non perdere troppo tempo a mano, avevo chiesto all'autore di Werdnabot se il suo botolo archiviatore era adattabile facimente alla bisogna, e mi ha detto che era interessato a renderlo più generale comprendendo anche il nostro caso. Ora sollecito una risposta, se non arriva entro un paio di giorni ce ne prendiamo un pezzetto per uno e via. --Lp ↤ 10:12, 12 ott 2006 (CEST)
replies: text: Ok. --Kal - El 11:25, 12 ott 2006 (CEST)
thread_title:  Archivi 

message: CommonsTicker was unable to post the latest update to the ticker page. This may happen
if there is a temporary problem with the servers or the network, or if the page has 
grown verry big. 
If you use "append" mode, please keep the page reasonably short, perhaps
by moving old entries that still need attention to a separate page, which could be included
in the main ticker page. Note that CommonsTicker will re-try to post the update on
the next run.
If you use "replace" mode, please consider requesting a shorter interval (less days) to watch.
CommonsTicker will not try to re-post the update, since it will replace the entire page
on the next run anyway.
(this is an automated message) -- CommonsTickerBot 07:33, 29 dic 2006 (CET)
thread_title:  CommonsTicker failed to post update: it-wikipedia-org.ticker.wiki.20061229063105.pending 

message: ﻿Hello
As you may have noticed, there have been some problems with CommonsTicker lately:
* first, the toolserver was down. After it was back up, we had to wait for fresh database dumps.
* also, many updates where failing because ticker pages where growing too large. Updates that went through half-way somtimes also caused entries to be posted multiple times, making the problem worse.
* when I tried to improve performance, I introduced a bug that caused the ticker to post trash sometimes. I disabled the ticker again when I was told about it, and I have fixed all effected pages yesterday (I hope I didn't miss any).
To sort this out completely, I have to rewrite parts of CommonsTicker. For now, I will enable the ticker again for most wikis, but not for the ones that where having most trouble - namely de-wikipedia, en-wikinews, eo-wikipedia, es-wikipedia, fr-wikipedia, ja-wikipedia, ru-wikipedia, simple-wikipedia and zh-wikipedia. I'll have to investigate those more closely.
So please keep an eye on CommonsTicker in the next days - if there is any more trouble, please tell me, preferrably on meta:User_talk:Duesentrieb/CommonsTicker.
Regards -- :meta:User:Duesentrieb 14:35, 5 gen 2007 (CET)
thread_title:  CommonsTicker: Ticker Trouble 

message: ﻿I am currently testing a new version of CommonsTicker (dubbed CommonsTicker NG) on the german Wikipedia - problems with ticker pages growing too large made a partial rewrite necessary. Most changes are "under the hood", the larges change for users is in the way the ticker page is structured and updated:
CommonsTicker will now create a subpage for each day, and include this as a template on the ticker page. New entries for a given day are added to the respective subpage without modifying existing entries on that subpage. Old subpages (sections) are removed automatically from the main ticker page - per default, 7 sections are kept (days for which there are no entries are not counted). Please check that your ticker page has both start- and end-markers for the region where CommonsTicker should post (see m:User:Duesentrieb/CommonsTicker#Ticker_Page); everything between the markers will be replaced. If the markers are missing, the entire page is replaced. 
When I have finished testing CommonsTicker NG, I will activate the new version on the wikis where CommonsTicker is currently disabled due to problems with page size (the large projects I mentioned in the last announcement). When all goes well, I will start to switch other wikis to NG one by one, as seems convenient. If you want the new version soon, or you don't want it yet for some reason, please tell me about it on m:User:Duesentrieb/CommonsTicker#Change_Requests.
This message was posted automatically by the CommonsTicker bot. For feedback and discussion, please go to meta:User talk:Duesentrieb/CommonsTicker -- CommonsTickerBot 15:43, 6 feb 2007 (CET)
thread_title:  CommonsTicker: CommonsTicker, The Next Generation 

message: CommonsTicker was unable to post the latest update to the ticker page. This may happen
if there is a temporary problem with the servers or the network, or if the page has 
grown verry big. 
If you use "append" mode, please keep the page reasonably short, perhaps
by moving old entries that still need attention to a separate page, which could be included
in the main ticker page. Note that CommonsTicker will re-try to post the update on
the next run.
If you use "replace" mode, please consider requesting a shorter interval (less days) to watch.
CommonsTicker will not try to re-post the update, since it will replace the entire page
on the next run anyway.
(this is an automated message) -- CommonsTickerBot 23:15, 1 mar 2007 (CET)
thread_title:  CommonsTicker failed to post update: it-wikipedia-org.ticker.wiki.20070301221441.pending 

message: Dopo alcuni mesi torno a riproporre la questione. Questa pagina non la guarda nessuno; io la guardo quando me ne ricordo e non ho altro da fare (dato che porta via un bel po' di tempo...), e un paio di altri utenti. Ad esempio, fino a poco fa c'era ancora aprile da controllare. Siamo sicuri che ci interessano i reupload dei file? È già tanto se riusciamo a seguire le cancellazioni... --.anaconda 02:32, 14 mag 2007 (CEST)
replies: text: C'è poco da aggiungere: è così, non si riesce a fare di più.Anche se è perfettamente comprensibile l'utilità dei reup. Si può ovviare in qualche modo? Ho visto che c'è un "delinker" automatico in circolazione ma non ho capito bene con che frequenza e/o periodicità gira. --Kal - El 02:46, 14 mag 2007 (CEST)
replies: text: Gli eventi riportati si possono configurare. Volendo i reupload si possono disabilitare - questo proponevo. Per il CommonsDelinker se ben ricordo qualche riga sul funzionamento dovrebbe esserci nella pagina utente. --.anaconda 03:11, 14 mag 2007 (CEST)
replies: text: Vista la presenza ormai consolidata del CommonsDelinker per la rimozione vera e propria (a proposito, se a qualcuno interessa qui si discute se assegnare o meno il flag di bot), credo che possiamo usare i due strumenti in modo integrato. A cosa ci serve, principalmente, il CommonsTicker? Se mi date conferma su quali opzioni di configurazione ci sono più utili, mi attivo verso Duesentrieb. --Lp ↤ 14:08, 14 mag 2007 (CEST)
replies: text: Personalmente lo uso per togliere le immagini cancellate e basta. Considerata la presenza del delinker diventa inutile? (il mio lavoro sporco, intendo) --Kal - El 14:17, 14 mag 2007 (CEST)
replies: text: Il CommonsDelinker non le toglie tutte; però si potrebbero integrare meglio i due bot: non c'è bisogno di riportare immagini già orfanizzate dal delinker. --.anaconda 14:20, 14 mag 2007 (CEST)
replies: text: Visto che il Delinker si occupa del lavoro sporco a cose fatte, potremmo riservare al Ticker il ruolo preventivo di "allerta" sulle cancellazioni? Ditemi voi se basta... --Lp ↤ 14:22, 14 mag 2007 (CEST)
replies: text: Per me è ok. Kal - El 02:43, 15 mag 2007 (CEST)
thread_title:  Eventi 

message: CommonsTicker was unable to post the latest update to the ticker page. This may happen
if there is a temporary problem with the servers or the network, or if the page has 
grown verry big. 
If you use "append" mode, please keep the page reasonably short, perhaps
by moving old entries that still need attention to a separate page, which could be included
in the main ticker page. Note that CommonsTicker will re-try to post the update on
the next run.
If you use "replace" mode, please consider requesting a shorter interval (less days) to watch.
CommonsTicker will not try to re-post the update, since it will replace the entire page
on the next run anyway.
(this is an automated message) -- CommonsTickerBot 16:29, 30 lug 2007 (CEST)
thread_title:  CommonsTicker failed to post update: it-wikipedia-org.ticker.wiki.20070730142407.pending 

message: CommonsTicker was unable to post the latest update to the ticker page. This may happen
if there is a temporary problem with the servers or the network, or if the page has 
grown verry big. 
If you use "append" mode, please keep the page reasonably short, perhaps
by moving old entries that still need attention to a separate page, which could be included
in the main ticker page. Note that CommonsTicker will re-try to post the update on
the next run.
If you use "replace" mode, please consider requesting a shorter interval (less days) to watch.
CommonsTicker will not try to re-post the update, since it will replace the entire page
on the next run anyway.
(this is an automated message) -- CommonsTickerBot 12:29, 7 ago 2007 (CEST)
thread_title:  CommonsTicker failed to post update: it-wikipedia-org.ticker.wiki.20070807102356.pending 

message: CommonsTicker was unable to post the latest update to the ticker page. This may happen
if there is a temporary problem with the servers or the network, or if the page has 
grown verry big. 
If you use "append" mode, please keep the page reasonably short, perhaps
by moving old entries that still need attention to a separate page, which could be included
in the main ticker page. Note that CommonsTicker will re-try to post the update on
the next run.
If you use "replace" mode, please consider requesting a shorter interval (less days) to watch.
CommonsTicker will not try to re-post the update, since it will replace the entire page
on the next run anyway.
(this is an automated message) -- CommonsTickerBot 17:52, 23 ago 2007 (CEST)
thread_title:  CommonsTicker failed to post update: it-wikipedia-org.ticker.wiki.20070823154558.pending 

message: CommonsTicker was unable to post the latest update to the ticker page. This may happen
if there is a temporary problem with the servers or the network, or if the page has 
grown verry big. 
If you use "append" mode, please keep the page reasonably short, perhaps
by moving old entries that still need attention to a separate page, which could be included
in the main ticker page. Note that CommonsTicker will re-try to post the update on
the next run.
If you use "replace" mode, please consider requesting a shorter interval (less days) to watch.
CommonsTicker will not try to re-post the update, since it will replace the entire page
on the next run anyway.
(this is an automated message) -- CommonsTickerBot 16:27, 28 ago 2007 (CEST)
thread_title:  CommonsTicker failed to post update: it-wikipedia-org.ticker.wiki.20070828142229.pending 

message: CommonsTicker was unable to post the latest update to the ticker page. This may happen
if there is a temporary problem with the servers or the network, or if the page has 
grown verry big. 
If you use "append" mode, please keep the page reasonably short, perhaps
by moving old entries that still need attention to a separate page, which could be included
in the main ticker page. Note that CommonsTicker will re-try to post the update on
the next run.
If you use "replace" mode, please consider requesting a shorter interval (less days) to watch.
CommonsTicker will not try to re-post the update, since it will replace the entire page
on the next run anyway.
(this is an automated message) -- CommonsTickerBot 16:33, 30 ago 2007 (CEST)
thread_title:  CommonsTicker failed to post update: it-wikipedia-org.ticker.wiki.20070830142731.pending 

message: CommonsTicker was unable to post the latest update to the ticker page. This may happen
if there is a temporary problem with the servers or the network, or if the page has 
grown verry big. 
If you use "append" mode, please keep the page reasonably short, perhaps
by moving old entries that still need attention to a separate page, which could be included
in the main ticker page. Note that CommonsTicker will re-try to post the update on
the next run.
If you use "replace" mode, please consider requesting a shorter interval (less days) to watch.
CommonsTicker will not try to re-post the update, since it will replace the entire page
on the next run anyway.
(this is an automated message) -- CommonsTickerBot 04:15, 4 mar 2008 (CET)
thread_title:  CommonsTicker failed to post update: it-wikipedia-org.ticker.wiki.20080304030540.pending