Do you have a website?

We do, but it's very minimal for now: https://dronesforwork.nl/

We'll be changing our company name in a few weeks, followed by the launch of a new website which should have a lot more information than the current one.

Sources for that?

Where is that place and why isn't anyone doing anything about it?

Not sure what's exactly going on, but I am served this plain PHP file instead of the actual content. https://hastebin.com/yakojujoka.xml

There wasn't a good, reasonable way to buy cheap roaming-data, at least not with my German contract. 150MB of roaming in the EU was 5€ with the purchase process (via SMS) being bugged and failing 50% of the time, sometimes charging my credit card instantly while delivering the "You can use your roaming data now" message days later when I was back home, customer support could not help because they "do not suggest that the data is available instantly". n=1, obviously.

Why does he sue two years after being fired? Sounds a bit fishy.

In the other hand, this sounds like something they might actually have done.

Why does this sound like something they might actually have done? In what way would (managers at) spaceX be benefited by not properly conducting tests and repairs?

Elon Musk has a high standard. And requires the best. I think thats how he has become big. Also read this:

https://www.quora.com/What-is-it-like-to-work-with-Elon-Musk

"Working with him isn’t a comfortable experience, he is never satisfied with himself so he is never really satisfied with anyone around him. He pushes himself harder and harder and he pushes others around him the exact same way. The challenge is that he is a machine and the rest of us aren’t. So if you work for Elon you have to accept the discomfort. But in that discomfort is the kind of growth you can’t get anywhere else, and worth every ounce of blood and sweat."

That incident (and SpaceX's history) has the makings of a movie.

It would require extensive support from browser vendors, so if google got behind a proposal like that, it could probably be pulled off.

Most servers would likely use both protocols for quite a long time before one could be discarded.

I feel like the biggest problem would be all the ISP's DNS servers, ISPs are notorious for breaking all kinds of stuff and this would probably be just another thing they break.

That's exactly the reason why I, along with my circle of friends, moved to Snapchat.

Anecdote, but upwards of 80% of people younger than 25 I interact with in Germany use snapchat.

Not sure about 2 - What are your arguments for this?

If the status page relies on getting updated information from the service, it may not even notice when the whole thing just crashes and goes down in flames. Attempting to do some predefined calls to the service to evaluate whether it is working correctly appears like a better solution?

Yea I was wondering about that comment too. I mean you can do both. Your status page should be static, updated by a service which both polls and accepts information from your services. You ideally want to go yellow if one of the two fails.

But yes, in general, the status page and status services should be entirely on their own independent infrastructure; and in a different data centre. A number of providers offer independent status page services. If your entire company runs off Digital Ocean, your status page/services should probably be running on Linode or AWS or whatever.