- Apple is considered to have come out of this with a black eye.
I don’t see how Item 4 follows from Items 1-3.
Let’s check some facts then. Apple:
Some of our Services allow you to submit content. You retain ownership of any intellectual property rights that you hold in that content. In short, what belongs to you stays yours.
When you upload or otherwise submit content to our Services, you give Google (and those we work with) a worldwide licence to use, host, store, reproduce, modify, create derivative works (such as those resulting from translations, adaptations or other changes that we make so that your content works better with our Services), communicate, publish, publicly perform, publicly display and distribute such content. The rights that you grant in this licence are for the limited purpose of operating, promoting and improving our Services, and to develop new ones. This licence continues even if you stop using our Services (for example, for a business listing that you have added to Google Maps).
I was planning to write that this is just the usual user unfriendly legalese. Then I stopped for a second to imagine how could a sync service become better by creating derivative work, publishing, and publicly displaying and distributing my files. I have no ideas.
When it took its approach to mobile software, Google made a big bet that smartphones and tablets were sufficiently mature and thus could be built in a way that didn’t require Google owning all points of the value chain. For the last year it seemed that Google bet right. Android was very quickly adopted by licensees to the point that it achieved nearly 50% share in smartphone shipments last quarter.
However, lately, cracks began to appear in the strategy.
Google sets up a set of fake results that afterwards show up in Bing results
Microsoft is using clickstream information as one of the ranking algorithm parameters.
Google accuses Microsoft for “copying” Google’s search results.
The fact that Bing tries to suggest other related searches while Google is not doing it makes me think that:
The fact that Google accusses such a young competitor makes me think that Google has hit a wall in its attempt to improve its current algorithms and so it starting to fear its competitors.
Disclaimer: This represent a personal perspective on the subject.
I haven’t upgraded the Python Google App Engine in a while and now I’m trying to catch up with the latest changes.
Size and quantity limits on datastore batch get/put/delete operations have been removed. Individual entities are still limited to 1 MB, but your app may batch as many entities together for get/put/delete calls as the overall datastore deadline will allow for.
I think this was previously set to 500.
The total size of Memcache batch operations is increased to 32 MB. The 1 MB limit on individual Memcache objects still applies.
I have an extension which allows storing larger objects into Memcache.
URLFetch allowed response size has been increased, up to 32 MB. Request size is still limited to 1 MB.
For the Task Queue, developers can specify task retry_parameters in their queue.yaml.
More details here. The new
retry_parameters supports the following additional options:
The deadline for Task Queue and Cron requests has been raised to 10 minutes. Datastore and API deadlines within those requests remain unchanged.
Task Queue has been officially released, and is no longer an experimental feature. The API import paths that use ‘labs’ have been deprecated. Task queue storage will count towards an application’s overall storage quota, and will thus be charged for.
Developers can now enable Warmup Requests. By specifying a handler in an app’s app.yaml, App Engine will attempt to send a Warmup Request to initialize new instances before a user interacts with it. This can reduce the latency an end-user sees for initializing your application.
More details here.
The deadline for offline URL Fetch API requests for Python and Java have been increased to a maximum of 10 minutes. The default deadline for offline URL Fetch requests remains the same.
This refers to URL Fetch requests sent from cron jobs and tasks. (see this)
According to this: “You can set a deadline for a request, the most amount of time the service will wait for a response. By default, the deadline for a fetch is 5 seconds. The maximum deadline is 10 seconds.”
During application creation, developers can choose between two Datastore configurations: High Replication or Master/Slave. See this.
You can set your application’s datastore to read-only mode in the Admin Console. Any writes attempted while the app is set to read-only will throw a CapabilityDisabledError. This feature can be helpful for migrating or copying data between two applications. See read-only mode.
The Datastore Admin tool has been updated to allow copying of one app’s datastore to another. The destination app must have the Remote API enabled. See docs.
httplibto make HTTP requests. When running in App Engine, these libraries perform HTTP requests using App Engine’s URL fetch service, which runs on Google’s scalable HTTP request infrastructure.
If these dime-store scrapers were doing so well and generating so much traffic on the back of our content – how was the rest of the web faring? My enduring faith in the gravitational constant of Google had been shaken. Shaken to the very core.
But what if you are any of the other thousands of millions of websites or just a blog?
I guess from Google’s perspective it’s some sort of a win-win situation:
Google is only forgetting the last part of this equation: the content producers.