When choosing any service provider, a crucial question is, "What happens if something goes wrong?" When you're choosing a hosting provider, we like to dig a bit deeper, and ask what risks are likely to be an issue for you?

Here are some of our questions:

[Update: a few days after I published this, Vector.im rebranded as Riot.im. It's the same project, just a new name...]

In 5,000 years, will anybody be able to read (or even access) things we put online today? Here at the dawn of the information age, we are creating the archetypes that have big implications, possibly for thousands of years. There's a bunch of recent science fiction stories that imagine various futures, written with the perspective of today's web, extrapolating where things might go as humanity evolves.

I learn best when I have a problem to solve, and with one of our D8 upgrade projects, we had a mess to clean up in the menu system.

So there are definite "gotchas" to migrating content from Drupal 6 to Drupal 8, when you take away the assumption that the ids throughout the system will remain the same.

Richard asks:

Just a question after reading an article posted here back from January 21, 2016 on Drupal 8, why Freelock.com has not moved to Drupal 8?  Just wondering if there was a particular reason we should avoid before jumping in?  Thanks.

Yesterday the Drupal security team gave a dire warning about extremely dangerous security vulnerabilities in multiple contributed modules. The fixes, and the details, would be released at 9am Pacific Time today.

Our branch strategy based on Git Flow did not survive. It was getting a bit old in the tooth, but the final blow was automation.

We have several Drupal 6 to Drupal 8 upgrade projects going on, which is particularly challenging given how quickly the Drupal Migration system is changing.

It's really a shame. Drupal Gardens has announced to its users that it's shutting down completely on August 1, and users need to move away from the service before it disappears.