Isn't this something that you should keep in mind for all services? After all they are basically applications you have no code for, running in computers that yo

Isn't this something that you should keep in mind for all services? After all they are basically applications you have no code for, running in computers that you do not control, funded by means you individually cannot affect and owned by companies/businesses making decisions you have no say over. Any element of control you cede to others can be used in ways you may not like or want. So if you want to ensure something will continue to exist for as long as you want it, the only way to do it is to have control over that something and either control all of its dependencies or rely only on dependencies that are widely available commodities that you work with through as many open standards as possible. For example, for web-based services, if you don't want something to go away (or be abused), then your best bet is to run a fully open source implementation of that version on a VPS (VPSes are on computers owned by others, but they are cheap commodities that you can easily replace, replicate and, if necessary, move to dedicated servers or your own machines). Personally i'd also only use simple applications with little to no (preferably no) external dependencies in case i need to pick up the development myself or make modifications. (of course having said that, i generally avoid web-based applications altogether and instead opt for desktop-based solutions whenever possible - one major reason being control)