3 ms·
This remind me of when the BBC had to remove the clock from their Internet homepage. This was because it just used the local time on the user's machine, and so
by NeoTar 3y ago
This remind me of when the BBC had to remove the clock from their Internet homepage. This was because it just used the local time on the user's machine, and so was considered to be inaccurate (and people would assume the BBC were authoritative!)
What surprised me looking up the story is that it happened surprisingly recently in 2013. I would have assumed that by that time the average person were sufficiently internet savvy to recognize that the clock was not remotely generated somehow. I wonder if the same conclusion would be reached today, or if BBC developers would instead sync the time between the server and website.
https://www.independent.co.uk/news/media/online/bbc-forced-to-remove-misleading-clock-from-its-homepage-8644046.html https://www.independent.co.uk/news/media/online/bbc-forced-t...
- eloisant 3y agoI don't see how the average person could know it didn't came from the servers. Even for a developer it would require looking at the JS code or the network calls. Anyway, what's the point of embedding a clock in a website? Everyone has a clock on their desktop computer to start with.
- Merad 3y ago> I would have assumed that by that time the average person were sufficiently internet savvy to recognize that the clock was not remotely generated somehow. IME the average person really has no intuition for how the internet and websites work. I don't think the thought process goes much beyond "BBC is showing me the time" -> "obviously they are showing me the correct time according to the BBC."