[06:41:40] You might use a simple alternative tool that I created in https://toolsadmin.wikimedia.org/tools/id/uploaders-in-cat (re @Camylevsky: Greetings all. For sometime now, I have been trying to get the number of uploaders using Toolforge, but the chart has not been a...) [06:45:35] It is because of the migration in wikimedia commons replica database. The tool uses recently removed `cl_from` field (as far as I remember). I already submitted a patch, but seems like the maintainer is not active. Anyway, a lot of tool was broken due to current structure and centralization of link targets. I tried to fix but most of the maintainers are not active, [06:45:35] so I tried rep [06:45:35] licated the tool with very basic UI (I hope no one would mind). (re @jeremy_b: idk why it's broken but it should stop loading Google JS on toolforge...) [06:46:04] @jeremy_b @Camylevsky [06:46:38] so how will you address the privacy policy violation? (re @nokibsarkar: It is because of the migration in wikimedia commons replica database. The tool uses recently removed cl_from field (as far as I ...) [06:48:31] Privacy policy? If I am not wrong in understanding your question, I am not collecting any private data at all. Even users do not need to be logged in to use the tool nor can they log in. It is a very basic structure tool. [06:49:44] you may not for any reason instruct a user's browser to load JS or CSS or fonts or images or any other resource from gstatic or Google domains. [06:50:31] if your tool is hosted on toolforge or wmcloud [06:51:25] I think we might be talking about something different. Are we talking about the new alternative tool i created (let's call it A) or the original tool (let's call it B)? [06:52:30] oops maybe I was confused. I was referring to `ptools`. [06:55:29] As far as I remember, tool A does not use any google hosted assets. But, let me check again. as for tool B, I did not go through the full code. Although it might be interesting if the maintainer is not active and I maintain the tool, it seems like I am not that proficient in PHP (I stopped using it 6 years ago). In tool B, I merely replicated the functionality, but [06:55:29] the code is no [06:55:29] t written in PHP. (re @jeremy_b: oops maybe I was confused. I was referring to ptools.) [06:57:55] By the way, if you are confused, the link to the tool is : https://uploaders-in-cat.toolforge.org/ @Camylevsky [06:59:00] Not very UI rich (one hour sketching), but functionality works 😁. [07:01:16] I imagine a patch won't be too hard but not opening laptop now. anyway will file a task for this, sounds like we'll need help getting it deployed. [07:01:56] By the way, I was very surprised to see the `cl_to` being removed from the common replica. Though , there might be some deprecation period and notice that I might've missed. [07:02:36] If it helps, my code is at: https://github.com/nokibsarkar/uploaders-in-cat (re @jeremy_b: I imagine a patch won't be too hard but not opening laptop now. anyway will file a task for this, sounds like we'll need help ge...) [07:08:28] the mail in my mailbox has cloud-announce list on the To list but I can't find it in cloud-announce archives. https://lists.wikimedia.org/hyperkitty/list/cloud@lists.wikimedia.org/message/7AMRB7G4CZ6BBOILAA6PK4QX44MUAHT4/ (re @nokibsarkar: By the way, I was very surprised to see the cl_to being removed from the common replica. Though , there might be some [07:08:29] deprecatio...) [07:10:49] is there any technical advantage or rationale you can give me (phabricator task or discussion)? Or is it just purely normalization? (re @jeremy_b: the mail in my mailbox has cloud-announce list on the To list but I can't find it in cloud-announce archives. https://lists.wiki...) [07:12:04] I don't remember offhand that particular change but a lot of these changes seem to be about space savings. on disk but I guess also in RAM. [07:14:26] in the archive I linked the announcement mentions T300222, T222224 [07:56:55] ok, now i can see the rationale. i need to practice reading old phabricator tasks, LOL.