There are no blocking tasks listed. General issue is, will the average user know how to recognize likely flickr-washing?

It is time to promote Wikimedia-Hackathon-2015 activities in the program (training sessions and meetings) and main wiki page (hacking projects and other ongoing activities). Follow the instructions, please. If you have questions, about this message, ask here.

Did someone work on this project during Wikimedia-Hackathon-2015? If so, please update the task with the results. If not, please remove the label.

See blocking tasks (TBD) for more.

I listed an obvious blocking task (the one you showcased in Lyon), but I have no idea about the rest.

In T90004#1284013, @Mattflaschen wrote:

There are no blocking tasks listed. General issue is, will the average user know how to recognize likely flickr-washing?

I want to know about this too. Unless there is solution for this, I'm certain that Commons community will come phab again to disable the function with lots of files to clean up.

We are trying to help all open tasks listed under "Work continues after Lyon" at the Wikimedia Hackathon 2015 workboard finding their best way forward.

• If you are participating in Wikimania, consider adding the #Wikimania-Hackathon-2015 project to get this task in that loop, which is about to start.
• If you think this project could welcome help from a dedicated Google Summer of Code or Outreachy intern, or from an Individual Engagement Grant, add the Possible-Tech-Projects project.
• If you would like to receive some other type of support (organizing a Tech Talk, establishing contacts with existing developer teams in Wikimedia or elsewhere, travel sponsorship for a related activity... you name it), please create a subtask explaining your request and associate it with #Engineering-Community (or you can start by commenting here if you prefer).
• Keeping the description, priority and assigned fields up to date always helps. :)

For some context about this message, see T101151: Evaluate which projects showcased at the Wikimedia Hackathon should be supported further. It is the last communication related to Wikimedia-Hackathon-2015 that we will post here.

A sever side flckr review and blacklist check is needed. This are, of course, blocking tasks.

In T90004#1407991, @Steinsplitter wrote:

A sever side flckr review and blacklist check is needed. This are, of course, blocking tasks.

Apart from that, my point at T90004#1324963 is still valid - there should be a way to mitigate the flickrwashing. Possibly Community-consensus-needed?

In T90004#1586712, @revi wrote:

In T90004#1407991, @Steinsplitter wrote:

A sever side flckr review and blacklist check is needed. This are, of course, blocking tasks.

Apart from that, my point at T90004#1324963 is still valid - there should be a way to mitigate the flickrwashing. Possibly Community-consensus-needed?

Of course the flickr washing blacklist must be checked. Before this all has been fixed, we can't enable this tool for all users.

If the files are reviewed on the server side, then the first edit must also be marked with a special tag which can't be faked. It is possible to fake upload log summaries and file information page content. An alternative solution for the upload wizard is to mark the file as 'unreviewed' and insert a {{flickrreview}} template with no parameters, asking for bot review.

I have a proposal activate this option for all.

The Upload Wizard should integrate a form of Flickr2Commons but without its faults (so it should be able to spot duplicates immediately), however only a very select group of people can use this and many people already have the wrong impression that Wikimedia Commons is only FOR YOUR OWN PHOTOGRAPHS despite there being billions of free educational images on the internet and many millions of them are on Flickr. Either the marketing has to change (and users should understand that public domain images are acceptable while fair use is it on Wikimedia Commons) or the tools ⚙ have to reflect this.

Also see T214003.

There is only one blocking task for this and that's T236341. @MarkTraceur if this has high priority, maybe raise the priority on T236341?

dupe T236342?

In T90004#5933603, @Shizhao wrote:

dupe T236342?

Kinda, T236342 is newer but actually specific about what has to be done. (namely T236341 and setting a specific limit)

Hard to believe nobody has picked this up yet. So many users would benefit from a change that, as far as I understand, shouldn't be total rocket science. Not saying it's easy, last time I messed with JS I broke MediaWiki's file system maybe. (T246695)

Thank you everyone who worked on this. 😊