Opera holds the web's most valuable secret
theregister.co.uk
theregister.co.uk
The article does very little to tell us why that's 'valuable' or indeed a secret.
Edit: to spell out my confusion. If you want to arbitrage ads, content providers would (presumably) need to include your ads in their content one way or another, so I don't see what advantage controlling the pipeline gives you. If you just want to inject ads into the content you're serving simply because you control the pipeline, then you can just as well inject regular ads, I don't see where the arbitrage part comes in.
This insulates the person doing the arbitrage from losing money because one or both of the markets changed (it is 'theoretically risk free').
So they would be theoretically be trading page impressions as they occur, to the highest bidder. Compare this to AdWords, which offers 'some amount of Cents' per impression.
You sell your adspace to opera, opera sells that AdSpace to someone else, dynamically based on market prices. (They could even sell it Google or whoever). Its like an ad stock market.
At least, that is my (very) speculative understanding.
edit: The key point is that they control the cache, so if you sell them ads and your page goes through the cache, they can insert it (whoever's ad it is) quickly. Otherwise it would be an extra level of indirection loading the ad.
from
http://labs.opera.com/news/2009/03/13/
Your privacy is important
Even when Turbo is enabled, encrypted traffic does not go through our compression servers. This means that when you are on a SSL site, we bypass these traffic and let you communicate with the SSL site directly. Opera generates statistics of the usage of Opera Turbo, but these are aggregated numbers and no information can be linked to a single user. Opera does not store any users’ private information.
http://www.opera.com/mobile/help/faq/#connection
"Is there any end-to-end security between my handset and — for example — paypal.com or my bank?"
"Opera Mini uses a transcoder server to translate HTML/CSS/JavaScript into a more compact format. It will also shrink any images to fit the screen of your handset. This translation step makes Opera Mini fast, small, and also very cheap to use. To be able to do this translation, the Opera Mini server needs to have access to the unencrypted version of the webpage. Therefore no end-to-end encryption between the client and the remote web server is possible.
If you need full end-to-end encryption, you should use a full web browser such as Opera Mobile."
Trolling much? They aren't hijacking anything. Opera Mini is a thin client (which lets it run on just about any phone, including old and crappy ones), so they have no choice but to pass everything through the rendering engine on their servers.
If Opera decided to act on this it could be the most valuable part of its business model. GMail etc. have shown that people are willing to pay with their privacy.
Disclaimer: I'm interning (so I don't know anything special) for Opera, but the opinions here purely my own.
I don't really see who would buy behavioral data on peoples browsing habits. That's fairly worthless unless you have a clear route to monetize it and connect back to those users.
GMail has a clear route - they show advertising on gmail.
All Opera could do is mess around with web pages, inserting their own advertising, or messing with content. Which would enrage users and website owners alike. As soon as they try to monetize, people will stop using it.
I use AdThwart on my desktop Google Chrome though!
I'll believe it when I see it (And then I'll block access for Opera mini users to my website).
Opera will NOT strip out ads from pages.
What Opera will do is to let the owner of the page choose to serve ads to mobile browsers through Opera's ad network.
So any ads from Opera on a site will be because the owner of the site requested them.
It is only occasionally noticeably faster, and the rendering is far worse. Mobile Safari is great because it actually renders sites appropriately. Opera mini is great because it's faster than your built-in phone browser, but it doesn't compete with real browsers even when it's marginally faster.
Also, the speed benefits are significant, only if you are on a slow connection.
What they say about the economics of mobile bandwidth and computing power vs. server bandwidth/CPU rings true, however. The trick would be to optimize the rendering for specific mobile browsers. One could even use the "native" rendering engine to do this. Apple should implement this trick for mobile Safari, optimized for the specific screen sizes of the various iDevices. Not only would this save rendering time and battery power on those devices, it would enable yet another advertising strategy for them.
Probably wary of bad publicity (for once) Apple accepted the application… and since then Opera barely touched it. No update to the non-standard look&feel, no update to the non-standard settings management (and widgets), no update to the awful zoom… and apparently barely useable on the iPhone 4…
And since they have't done any update to it since May while they released 5.1 for just about every other smartphone, I'm not exactly expecting anything.
[†] super-effective image and content compression? Elimination of multiple-server DNS lookups/requests/transfers? Compiling Javascript into a device's or Opera-internal "native" code on the server? I don't believe we've seen the last yet.
Take a look at the Turbo feature in Opera Mobile. It's similar to the Turbo feature on desktop. Once again, data is being sent through the server and it is being compressed. However, Turbo is capable of handling interactive-web-content (JavaScripts) because the rendering part is still being done locally.
P.S. What Opera is doing is similar to what www.onspeed.com does. I used to use that during my dialup days, and it was a big big help.
You are living in a dream world if you think compression is going away any time soon.
And with operators cutting down on data plans, limited bandwidth isn't going away any time soon either.
By the way, what about online banking etc. They are introducing yet another weak point by playing the middle man.
I was confused why or how OPML would serve Opera's purposes in this instance.
So basically, as long as Opera's security is ok, we are ok. However, if someone manages to find a hole, we might be screwed. But, how practical is it to launch an attack on a mobile webbrowser that is possibly using encrypted WiFi along with a encrypted communication channel? May be someone else can shed more light on this.
Other than that, governments can corrupt the certificate-issuing authorities and present you with forged SSL credentials.
http://www.eff.org/deeplinks/2010/03/researchers-reveal-like...
Comparing Opera's cache to Google's cache is not a good idea, they work differently.