News for hackers. Stuff that matters.
Re:Google removes ‘view image’ button from search results by prepend on Friday February 16, 2018 @05:43AM (#16391434)
I don’t believe that this is the sole motivator. As others have said, they could remove this for Getty images only (based on domain, based on reverse image search, lots of ways). But also, this seems like an absurd judgement, that if true they would want to highlight how the judgement had a very specific design fix as part of the settlement.

Since Google isn’t highlighting any such absurd ruling’s specific language then there must be some other reason.

Re:Google removes ‘view image’ button from search results by simonh on Friday February 16, 2018 @07:34AM (#16391864)
>...there must be some other reason.

If Getty can successful sue them, then any image rights holder can do so. Making an exception for Getty images doesn't resolve the underlying general liability or infringement. That means if another rights holder were to sue them for not addressing that liability for their images, now Google are infringing wilfully and subject to punitively increased sanctions or damages. That's reason enough to apply this remedy across the board.

Re:Google removes ‘view image’ button from search results by prepend on Friday February 16, 2018 @11:55AM (#16393678)
YouTube and many other sites have systems to work with rightsholders. It would be trivial for Google to allow Getty and others to manage their images that show up while still retaining functionality for the billions of images created by people who don’t care or who even explicitly allow Creative Commons usage.

Thus my suspicion. What’s a little sad is 15 years ago I would give Google the benefit of the doubt, but this reminds me how times have changed.

Re:Google removes ‘view image’ button from search results by simonh on Saturday February 17, 2018 @11:52AM (#16401461)
YouTube, where a user chooses to upload content and Google defines the platform features and standards, is pretty different to search.

‘Still retaining functionality’ would require assuming permissive access to images as the default, which is what has got a Google into this mess in the first place. The whole point of this is that, for sites and rights holders that don’t explicitly allow access, Google cannot assume they grant it. They have to assume the most restrictive grant of rights, and adoption of metadata to indicate more permissive access is so poorly adopted it’s just irrelevant in practice.

Re:Google removes ‘view image’ button from search results by tripzilch on Monday February 19, 2018 @11:47AM (#16413920)
> They have to assume the most restrictive grant of rights, and adoption of metadata to indicate more permissive access is so poorly adopted it’s just irrelevant in practice.

Try the advanced image search options, just like many other modern image search engines, as a user, you can filter for permissive licenses. I'm not sure how they gather that metadata, but the results I'm getting, it's not poorly adopted at all.

So they could in fact retain the functionality for images with the right license.

Re:Google removes ‘view image’ button from search results by subroutine on Friday February 16, 2018 @07:39AM (#16391887)
I think Google prefers to minimize the: "if this domain, and only this domain, do this special thing". Like you said, given that it would be absurd to remove a UI element based on some whim that it'd put them in compliance, I'm sure a major element of the plaintiff's litigation case hinged on this very feature.
Re:Google removes ‘view image’ button from search results by prepend on Friday February 16, 2018 @11:57AM (#16393692)
They have many cases of this. They actively filter based on domain to comply with takedown notices. That’s the most public example of how they have a huge number of exceptions based on domain and file.

Of course, I’m sure they do this in an intelligent way rather than literally a bunch of one off kludges.

Re:Google removes ‘view image’ button from search results by subroutine on Saturday February 17, 2018 @02:51PM (#16402374)
Maybe completely ignoring a domain is different than a implementing subroutine that ignores indexing a domain's images but not its other (text-based) content?