How @digitalocean just killed our company @raisupcom

twitter.com/w3Nicolas/status/1

Thread intéressant sur une entreprise dont tous les serveurs ont été bloqués par DO qui révèle une possibilité à laquelle je n'avais pas pensé : qu'un hébergeur peut bloquer toute une infra et tuer un business rapidement. D'où encore une fois le besoin de rapatrier ses données sur un support qu'on contrôle régulièrement.

@carlchenet @digitalocean This is unpleasant. I hope it went well in the end.

It would be very easy to laugh at the DO client for doing silly things like not having local backups that nobody can take away from them. But running a startup requires paying attention to so many details and aspects that it is easy, indeed likely, that one overlooks at least one, and that's all it takes for a disaster.

So I don't laugh, or say they should've been more careful, and I hope nobody else does, either.

Follow

@liw @carlchenet @digitalocean striking to me is the "drop dead end of thread" (rephrased in corp speak). I have seen similar posted before and there seems to be a perception that limits legal liability vs explaining and providing a way to followup

@joeyh @liw @carlchenet moisey jumped in on the thread and intervened, but unless there's something to the story we don't know, it probably shouldn't require a DO founder to exercise special authority to resolve something like this.

that said, i wonder how many similar stories can be told about larger providers with even less perceived obligation / incentive to reverse a decision. this certainly isn't the only desperate appeal to social media i've seen...

Sign in to participate in the conversation
Octodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!