W3C home > Mailing lists > Public > public-bpwg@w3.org > January 2009

Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting.

From: David Storey <dstorey@opera.com>
Date: Sun, 18 Jan 2009 17:01:24 +0100
Cc: Mobile Web Best Practices Working Group WG <public-bpwg@w3.org>
Message-Id: <13C188AE-4C75-4218-B92E-429CC04A8368@opera.com>
To: Luca Passani <passani@eunet.no>


>
>
>> I guess one difference is that certain proxies the end user chooses  
>> to use, such as by downloading and using Opera Mini, but it is a  
>> different ball game for proxies that operators push on the user  
>> without them selecting it (i.e. given to all mobile browsers).  I  
>> think the former is fine but not so much the latter.
>
> I think they are both wrong. But since OperaMini tends to be "opt- 
> in" by nature, it does not bother the rest of the ecosystem as much  
> as the others. FYI, Opera partnered with ByteMobile, which leverages  
> Opera's technology to reformat websites exactly as Novarra and all  
> the others (look at Voda Ireland, for example). Glad to hear that  
> Opera does not like this model.

"I" and "Opera" are not exactly the same thing.  I don't doubt it is a  
solution to a problem, especially when the transcoders are good quality.

>
>
>>
>> In regard to the no transform header; this can't work for solutions  
>> such as Opera Mini, where they only support using a proxy.
>
> I think OperaMini should stop transcoding HTTPS content

Wouldn't work.  Opera Mini only supports transcoded content.  Without  
it we'd have to show a screen saying "site not supported"  Not exactly  
good user experience, or what the user wants.  If a browser supports  
both regular html and transcoded content then I personally fully  
agree, but otherwise we need to serve the content.

Opera Mini exists to run on phones that wouldn't support a full  
browser.  Users do also run it on smart phones as it saves the user  
money in data traffic (and assumably the operator in data traffic  
costs).
>
> .
> Luca
>

David Storey

Chief Web Opener,
Product Manager Opera Dragonfly,
Consumer Product Manager Opera Core,
W3C Mobile Web Best Practices Working Group member

Consumer Product Management & Developer Relations
Opera Software ASA
Oslo, Norway

Mobile: +47 94 22 02 32
E-Mail: dstorey@opera.com
Blog: http://my.opera.com/dstorey
Received on Sunday, 18 January 2009 16:02:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:08:58 UTC