How does this 'undermine trust'? If you're basing your scheduling based exactly on that clock expecting the exact time in London, then you are doing something wrong.
It's on the BBC and so people expect it to be accurate.
For example, I imagine a lot of people aren't sure if/when the clocks change (daylights saving time). They check on the BBC, see that their computer time is "accurate" and assume the clocks haven't changed.
As another example, I often google "time" to check to see if my clock is accurate. If that just echoed back my local time I would feel like that was a breach of trust
Often when we switch from GMT to BST (one hour ahead) I have to Google the time in the UK (because of Apple's trouble in the past with daylight savings, I can't trust my phone).
It would be reasonable to expect someone to go to the BBC homepage and see what the current time is after the daylight savings switch, and wrong to find the time was incorrect due to their PC not being configured correctly.
Comments
How does this 'undermine trust'? If you're basing your scheduling based exactly on that clock expecting the exact time in London, then you are doing something wrong.
It's on the BBC and so people expect it to be accurate.
For example, I imagine a lot of people aren't sure if/when the clocks change (daylights saving time). They check on the BBC, see that their computer time is "accurate" and assume the clocks haven't changed.
As another example, I often google "time" to check to see if my clock is accurate. If that just echoed back my local time I would feel like that was a breach of trust
Often when we switch from GMT to BST (one hour ahead) I have to Google the time in the UK (because of Apple's trouble in the past with daylight savings, I can't trust my phone).
It would be reasonable to expect someone to go to the BBC homepage and see what the current time is after the daylight savings switch, and wrong to find the time was incorrect due to their PC not being configured correctly.
Ah, that's a good point actually