Btw, why is renames a destructive op? We have file redirects or am I missing something.

Regarding "in use" API, also see bug 29640

(In reply to comment #1)

Btw, why is renames a destructive op? We have file redirects or am I missing
something.

ForeignApiFile/Repo has always had problems with following redirects properly :\

(In reply to comment #3)

(In reply to comment #1)

Btw, why is renames a destructive op? We have file redirects or am I missing
something.

ForeignApiFile/Repo has always had problems with following redirects properly
:\

And furthermore, the Wikimedia Commons community doesn't let redirects for typos and other stuff.

Is there an interest in proposing this project for Outreach Program for Women?
If so, and if there at least one mentor for it. please move it to the "Featured projects" section. This way it will be automatically transcluded in
https://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_7

Thank you!

vladjohn2013 wrote:

Hi, this project is still listed at https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Build_an_interwiki_notifications_framework_and_implement_it_for_InstantCommons

Should this project be still listed in that page? If not, please remove it. If it still makes sense, then it could be moved to the "Featured projects" section if it has community support and mentors.

(In reply to comment #6)

Hi, this project is still listed at
https://www.mediawiki.org/wiki/Mentorship_programs/
Possible_projects#Build_an_interwiki_notifications_framework_and_implement_it
_for_InstantCommons

Should this project be still listed in that page? If not, please remove it.
If
it still makes sense, then it could be moved to the "Featured projects"
section
if it has community support and mentors.

It still makes sense, and would be a good project. Whether it has mentors is a separate question - although I am interested in this, I personally do not have the time to mentor anything in the near future.

Consider that this is already implemented in a "pull" sense in Extension:CommonsMetadata. We have file usage, and a bunch of other awesome image metadata, returned from the API that you could previously only get from the file page. This project may not take very long anymore.

Wikimedia will apply to Google Summer of Code and Outreachy on Tuesday, February 17. If you want this task to become a featured project idea, please follow these instructions.

In T48525#486127, @MarkTraceur wrote:

Consider that this is already implemented in a "pull" sense in Extension:CommonsMetadata. We have file usage, and a bunch of other awesome image metadata, returned from the API that you could previously only get from the file page. This project may not take very long anymore.

Do you think it is a good candidate for a GSoC / Outreachy project?

Wikidata has some sort of push notification system, I wonder if that's generic enough to reuse.

This task does not really require push notifications, though - the notifications are only relevant when you try to access a remote image, so they can be just pulled at that point.

In T48525#486127, @MarkTraceur wrote:

Consider that this is already implemented in a "pull" sense in Extension:CommonsMetadata.

https://www.mediawiki.org/wiki/Extension:CommonsMetadata says

The extension in its current form is intended to be a temporary solution, eventually replaced by Wikidata on Commons.

Which points to an inactive page in Commons, which points to https://www.mediawiki.org/wiki/Multimedia/Structured_Data

I still don't see how all this would be a solution for a third party MediaWiki using InstantCommons, though.

In any case, the context of this task looks like having too many moving parts. I wonder whether it is a good project for a new intern.

We have a Wikimedia-internal push notification. This can not be reused to notify 3rd party wikis. We had a team of students work on something for 3rd parties (pubsubhubbub) which could have been used for this. That was blocked from deployment. I think this is too much for one student/intern tbh.

I was thinking of pubsubhubbub. Is that project completely abandoned then?

This looks like a problem that needs a generic solution - there can be many different cases of 3rd-party wikis using remote content and needing notification (remote file repos, Wikibase, remote template transclusion, soon probably remote scripts/Scribunto modules) and we don't want each use their separate mechanism. Coming up with such a mechanism is way beyond GSoC, I agree. Maybe implementing it or starting to implement it once there is consensus how it shoul look could be such a task.

Agreed. And the students with pubsubhubbub would have been a great way to solve this if it wasn't blocked from deployment. Since the students are finished with the project they will not put in more work and I don't have resources on my team to spend on this after this setback anytime soon.

Thank you for your quick feedback. I have removed this task from Possible-Tech-Projects.

May be related to T125138?