jrk's dashboard

I think the right generalization of the existing syntax here is to have "by <date>" be orthogonal to the existing context to implicitly specify @todo and set a due date. However, I think the existing reminder date mechanism should still work in such a message so you could be reminded at any time you want, independent of the actual due date.

e.g. "Remind me Tuesday to do X by 9pm Saturday"

But yes, I have definitely wanted something like this for similar reasons.

The obvious advantage is that it makes Sandy todos richer by nature, since they include a meaningful due date independent of the current reminder setting, rather than having to view Sandy items as more purely timed reminders, as I usually have to use them currently. As such:

* Viewing a list of upcoming items sorted by date would give a more meaningful ordering (by real due date, not reminder-date-that-happens-to-be-due-date-because-of-how-the-email-system-works)
* Future updates to e.g. snooze an item would leave the item with a still-meaningful primary/due date, rather than an old date (the time of the original reminder) that slips into the past as the item is pushed forward. Currently, this makes my list a little jumbled and disorganized when I go to review it by date.</date>

Scratch that, as mentioned elsewhere on here, Google Calendar can't subscribe to authenticated feeds.

This problem is still happening in 10.5.1, and it definitely seems to have to do with the "@" in the username. iCal will download the ics once on calendar creation, but subsequently tries to encode the username into the URL of the subscription, making it webcal://user%40domain.com@iwantsandy.com/list.ics, and at this point it fails to authenticate and produces the errors describe above.

The (ridiculous) workaround I am now trying is to subscribe to the Sandy feed in Gcal and then export a share from there to subscribe in iCal.

Lame.