<div dir="ltr">This of course doesn't do anything to predict the time of future updates. However, something might be done at the level of the UN to deal with future updates using special software.</div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jul 11, 2015 at 5:03 PM, Zoidsoft <span dir="ltr"><<a href="mailto:zoidsoft@gmail.com" target="_blank">zoidsoft@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I've brought this up before, but I think it might be time to try to automate updates by taking user data from PC's, iPhone's etc. Some people misunderstood my suggestion before, but I'm old enough to remember a time before the internet, cell phones and when there was no such thing as color TV. We used to set these gadgets manually. To make this more clear, we should be taking input from users as to what time it is in each region and then analyze this data statistically to see if the deviation in each region is enough to warrant a change in the database. Where I wasn't clear about last time is that one would have to differentiate between data set by the database and data set by individual users. A dialog should come up on occasion to ask if the time displayed is correct for the location of the user. Corrections can be done using iteration until a certain accuracy level is reached (not all devices will be correct).<br><br>I've considered that such power might be abused by trolls, but given that most users keep their clocks updated and will negate incorrect times, trolls in the minority would just be overridden. It's an idea in the early stages but if hashed out more completely, it can potentially save a lot of trouble.</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jul 11, 2015 at 4:18 PM, Peter Ilieve <span dir="ltr"><<a href="mailto:peter@aldie.co.uk" target="_blank">peter@aldie.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 11 Jul 2015, at 20:42, Deborah Goldsmith <<a href="mailto:goldsmit@apple.com" target="_blank">goldsmit@apple.com</a>> wrote:<br>
><br>
> Meanwhile, the current situation is what it is, and we need to get tz updates to customers as quickly as we can. I wouldn’t want to see IANA rush data out before it’s vetted, or if further revisions seem likely, but neither do I want to see IANA sit on the data if it’s unlikely to change. IANA should not be making assumptions about how much time users of the tz database “ought to” need to get it to their customers.<br>
<br>
</span>I don’t think it is IANA that is sitting, or rushing, or making assumptions.<br>
My understanding is that IANA just hosts the mailing list and the data.<br>
The tz project is very much a volunteer effort. Please don’t make it seem<br>
more official than it is.<br>
<br>
I agree with Guy Harris on this. If Apple can distribute the digital camera<br>
raw updates more quickly/frequently than OS updates then it ought to be<br>
possible to do something similar for tz updates. I’m not knocking Apple<br>
here, I’m a happy user of their stuff.<br>
<br>
Even if this was an official IANA thing the problem would remain.<br>
The government of Elbonia is still going to decide to fiddle with<br>
their clocks next week even if IANA tells them they shouldn’t.<br>
<span><font color="#888888"><br>
<br>
Peter Ilieve<br>
<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>