robinson-wall
Joined 13 years ago
Joined 13 years ago
Much as with backups - if you don't test them, they don't exist.
Everywhere I've worked has had multi-AZ infrastructure. I have never worked anywhere where the failure of an AZ has been simulated regularly, with second-order effects mapped out.
Both occasions the pieces weren't structurally important, and were small decorative elements.
It cost £20 and I was dubious about it, but it cleans better than I've ever managed by myself with a spray. Lasted about 1.5y before it stopped being effective (just moves grease around rather than picking it up) and I went and bought another one.
Once you're storing a few million objects at standard durability it's par for the course.
This sounds like a bug we're aware of where an account that goes public -> private we'll reliably purge their tweets from the public index, but if an account goes private -> public sometimes we'll not re-populate the main index correctly.
> we had one person's account whose search results still showed searchbanned tweets
This part doesn't match what I'm describing, but could be explained by the logged in account having access to private tweets in search results that logged out / other accounts do not.
These ads are deliberately designed to prey on the desperate, unfortunate or the technically illiterate.
Some of them probably know exactly what they're doing and I have no sympathy, but some of them probably fall into the same category as people falling for Authorised Push Payment fraud.
It's just more expensive and another thing to maintain, and still doesn't account for _all_ failure modes (what if you sync really frequently and a bad change was made deleting all accounts?)
In my case I had a country name accidentally put in a region field, but it didn't look out of place because field labels are missing when filled in. Frustratingly, your contact card with that address will show a map preview that when tapped opens maps with a pin in the right place, so there's clearly some logic to "fix" incorrect addresses somewhere.
There were two - I pointed out both and they didn't seem super happy about it. To this day I'm still not sure if one of them was an unintentional error.