Tag Ralph!

Nicht "gurken", "gurke". :)

Only German speakers make that mistake.

That's odd that you mention it shouldn't work in IE. It does! Maybe this is because the cookies are set and retrieved inside the gadget javascript and are not sent to any 3rd party website? The module is loaded locally on the google page, so shouldn't IE and Safari think that it's just the browser or google setting and retrieving cookies? All they see is a page of code retrieved from the ig website, right? How do they know where the gadgets are coming from?

Let me also clarify that I am only setting these cookies as a backup. Every time I use prefs.set(), I also store a cookie with the same information, because prefs.set() often doesn't work and loses info. Both instances of the data have a time stamp, and I only use the cookie data in the event that the prefs time stamp is older than the cookie time stamp, and then it tries again to upload it. That way, the module loses a LOT less information.

As a suggestion, maybe in the future (WAY down the line, when you guys are actually bored ;) the prefs.set() and prefs.get...() functions can do this automatically. It would certainly make ig much more seamless! Think of all those times you add a module or rearrange everything and when you come back, it's exactly like you didn't do anything.. Very confusing to people who haven't thought about what's going on in the background. Looks buggy, even though it's just slow internet. Some simple cookie code like my hack job fixes most of this behavior.

To stop relying on the MODULE_ID, looks like I'm going to have to make a hidden userpref with a unique id that's static. How to make a unique ID... Get a timestamp + __MODULE_ID__ the first time the gadget loads?

Thanks for the info! -Jack