I read about a psychology study where they analysed how many people can link their own actions to effects. A large number of people made the same mistakes multiple times because they didn't connect the cause. After being told what the cause is, most changed their behaviour, but a significant portion of people still didn't "get" it and continued making the same bad inputs.
Edit: See my comment below for the Are Technica story where I read this
I think it's important to note that by using these opt-outs you're also impacting coverage to privacy-preserving alternatives for network location like BeaconDB
Funny you should mention that, Nextcloud originally forked off OwnCloud due to drama.
I think the server is working, it's basically OwnCloud Infinite Scale but rebranded. Not sure about the client apps, those might be work in progress still. I haven't really kept up with it either though
Many of the people who worked at OwnCloud Infinite Scale are now at OpenCloud due to disagreements between them and the company which purchased OwnCloud.
The FSF has an ass-backwards approach to firmware, leading to only these distros fulfilling their requirements.
Their preference for firmware is as follows:
Firmware that's open source (fair enough)
Firmware that can't be updated (i.e. devices that are flashed once at the factory)
Firmware that can be updated (CPU microcode, firmware for GPUs, SSDs, etc)
As Linux includes patching of CPU microcode on boot (to fix security vulnerabilities and bugs) the default build of Linux doesn't fulfill those requirements.
In practice many Exchange enterprise admins disable or restrict protocols other than EWS. This feature allows you to use Thunderbird anyways and will also enable calendar sync in the future, another often restricted part.
I think I'd want something between normal and hard difficulty. Normal makes most fights trivial when you hit most QTEs, while hard kills you on single QTE fails almost.
I haven't really enjoyed JRPG combat, so this mix works really well for me
You can use host_vars to set different variables per host. You'd still run the same playbook against both hosts, but each has different services activated.
Make the folder host_vars in the repo root
Make subfolders for every host with their hostname
Enable services you want by writing the variables into a yaml file for your host (any file name as long as it ends with .yml
Write an Ansible inventory for your hosts
Run the playbook with your inventory
Slightly fancier would be using group_vars instead, you can add a host to multiple groups. Then deploying the same services on a new hosts would simply be adding it to the group
I read about a psychology study where they analysed how many people can link their own actions to effects. A large number of people made the same mistakes multiple times because they didn't connect the cause. After being told what the cause is, most changed their behaviour, but a significant portion of people still didn't "get" it and continued making the same bad inputs.
Edit: See my comment below for the Are Technica story where I read this