While I don't doubt they have a way of getting permission to access that data, I don't think they will put in the effort unless you're a relally big fish.

Neat. Didn't have a single request go through for 2 hours. Guess they need to improve their metrics before the IPO...

It's not so odd that the Chinese choose to use their domestic payment system over a US one. You probably needed a government ID to get your credit/debit card too (at least when you opened your bank account).

I'm not saying the Chinese surveillance system isn't horrible, but the western ones are catching up quickly with the adoption of Flock cameras everywhere and Palantir analyzing every bit of digital footprint you leave. Is there anyone who think there isn't a non-negliable risk that people will walk around with a "jew star" marking in the US in the coming 5-10 years?

https://www.scaleway.com/en/transactional-email-tem/

[EDIT] Found the answer from the OP:

> To be honest I implemented Lettermint before I migrated to Scaleway, so I didn't even look at TEM

Are Americans not embarrassed by the way these tech bros operate? As a European it’s obvious that the US gone from an allied to an enemy. I would feel like a traitor if I picked US tech these days.

I will report OpenAI to the data protection agency in my country and I encourage others to do the same. They can not blame Mixpanel when they sprinkle others personal information around like this. NOT OK.

Cloudflare builds a global scale system, not an iphone app. Please act like it.

But at the same time, what value do they add if they:

* Took down the the customers sites due to their bug.

* Never protected against an attack that our infra could not have handled by itself.

* Don't think that they will be able to handle the "next big ddos" attack.

It's just an extra layer of complexity for us. I'm sure there are attacks that could help our customers with, that's why we're using them in the first place. But until the customers are hit with multiple ddos attacks that we can not handle ourself then it's just not worth it.

How can you write the proxy without handling the config containing more than the maximum features limit you set yourself?

How can the database export query not have a limit set if there is a hard limit on number of features?

Why do they do non-critical changes in production before testing in a stage environment?

Why did they think this was a cyberattack and only after two hours realize it was the config file?

Why are they that afraid of a botnet? Does not leave me confident that they will handle the next Aisuru attack.

I'm migrating my customers off Cloudflare. I don't think they can swallow the next botnet attacks and everyone on Cloudflare go down with the ship, so it will be safer to not be behind Cloudflare when it hits.

Best on-call I’ve had.

Looks like they’re doing that.

It makes no sense to have the dot at the end of an anonymous named function.

If it's a false positive they just resolve it without it affecting SLA and if it's a real problem then us customers wouldn't have to debug our own stack for 2 hours before Microsoft informs us that they are the problem.

EDIT: Wonder how many man-years of extra debugging work their non-working status page have caused the customers.