Live data from Hacker News

Store.js - cross browser local storage without using cookies or flash

github.com

61–63 of 63 posts

Re: Store.js - cross browser local storage without using cookies or flash

#61
post #60

Earlier quoted context omitted.

Then disable it by default, but don't leave it out altogether.

Can you give me an example of when it would ever be appropriate to turn something like that on?

whenever the user wants it

Re: Store.js - cross browser local storage without using cookies or flash

#62

Earlier quoted context omitted.

I'm completely unconvinced that cross-domain local storage is even remotely a good idea. I can't think of any data I'd want to store in a clientside database that I would want other sites to be able to see/modify. So, all hopes for cross-domain user tracking are still doomed. sigh Um, this is a good thing. I don't want the sites I visit to be communicating my use patterns to each other.

Actually, it wasn't a sarcasm. I do need cross-domain user tracking for perfectly legitmate reasons. Many of my users do A/B test where control is www.example.com and variation is www.example.org (for example) and the goal page lies on www.shoppingcart.com -- currently there is NO way I can track a user across these three domains (no, third party cookies don't work properly on Safari and Opera). I am left to experime…

If you don't need 100% reach, have a look at xauth source: http://github.com/xauth/xauth

They use a central domain and window.postMessage to make a secure but shared storage.

Re: Store.js - cross browser local storage without using cookies or flash

#63
post #16

Earlier quoted context omitted.

"Hidden?" Give IE some respect...its rendering may have been crap, but it had plenty of features like this for building robust web applications years before the cool kids realized that might be a good idea.

Yes, that's exactly what I was trying to get at, evidently unsuccessfully. For all of IE's failings, it does seem to have been first to support an awful lot of scripting features. They've always been documented , but hardly anyone seems to know about them until the other browsers popularise them, and even then IE's implementation seems to be forgotten, presumably because APIs are nonstandard and the docs use differen…

I wanted to point out the significant difference between "hidden" and "ignored". There was nothing hidden about these IE features. People just chose to ignore them. And of course they were nonstandard, just like most other new technology.
Post reply on HN