Reminds me of race conditions in programming.
1 in 15 times the bug happens and you can’t figure it out, but if 2 asynchronous events happen to happen within 10ms of each other it breaks.
Could be some super specific timing on one of the steps where a discrepancy of a short time doesn’t seem meaningful but is
Wires that wouldn’t electrocute us?
Is it because we would have resistance and it wouldn’t so it’d ignore us?
I think part of the problem was websites needing to work on other browsers too. When it’s your own engine if a website doesn’t test against it, the website might be broken. So then the websites say they don’t support such and such browser.
Less of an issue when its all chromium.
We run into problems on safari a lot like this since my partner keeps using it on her Mac.
Ya, if the news organizations are using open graph and that’s all Google and Facebook and whoever are using that’s stupid.
Show our preview so people will click the link! OH NO our preview is too good and people aren’t clicking the link! Government make them pay us!
Is it actually a provided preview, or a preview they are generating.
I know part of the legit problem is when a website summarizes something and then people don’t click on the link, which reduces ad revenue.
But maybe there’s a provided summary (which should be fine) and the other way it gets summarized (which could arguably be deemed bad)
But making them pay to just link with is batshit insane.
Well the good thing is they were able to reproduce it themselves so they won’t drive themselves fully crazy trying to narrow that down, assuming not a scam.
I wonder how much you could automate that all to remove as much human factor as possible and be down to exact times if needed.