• 0 Posts
  • 19 Comments
Joined 3 years ago
cake
Cake day: September 14th, 2023

help-circle
  • Their privacy policy states the obvious, and repeats what’s in the SMTP RFC (821). I can only guess this is because of transparency. All email providers have access to that information. I would actually argue for them that they are better at letting people know which kind of data they do and don’t have access to.

    Every (email) service is bound to the law of the country they reside or operate in. Proton has part of its offerings in Switzerland, part in EU (Germany if I recall well). Swiss FADP is very close to GDPR. Also when it comes to privacy protection. Every company bound to GDPR (or FADP) has to abide to the law, and when law enforcement has a good reason to check out user data, and the judge agrees, any company has to provide evidence. Even non-EU based companies offering services in EU. With their transparency report they are providing a tool to their users to know and understand what happens to their data in a lawful manner. And I see that as a win for transparency.

    But this is just my opinion, and it is ok to not agree with how I see the world.






  • I would copy the existing system onto a new system:

    1. Update system to the latest packages
    2. Create a new base system using the same distro
    3. Check which packages are not on the new system, add them to your playbook
    4. Install packages on new system
    5. This will take some time. Run a find of all files and pass them to md5sum or sha512sum to get a list of files with their checksum. Compare the list from the old system to the new system.
    6. Update your playbook with these findings. Template is probably the way to go, Lineinfile might be good as well, use copy if nothimg else works.
    7. Check firewall settings and update your playbook.

    Anyhow this will take some iterations, but while you have a copy of your ‘production’ system, you can test on your ‘test’ machine until you have the same functionality.














  • It is clear the author of the article hasn’t taken the effort to learn the rules and apply them.

    I originally chose (3 years ago) DnD5e over PF2e for my newest campaign because of simplicity: I played DnD ever since I could walk, and PF2e seemed to have too much and too complex rules.

    Big Mistake

    I needed to come up with my own solutions to shortcomings of the DnD5e system, as it promotes to be rule light.

    My session prep turned into nightmares, as it took more time tinkering with the rules than it did building the campaign.

    Enter OGL relicense fiasco

    Our group decided to leave DnD5e behind and venture into PF2e mid-campaign. I was flabbergasted at the maturity of the rules. There is indeed a lot of rules, but they all fit together. The rulebook has a notoriously bad index, and it is being addressed in the remaster, but the archives of Nethys website is awesome and a good complement. It tried learning the rules in record time, and my players are patient when I need to look something up mid-session, but the games are more awesome.

    I spend my preptime doing what I like best: designing the campaign, not the rules.

    I am still picking up details each session, but up until now, it is my non-professional opinion PF2e rocks and DnD5e sucks mothballs.