If I worked for PayPal right now I'd be printing résumés. Stripe recently laid off 300 of their IT people. To paraphrase Petey Greene, I wouldn't trust them to wash my car.
I tried AoC out one year with the Wolfram language, which sounds insane now, but back then it was just a "seemed like the thing to do at the time" and I'm glad I did it.
LinkedIn is by far the worst offender in post previews. The doctype tag must be all lowercase. The HTML document must be well-formed (the meta tags must be in an explicit <head> block, for example). You must have OG meta tags for url, title, type, and image. The url meta tag gets visited, even if it's the same address the inspector is already looking at.
Fortunately, the post inspector helps you suss out what's missing in some cases, but c'mon, man, how much effort should I spend helping a social media site figure out how to render a preview? Once you get it right, and to quote my 13 year old: "We have arrived, father... but at what cost?"
The clock is not entirely bug-free and has been a bit of a victim of my impulse towards premature optimization. I've rewrote it once and I'm considering rewriting it again... so it's not just you. It should hopefully work properly if you reload the page.
For some reason I never seem to encounter bugs like this myself! I guess I'll have to do another rewrite of that. Was it just the menu clock? Did the clock app exhibit the same behavior?
reply