• 0 Posts
  • 59 Comments
Joined 2 years ago
cake
Cake day: June 28th, 2023

help-circle


  • I don’t think it’s equivalent to sovereign citizens. OP is the author of their comment and therefore has the copyrights. As the author one can license their work as all rights reserved or other permissive licenses.

    OP chooses to license their work as Creative Commons.

    They’re not forcing you to accept the license, it’s your local government that enforces copyright.

    The reason why this might work on Lemmy but not on corporate Social media is that corporate social media often have terms of service that require you to give them ownership/rights/etc. Lemmy has no such ToC.


  • It’s government reporting data. If you find a better source I say go for it. But I used that data for salary negotiations in the past successfully.

    I’m not talking about take home. I’m talking about total annual compensation including things like RSU payouts etc.

    Even if we throw out the ones you doubt there are many 300k to 400k entries with the AI researcher title. If we add annualized RSU payouts we easily hit over €500k.

    At this point t though you are free to doubt me.




  • I see your point but like I think you underestimate the skill of coders. You make sure your timeout is inclusive of JavaScript run times. Maybe set a memory limit too. Like imagine you wanted to scrape the internet. You could solve all these tarpits. Any capable coder could. Now imagine a team of 20 of the best coders money can buy each paid 500.000€. They can certainly do the same.

    Like I see the appeal of running a tar pit. But like I don’t see how they can “trap” anyone but script kiddies.






  • I like the fact that it is a solid mandatory access control system. With SELinux you are substantially more safe than without.

    For example. Let’s say you are running a compromised version of OpenSSH. Threw a XZ style back door a hacker gets in as OpenSSH (which runs as root).

    Without SELinux the system is fully owned. With SELinux the attacker can only access what OpenSSH needs to access even if they have root. They can’t just chmod files and folders wherever. That means your photos and application data are still secure. With the pre written SELinux policies this applies not just for OpenSSH but for every piece of software installed on your system. Everything is limited to the exact folders, ports, and system capabilities that it needs and no more. Even stuff like seperate websites being served under Nginx. You can have Nginx-subgroup-1 and Nginx-subgroup-2 where the applications can’t see each other even though they are being run as the Nginx user.

    I don’t trust any Linux distro without this security layer.

    It’s a little difficult to learn and master, but it’s totally worth it if you care about security.

    Redhat put out a comic about it a few years ago explaining the basics. https://people.redhat.com/duffy/selinux/selinux-coloring-book_A4-Stapled.pdf