[tor-talk] Should DOM storage really be enabled by default in TorBrowser?

[Aymeric Vitte]

The problem will be that sites such as Mega will not work any longer 
with TBB but it's not logical to forbid indexedDB and allow localStorage 
(and sites such as Mega should better use indexedDB rather than 
localStorage)

Le 19/06/2014 18:55, Aymeric Vitte a écrit :
> That's exactly what I pointed out in my follow-up email regarding yt 
> streaming.
>
> Given that there are no options to disable it or ask for permission in 
> FF, given that FF behaviour is unclear regarding how it is managed 
> (for example blocking 'offline storage' by clicking on the icon on the 
> left of the url + more information/permissions seems to have no 
> effect) and given that it is used by many sites to store cookie-like 
> stuff, I really think it should be disabled.
>
> I would disable the cache too since it can give some information that 
> you already visited the place and when.
>
> Le 19/06/2014 18:15, Joe Btfsplk a écrit :
>> Curious: Should DOM storage really be enabled by default in Tor 
>> Browser 3.6.x, when other forms of disk storage are disabled?
>>
>> If so, why is that?
>

-- 
Peersm : http://www.peersm.com
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms