Should be possible to disable/uninstall node-squirrel functionality and any other third-party services

What's your motivation for this? Are you looking to reduce the overhead of running the module? Do you want to be able to prevent some admins from creating these kinds of destinations?

I also think NodeSquirrel should be an optional sub-module like it was before simply because this is advertisement for a third-party paid service. The free version can only be used a little for testing. I understand they are paying for the latest developments of Backup & Migrate and we can thank them for that but there are many modules paid for by commercial companies without built-in ads like that. I don't see why this module should be an exception in the Drupal universe. Also, I might add that, in my humble opinion, aggressive marketing like that can allienate potential customers instead of driving them to you... The current last paragraph in the module description should be advertisement enough.

My 2 cents.

By the way, thank you very much for a great and an essential module!

Hi LeDucDuBleuet and Pere,

I struggled with this issue myself. I wanted to make NodeSquirrel and Backup and Migrate as easy to use and accessible as possible and building it in removes a significant barrier to entry. On the other hand I did not want to give the impression that I was selling out my module or turning it into a revenue stream at the expense of the module's users. Backup and Migrate is and will always be a labor of love and something I contribute to to help the community which has helped me so much. The addition of the paid service might be a step too far for the Drupal community but I hope not.

For what it's worth there is no us and them here. I'm the sole maintainer of Backup and Migrate and I'm also the creator of NodeSquirrel. There is no third party paying money to get an ad into the module. Not sure of that makes any difference but I figured it would be best to be clear.

I welcome this debate and would love to hear people's opinions on it as there isn't a whole lot of precedent in the Drupal community for this sort of thing.

Thanks
Ronan

I don't think my boss and my admins would be happy to know there is a module that tries to send our data to 3rd party server. That's why I think it should be a submodule.

@Mołot

Just to be clear. The module makes NO attempt to send any data to our servers until you sign up for an account and activate your secret key on your site. It works exactly the same way that ftp and s3 do.

@ronan just to be equally clear - security audits to check if what you just said is still true with each version takes time, and time is money. And ftp is easy enough to monitor. For S3 buckets - yea, I think they should be separated, too, for similar reasons squirrel should be.

NodeSquirrel is built in to 7.x-3.x, but it is not a part of 8.x-4.x going forward.