Yes, that would be very welcome by all contributors reviewing images.
Regards,
Yann
On Tue, 18 Jun 2019, 22:29 James Heilman, wrote:
> So Yann should we as a community just build something as a proof of
> concept? If we are talking less than 250 USD per month, I am sure we can
> scrounge up
So Yann should we as a community just build something as a proof of
concept? If we are talking less than 250 USD per month, I am sure we can
scrounge up the money for a trial 6 month trial.
James
On Tue, Jun 18, 2019 at 2:59 AM Yann Forget wrote:
> Hi,
>
> Yes, James' pricing doesn't match the
Hi,
Yes, James' pricing doesn't match the actual cost.
We do not need to check all images uploaded to Commons, only the suspicious
ones (small images without EXIF data).
If we check 2,000 images a day (more than enough IMO), that would cost $7 a
day, so $210 a month.
Regards,
Yann
Le mar. 18
The landscape has changed quite a bit since 2012, and there are a number of
players that could offer a service like this by now. It may be worthwhile
exploring them briefly (including but not limited to Google), if we believe
this is important enough to invest time in (and I agree that there is a
Google has been offering reverse image search as part of their vision API:
https://cloud.google.com/vision/docs/internet-detection
The pricing is $3.50 per 1,000 queries for up to 5,000,000 queries per month:
https://cloud.google.com/vision/pricing
Above that quantity "Contact Google for more
On Mon, 17 Jun 2019 at 06:28, Yann Forget wrote:
> It has been suggested many times to ask Google for an access to their API
> for searching images,
> so that we could have a bot tagging copyright violations (no free access
> for automated search).
> That would the single best improvement in
Hi,
It has been suggested many times to ask Google for an access to their API
for searching images,
so that we could have a bot tagging copyright violations (no free access
for automated search).
That would the single best improvement in Wikimedia Commons workflow for
years.
And it would benefit
Leila
Since I raised this particular issue,, I'll take the liberty of giving an
answer to this question, even though you addressed it to Benjamin. The
failure that I was pointing to was not the failure to identify copyright
violations, but the failure to address the huge backlog of probable
Hi Benjamin,
My name is Leila and I'm in the Research team in Wikimedia Foundation.
Please see below.
On Mon, Jun 17, 2019 at 12:59 AM Benjamin Lees wrote:
>
> The community has been working on copyright violation issues for a long
> time.[2] There are probably ways the WMF could support
