koollman

the other half

Are curses part of the enchantments ? I think I noticed those

people use weird and rare bacteria bottles sold on amazon as tatoo ink

That would be incorrect.

IANAL, but cloud act purpose is to allow the usa government to ask data from USA-based or USA-related services providers, for offsense/crimes.

It does not allow service providers to do anything else with that data.

Not theft indeed, but copy/use of data without consent. How are they worse:

They are now at risk if there is a data leak in the USA. There are higher fines for data leaks in Europe, so they aren't as well protected as before

It is easier to sell crap in markets with no customer protection or safety rules.

It is cheaper to make stuff without regulations or worker rights.

But, well, that's not really the point you want to make, is it ? :)

I do think some exemples of "stuff that can happen to you" are useful (without becoming a support site, of course).

It may help others consider what they should be doing to not let this happen to them or imagine what they could do before it happens to avoid being stuck.

Do read contracts, service terms and SLA/guarantees (and other customer experiences, if available)

You don't have to run it a entire duplicate of your current infrastructure, just plan for it to happen (depending on impact to your business). Then it means you can think about doing it after a few days of downtime, maybe earlier depending on difficulty/impact.

But, yes, you do have to plan to run it elsewhere and consider wether various features may make it harder for you to move on. vendor lock-in is a known business risk

Well, it is about things to prepare before being in this situation, I acknowledged already that it was unhelpful now, since it is too late. It is advice for other business deciders looking at this, or for this one for changes to implement in the future.

Sometimes the plan is "well, this business had a good run, now it is over".

Sometimes it can be as cheap as "well, here's the documentation to run all my stuff elsewhere, starting from my external backups"

Depends on how much money you lose from a failure and how likely the failure is. As an additional point, you may not plan for s3 going down, but even a price hike on egress traffic may put a business in trouble if trying to move without already having external backups. So, as often, you have to do some cost/risk analysis. But having backups not controlled by your main provider is often considered a good idea.

Technical problems, human error, cost changes, various disagreements between provider and customer, can all be made easier if you have a plan B rather than being stuck with a single provider or solution

external/independant backups are a thing. They would be part of a disaster recovery plan (and you should test the restore process and result from time to time, else they might be worthless when you actually need them).

I understand this is not helpful right now, but there are best practices and many ways to plan for this kind of stuff for good reasons. Some things can and will go wrong, and sometimes that may cost your business a lot, which means you have to anticipate (or accept) the possible costs and risks.

It is part of the job

if your business depends on someone else's entirely to work, you have to factor that into your risks and maybe plan for it.

No alternatives, no disaster recovery plan, nothing you could try for more than a week with some other provider ?

sorbs sarved me well for many, many years. RIP :/

would need some benchmark against indexed data

"$40k became 'untraceable' while being reported as lost" /s

the revolution option has expired and cannot be enabled anynmore

I've used bluetooth on linux, windows and macos. It mostly works (definitely nothing as bad as "never seen BT work at all on windows". There are so many keyboards, mouse and audio devices working pretty decently that I wonder what you are using and what is your use case.

My main gripes with it are:

- (lack of) selection of which device I end up connecting to (typically previous used device, unless not, and if you don't want that and it connects anyway, it is annoying to go and disconnect it)

- shitty audio quality in most implementations if you want to use microphone at the same time as listening to audio

- lack of support for actual multi-device connectivity (not 'this headset can switch between two "connected" sources, only playing from one' but 'this device can mix those two audio sources and play the result', for example. Which shouldn't be much more expensive than the worst case of adding another entire BT circuit + mixer)

I guess the kind of web centralized on google/amazon/azure/facebook, and a few others (cloudflare comes to mind)

no, it is not.

opt-in. Pay them for it. And have a culture of fixing stuff and spending enough before shit happens, so that on-call is rare and problems don't repeat too often

You seem to manage fine. I do think most projects do not need AWS, and at work we run most of our infrastructure on our own servers (colo, we rent racks and buy servers).

Remember to consider more annoying points that can often become hidden costs, or hidden risks: - backups (and more importantly, restores :) ) - maintenance and security (you are in charge of the lower levels too) - decent authentication, authorization, and accounting (AAA) - SLA, both 'in theory' (what does the contract with your provider say) and 'in practice' (how much would an interruption could cost you and what happens if the provider does not respect SLA at all) - how do you handle outages (ideally you want to have a plan to know what to do when the obvious things go wrong. Then for the non-obvious things) - how do you transfer knowledge to a potential new employee. Is there only one person that know how something works. (called 'bus factor')

And yes, most of those also apply if you use AWS, but typically they would cover different parts or have different risks. And usually some associated product you can pay to manage that risk

Yeah, right, I agree with ... err... Oracle. No, wait, something's wrong...

"ethics". Well at least they are creating more examples to analyze

did they use phones to communicate too ? they should ban that. And what about their voices ?

Having worked as a contractor ... sometimes, you hope things will get better or at least tolerable, or you go on because still need to be paid because stopping may mean you get nothing (bad contracts). It's a pretty common topic for contractors.

That's a strange take on the subject of db servers and ssl usage. Most db servers shouldn't be accessible on internet, which skews the announced result a lot. And, obviously, clients and servers generally won't require ssl by default, because it would make no sense in most situations. (but at least the 'prefer' default setting is mentionned) Requiring a certificate to run the server isn't something that is likely to become the default setting for a while...

which systems would you consider "proper concurrency-safe" ?

https://www.icann.org/en/accredited-registrars?filter-letter... is a good list. I use OVH

it's from a song of flight of the conchords, called robots. https://www.youtube.com/watch?v=hUnibKe_o18