I think this is just an artifact of how the code is representing "present". It's clear there's no actual content on this page, looks like it was recently created from a template in anticipation of posting a biography.
The end date for his term is marked as "present", so the text at the bottom is rendering it as the UTC time at page load. In this case, it will be a few minutes behind as the page gets cached at CDN edge nodes, and will be slightly different for everyone. When you see it change, that's the cache TTL expiring.
I'm a software developer. You don't publish pages like that until they are ready for public viewing. A "draft" page should stay in a draft state and NOT get published. And besides, the fact that date was updated several times, is odd.
I think this is just an artifact of how the code is representing "present". It's clear there's no actual content on this page, looks like it was recently created from a template in anticipation of posting a biography.
The end date for his term is marked as "present", so the text at the bottom is rendering it as the UTC time at page load. In this case, it will be a few minutes behind as the page gets cached at CDN edge nodes, and will be slightly different for everyone. When you see it change, that's the cache TTL expiring.
Nothing to see here...
I'm a software developer. You don't publish pages like that until they are ready for public viewing. A "draft" page should stay in a draft state and NOT get published. And besides, the fact that date was updated several times, is odd.
So someone f'ed up. The date changing is not odd. That would be expected behavior due to CDN caches.
It would be a hardcoded UTC timestamp that would be independent of CDN location.