From implementation standpoint, I frequently use Google Auth and a bunch of their APIs. At least for Python, I can confidently say that they are not at all painful. Yes, there is fragmentation between different oAuth providers but unless you are writing oAuth library yourself, you may not need to face these problems ever. Fyi, I am not using any oAuth lib but then I only use google auth for my app, not fb or twitter.

Life lesson: Take care of your health. Tech lesson: Encrypt everything.

Even in this day and age, encrypting everything is seen as some kind of hacker's paranoia.

If a new OS install instead asked "In the event of physical theft, what would you like to grant thieves access to?" with checkboxes for "My email account", "My social media accounts", "My documents and photos", etc, would people feel it was paranoid not to tick all the boxes?

that is in a different table which was not compromised.

OK, I want to make sure though. How can these creds be regenerated? What happens if we had leaked them accidentally, there seems no way to regen them?

Please have a look at https://www.browserstack.com/automate/rest-api#rest-api-key

Thanks (can't reply direct to the reply for some reason)

There's some kind of algorithm that prevents two users ping ponging comments too quickly. Not sure exactly how it works, but I've had experienced that before.

It is Linux. Let systemd live and if you don't like it, switch to upstart. No one is stopping you.

Actually it's not like this. On FOSS when there is no manpower distros need to make a choice: supporting the software themselves or pick the maintained solution. So when upstart developed slowed down, by other words Canonical pulled resources from it, it was when they made the decision to switch to systemd.

Also the cost of maintain it and adapt applications who are tied to systemd is much more larger than adopting syetemd.

The only viable solution i'm seeing right now is: Use a mainstream distro with systemd or switch to other one which maintains their own init system like Slackware or Gentoo.

It's (slowly) becoming impossible.

This is the "TempleOS impulse". The feeling of disgust with byzantine complexity, driving an impulse to start clean and chase the money changers out of the temple

Upvoted for mentioning TempleOS, I have never been more frightened when reading about OSs.

ownCloud would be perfect for this case. Users can share files, have disk quotas to avoid misuse, share contacts and calendar events. If you want you can user ownCloud user management or integrate with AD or OpenLDAP. Both community and commercial support is also available.

To be honest, I won't say that you can run a lot of users on it and expect amazing performance. It is mostly for evaluation and hobby usage. I suppose that it would be good for 2-3 users. I am thinking of removing certain extra things that are running on it and create a lean image. Hopefully it'll improve the performance.

I understand, sometimes it can be tricky. I would recommend using the stable build rather than master snapshot but then it is my personal preference.

You can go for an ebook, if price is a concern.

I have encountered the first situation you mentioned a few times. Thanks for the pointer, I should have mentioned it.

nope. It is a 30 minute trial. :)

You mean normally?

Yes. You can just sign up for a 30 minute trial anytime with your email id.