We need to insert null revisions into the client for Wikibase changes.
This will allow changes to show up in the article history and display correctly in the watchlist.
In the simplest implementation, a null revision is treated as being done by IP user 127.0.0.1, similar to what Special:Import does.
It's not pretty, so we'll need a separate to-do to handle displaying external users and changes in a nicer way, everywhere in the client.
Version: master
Severity: major
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T56162 Almost impossible from client's perspective to restore deleted language links | |||
| Open | None | T42358 [Epic] Wikidata changes in article history | |||
| Open | None | T90435 [Epic] Wikidata watchlist improvements (client) | |||
| Open | None | T45578 Watchlist changes need unique revision id | |||
| Declined | None | T45581 Insert a null revision for wikibase changes |
(In reply to comment #0)
We need to insert null revisions into the client for Wikibase changes.
Really? Will there be a way to filter them out? One of the most appreciated effects of Wikidata is that articles' history, especially on smaller wikis, gets much cleaner... If you add them again to history it might become even harder to read it than it was before, depending on how obvious it is that it's equivalent to a bot change.
@Nemo: Yes I think we want a way to filter them out, yet having the null revision and the option to show (filter on) these changes is important also.
I agree with Nemo, we would be polluting page histories. And at least a very wide community consensus would be required for this change.