295 karma · joined May 5, 2015
I would like to know more of the implementation of this and more information on policies to protect access to my data. And I would like to know where the data is stored. I suppose I got read the manual, but maybe some info tidbits could be included in the announcement.
Plus each CalDAV client does things a little differently so it's very hard to debug, especially when most clients are black boxes. Permissions and feature and how they respond...a potentially different.
I (unfortunately) consider the custom CalDAV server I wrote to be a bit a technical achievement, even though I'd rather I didn't have to do it. But I had to do it because there's really no other good option for writing calendar services that work with native calendar applications.
A lot of 9/11 commemoration now is all done in hindsight, but like you said, in reality it was very confusing, little information, conflicting and erroneous reports, and most of the information came from TV news. Websites weren't as social or robust.
So to actually "replay" that day by getting realtime texts on your own phone throws you back to that day more than commemoration programs do IMO.
There is also a "Hindsight" perspective on the site you can choose which will notify you when Flight 11 takes off, when Cheney left to go to the bunker, etc. which gives another interesting perspective of the events.
There's something different about getting the events realtime that is just "new." We typically read summaries or view edited clips. Realtime info, over the day, is really something that hasn't been done before.
I have heard several times how actually having some competition helps companies quite often. It's not automatically the end if someone else has a similar offering.
There are a lot more timezones than there are offsets, and several timezones may have the same offset at a given point in time, but that may not be true every day of the year because they have different rules.
So the robust solution is to make all your datetimes "timezone" aware, not "offset" aware. And yes that means using the Olsen Data and yes that means more complications. But it's the only way to have accuracy for human-oriented datetimes.