Skip to main content
 

Oz Monolith

*An Update on the Oz Monolith*

So it's a little over been two weeks since we turned down most of Oz for frontends. Project Death Star removed most Google+ traffic. Purple Hummus removed contacts.google.com. Project Falcon got iOS G+ on FEDS. And the OneGoogle Notifications Widget is now exiting too.

There's still much more to do, Apiary APIs, widgets and more need to go. And lots of code to delete as you can see in the Rise and Fall of Oz by # of files below.

Thanks to everyone that removed services/code, and let me know if you're missing a killoz teams badge.

 

Looks like we're not quite   for image filtering.

TL;DR -- SIte displays porn content from freebase/knowledge graph that violates AdSense ToS.


_A quite strange thing happened recently. I have a news website and I'm using Freebase API to provide readers for more in depth information about the content of news articles.  The site runs Google's AdSense ads._

_Following the publication of a local news, on the sidebar containing text and images downloaded through Freebase API, an image of a woman with her bare breasts was displayed._

_Well, that image, made available by Freebase, which is a Google product, was considered obscene by the team of AdSense (also a Google product), which decided to suspend the service. A sort of vicious circle of Google, exercising a censorship on itself._

_Given the impossibility to make Google people understand that the visualization of such kind of images was occasional and not intentional, I'd prefer to avoid such problems in the future. Hence, I'd like to know whether there's some way, when using Freebase API, to filter out images considered obscene by the AdSense team._