pifm_guy

Although if apple didn't have Siri, then they would likely allow other voice assistants on the platform, and you'd have 'dictation by alexa' instead.

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.

Don't get yourself in that position.

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?

They didn't give permission for the internet service to launch there. But they did give overflight permission.

Remember that Loon, the USA Google balloon project, sent similar balloons around the world, including over China.

They didn't shoot our balloons down.

Ask someone local.

What's available and rules vary really widely city to city.

What makes sense financially also depends on your building construction, climate and fuel prices, which also depends a lot on location.

I just filtered for the word yeti.

I don't want a yeti hopper...

All of those things look pretty 'fixable' in the game of cat and mouse ...

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.

It's a shame this is US only.

Typically companies that do that will later release in ~10 more countries, or maybe even 50 more, and then give up.

If you live in Mozambique, the chances of ever being able to buy this are pretty much nil.

Sketch of a design to solve this:

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.