Snaterlicious added a comment. Summing up the proposal:
Rationale: //Do not push any changes to the client that do not affect the output of a watched article, but push all changes that affect the output of a watched article.// 1. Any changes to the Entity that do not affect the output of the linked article, are out of context boundary as there is no direct relationship between such changes and the article. Even changes to multilingual values are not relevant as long as the value in the client's language (or its fall-back if there it no value in the client's language) remains untouched. 2. Changes to an Entity of which some content is integrated in a watched article not directly linked to the Entity (e.g. using arbitrary access) should be pushed to the ones watching the article accessing the Entity content as the output of this article is affected. (As long as the same content is not accessed from the article that is directly connected to the Entity as well, the ones just watching that article should not be notified.) 3. Regarding programmatically accessed Entity content as done by the Mobile extension: Such changes need to be pushed to the client as well since article output is affected. However, explaining to the user the reason why such changes appear in the list of recent changes is out of scope for Wikibase and, in general, has to be performed by the developers integrating programmatic access of Entity content. Basically, integrating Site Links in the client as done via the "In other languages" side bar is programmatic access as well. Conclusion: 1. //In general, changes to any Entity content (Label, Description, Aliases, Statements) should be pushed only if the affected content is accessed explicitly or programmatically from within the watched article.// If a user is interested in watching additional changes to the Entity, the user may watch the Entity in the repo. 2. //The filters currently offered in the client are sufficient.// (Though additional filters should probably be available in the repo.) There is no need for separate bot edit and patrolled edit filters. 3. //Pushing of programmatic changes should be a matter of Wikibase configuration.// Default configuration may be: - Changes to Site Links of the same project (may be altered to Site Links of all projects if there is an "In other projects" side bar). - Changes to Badges on the watched article. 4. In the scope of the proposed context, grouping changes to something called "Item changed" would make even less sense. //Grouping should be performed on Entity element level only// (i.e. "Statement changed" grouping changes to one particular Statement). TASK DETAIL https://phabricator.wikimedia.org/T90435 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>. EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Snaterlicious Cc: Snaterlicious, Liuxinyu970226, Quiddity, Rschen7754, Ainali, MisterSynergy, Lydia_Pintscher, Aklapper, daniel, Wikidata-bugs, aude _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
