You could easily automate this (cap,puppet,chef) if you have a lot of installs. If you genuinely don't want to test updates, you could run it on a schedule.
What it doesn't do, and can't do, is guarantee that security updates will never break your app, but they do quite a good job of isolating them, you do have to do some testing. There is possibly an argument for lts releases which receive few new features and focus on bugs, but what you're complaining about here are really the complexities of running multiple web apps/servers, not something a framework can really help with.
I don't think you have to worry about this update if you have already updated tho latest anyway (which you should have done if on 3.2.x).
At some point of course, people are going to start using data analysis of all your posts and even writing style to build up an entire history of you from all these public posts, this will happen, indeed it's already happening precisely because it is so valuable. So your curation of your online life is really the illusion of control, in fact the culture of google, like that of Facebook, leads me to believe these things will appear at the top of a google search as you fear at some point in your lifetime.
You've just described how fashion works, and how most people experience it. People who don't care so much follow the lead of those who do, so that they don't stand out from the crowd.
To be fair, any WP hosting company is going to run into issues with non-standard installs, and they're not going to be able to accommodate any setup. If you have a customised WP install, it might not work on this sort of provider, they're optimising for speed, not dealing with, and they probably don't want the headache of trying to support any plugins or modifications that you might bring to WP.
It would make sense for them to offer a dev plan with every production plan though, and let you upload your site, and serve it to a limited no of people as a testing ground. Given their 'Power Tools for Power Users' stuff on their website, they really should consider at least offering staging servers for testing.
I guess at present they're just not a good setup for developers trying to modify WP, and are instead trying to capture the market for hardened WP hosting for mostly vanilla installs.
The CoffeeScript gem is included by default in new rails installs, and some js.coffee files are created, so you'd have to explicitly remove it - most people won't bother even if they are writing most of their js without it. The following gems are included by default, which perhaps makes the usage in these apps (done in a hurry) not very surprising:
Or the admins could just reserve hellbanning for only the most persistent serious trolls. It is a useful tool but should only be used in extreme circumstances, not just for one bad comment. If it was used only once a month or every few months for persistent trolls it wouldn't be a problem.
Bad comments get voted down anyway, so there's already a mechanism for that, IMHO hellbanning should really only be used on people trying to post spam repeatedly or repetitively troll comment threads.
bundle update (if gem version is set with ~>)
You could easily automate this (cap,puppet,chef) if you have a lot of installs. If you genuinely don't want to test updates, you could run it on a schedule.
What it doesn't do, and can't do, is guarantee that security updates will never break your app, but they do quite a good job of isolating them, you do have to do some testing. There is possibly an argument for lts releases which receive few new features and focus on bugs, but what you're complaining about here are really the complexities of running multiple web apps/servers, not something a framework can really help with.
I don't think you have to worry about this update if you have already updated tho latest anyway (which you should have done if on 3.2.x).