Running backups from a plugin is inherently very load intensive as it's just not an efficient way to do it. We do everything we can to help the performance, but it won't always be a good fit for everyone. Usually the tradeoff is acceptable for most people, and the average site is on the smaller side for db and files so are not such a problem. We are working on a new incremental backups feature, which should help substantially with performance, though it will still be some hit. Look for that in the coming months. Meanwhile you can either try to spread out their schedules as much as possible across all the sites on a server, or use a usually much more efficient server side backup process.

I think I kindof understand what you are saying. It is a bit of tangled mess right now as per what is handled on hub side and what on plugin side. Man...

Fix is in for next release.

Sorry for your trouble! This is fixed in 4.5.1, though as said it's very important you update PHP, anything less than 5.6 is no longer supported and insecure. It's like running Windows 95!

The only way the Hub can change to HTTPs is if the website is loaded over https. Maybe a self-signed cert is being used?

If you are going to use https you should force https with a 301 redirect. Your host can do this or maybe a ssl plugin.

Actually strike that, it appears you can make a global locale glossary! I made one for French https://premium.wpmudev.org/translate/languages/fr/defau...

Good suggestions! We do support Glossaries, however the way GlotPress is designed glossaries are per project+language, one glossary can't be shared be...

Our implementation uses Basic Auth, which already has standard support from Composer itself: https://getcomposer.org/doc/articles/http-basic-authentic...

As said if you know userids ahead of time you can just preset it in config file. Or if not using config, simply deactivating and reactivating will cha...