As I reported in ticket #335, I was having problems with my token changing, which forced me each time to update the URL for every iCal feed and for every Quicksilver Applescript I use. For a while, I couldn’t figure out what was causing the token change, but thanks to a casual remark on http://blog.gtdtracks.com/, I have figured out the problem: changes to preferences change the feed URLs, and thus break the iCal subscriptions and Quicksilver Applescripts.

Does it have to be this way? It sure is inconvenient to have to adjust all those settings and scripts.

I’ll take a look at this and see if we can change it so that the token only changes when the password is changed (which was what I originally intended).

Craig and Bsag, I just checked in a fix to this. The token will now never be automatically updated after the initial creation of the user. I added some UI to the preferences page to give the user the ability to explicity trigger a regneration of the his/her token. As I was playing with it, this seemed to make more sense than updating when the password is changed. What do you think?

That sounds fine. I originally intended the token to change when the password did because I thought that if you suspect that your password has been compromised, your token probably has too. But this gives people the choice about when to update each, which is fine.