Risker added a comment.

This is a hugely political issue. Let's please not do this unless necessary. Daniel has provided a patch for T177707 and Marius has been working on various other improvements.

I'm not sure how political it is at this point; it was an issue, certainly, when use of Wikidata was first being considered on some projects, and a regression to remove it from recent changes and/or watchlists may have negative impacts on a few projects. On the other hand, removing it entirely, with noise coming from communities about it, will in fact focus the minds to address this issue - not only for Wikidata, but also for ORES and for Commons changes as well. Two are in place now and are having an impact, and the third has been a much-desired feature for as long as I can remember. Getting this right is important and worthy of the investment of time of many knowledgeable developers, not just one or two people trying to do a quick "repair" without digging into the underlying issues. Including all of these things in some sort of easily accessible recent changes/watchlist profile is very important, particularly for projects with a larger community; however, the way we are doing things now (particularly on projects where the recent changes origins are heavily weighted toward Wikidata) is creating major bottlenecks. The methodology for including this data deserves some rethinking and testing of other options. We can't just keep tacking more tables onto watchlists/recent changes, if the impact is rendering RC/watchlists slow to the point of unusable or flooding the servers.

It strikes me that this is an unforeseen effect of the remarkable success of Wikidata. If not for its extensive usage on certain projects, the root causes of this bug would not have been identified so quickly. There is every reason to believe that if other projects continue to expand their use of Wikidata, they too will encounter the same issues; the same is true if a similar methodology is used to include Commons changes. This problem isn't really about Wikidata; it's about the effects of the ever-expanding use of recent changes. It's just particularly obvious with Wikidata because it has been so successful.


TASK DETAIL
https://phabricator.wikimedia.org/T171027

EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: jcrespo, Risker
Cc: Nirmos, Stryn, Mike_Peel, Capankajsmilyo, Elitre, Risker, Peachey88, Stashbot, Finavon, WMDE-leszek, saper, Masti, Lydia_Pintscher, D3r1ck01, matej_suchanek, Ankry, Ladsgroup, Lsanabria, Josve05a, Bawolff, greg, Dominicbm, Vriullop, Jmabel, Fae, IKhitron, Johan, Herzi.Pinki, jmatazzoni, Mattflaschen-WMF, KTC, Framawiki, zhuyifei1999, Marostegui, aaron, Andrei_Stroe, Turbojet, Rsocol, Strainu, Jwh, Pyb, Darwinius, Arbnos, Jdforrester-WMF, TheDJ, gerritbot, VladXe, Kf8, Liuxinyu970226, Jay8g, TerraCodes, Iniquity, jcrespo, Reedy, Catrope, Vicpeters, Demidenko, MaxBioHazard, Aklapper, Waytogoeducation, Lordiis, GoranSMilovanovic, Adik2382, Abiyoyo, Th3d3v1ls, Ramalepe, Liugev6, QZanden, Vali.matei, Jack_who_built_the_house, Lewizho99, Minhnv-2809, Maathavan, Poyekhali, Volker_E, Wong128hk, Luke081515, Wikidata-bugs, Base, aude, GWicke, El_Grafo, Gryllida, putnik, Steinsplitter, Mbch331, Krenair
_______________________________________________
Wikidata-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to