• 17 Posts
  • 324 Comments
Joined 4 years ago
cake
Cake day: May 30th, 2021

help-circle
  • Welcome to the deep rabbit hole :-) how much do you know about how computers work? In general, you’re going to need to understand some basic networking and general Linux administration, but if you already have a grasp on that then I’d say you just need to start small (simple service, aim to have a resilience goal with backups and restoration) and other metrics that motivates you. Perhaps you want to learn something new with every service you host? You decide, this is your hobby :-)













  • There are various obstacles to “just forking” a project; it requires times to understand the frameworks / libraries used in the project, understand the code and its different parts and last but not least, have a interest to invest that time and energy (most often, that time could be spent developing your own solution that would fit your usecase better).

    As for the stage I was referring to, both the theories of enshittification and rot-economy see software and services going through stages to attract new users, before going in for the profit maximizing.







  • I’ve tried different approaches with fail2ban, crowdsec, VPNs, etc. What I settled on is to divide the data of my services in two categories: confidential and “I can live with it leaking”.

    The ones that host confidential data is behind a VPN and has some basic monitoring on them.

    The ones that are out in the public are behind a WAF from cloudflare with pretty restrictive rules.

    Yes, cloudflare suck etc., but the value of stopping potential attacks before they reach your services is hard to match.

    Just keep in mind: you need layers of different security measures to protect your services (such as backups, control of network traffic, monitoring and detection, and so on).