Here is a news report with video footage of one such incident (the part where the victim is decapitated is clipped from the report):
https://youtu.be/3IwhsYfnNvs
I am personally aware of quite a few speedboat related accidents, some fatal, and this is a common pattern.
The types of death that people imagine (boat sinks, boat engine dies and drifts out to sea) tend not to be killer in small boats because they mostly operate in busy waterways near shore where someone else will come help.
False negatives are more worrying. On a small speedboat, a common cause of death is that the captain falls overboard while the boat is doing a sharp turn at speed. The boat then does a 360 circle and within 10 seconds runs over the captain before anyone else in the boat can intervene.
Will these wireless keyfobs reliably cut out within 10 seconds when the boat never goes more than say 60 feet from the captain? I suspect not.
You should also design all your code to be rollbackable... But for the very rare case that a rollback won't solve the problem (eg. An outage is caused by changes outside your organisation's control), you also need to be able to do a rapid code change, recompile and push. Many companies aren't able to do this for example their release process involves multiple days worth of interlocked manual steps.
Obviously you do everything possible to stop an outage like this happening...
But when it inevitably does, you should be prepared for a full system simultaneous restart. Ie. So that no 'bad' signals or data from the old system can impact the new.
That is the sort of thing you should practice in the staging environment from time to time, just for when it might be needed. It could have taken this outage from many hours down to just many minutes.
Twitter indexing was basically real-time - you could see a tweet within a few minutes of it being made
Mastodon seems to take many days to appear, if at all. I suspect Google just scrapes the webui occasionally and doesn't use any push-based mechanism for notifications. That probably means it misses some too.
I never really saw how making the counters random helped fight bots.
Anyone who wants to know if their bot armies upvotes are counted can just choose 2000 articles, upvote a random half, then see if the half they upvoted have higher vote tallies than the half they didn't.
No amount of delay, quantizing, or adding noise will defeat that tactic. So why try at all?
I really want to see ssd manufacturers offer a decent warranty...
This drive costs $100, and will last 10 years or until 100TB has been written to it, as long as you keep it within the specified temperature/humidity/power conditions.
If it fails to do that, we will return $1000 to you.
Company can upload some prompts to OpenAI, and be given 'prompt tokens'.
Then companies client side app can run a query with '<prompt_token>[user data]<other_prompt_token>'. They may have a delegated API key which has limits applied - for example, may only use this model, must always start with this prompt.
That really reduces the privacy worries of using all these third party companies.
It's the chicken and egg problem... If you started a new card provider today, you'd need to get consumers onboard, banks onboard, merchants onboard, and every card machine in the world replaced to accept your new card type.
The closest we get to that is loyalty cards and gift cards that only work in one shop. Some of those have managed to be compatible with a few shops, but nowhere near what would be needed for a consumer to consider it a replacement for visa.
For non-us citizens, USD's either incur a conversation fee to another currency, or an international withdrawal fee. There is no way to get money out without paying one or other fee.
The patch causes a different root filesystem to be used. Specifically, if the kernel command line specifies a root filesystem that must be used, then that one will always be mounted, even if other devices are available.