What’s wrong with Ubuntu and RH? Is it because of the snaps / source code debacle? Both of those had solid business cases to them and while I dislike the outcome, I do understand why they made that choice and most importantly - I still approximate what each company does for FOSS.
My two examples are of OS SaaS that got their plug pulled before they got to that stage. See skiff.com and omnivore.
Awesome <3
If you need feedback, testing etc. on this feature, I’m happy to help. Just pm me and I’ll give you my github account.
This is really cool. Happy that you included the comments, as I find them often quite insightful. Look forward to spin this up and try it.
Edit: I know this is really hard to design and implement, but is it possible to bring in certain amount of child comments as-well? E.g., past a certain vote threshold or only X child comments deep. This might be a requirement that want to “move” the social media platform into the RSS feeder, but I want to entertain the idea.
There are so many monitoring tools with various degrees of complicated setup / configuration or the amount of information you get. And honestly, I’ve looked into various tools: checkmk, monit, Prometheus… And realised that I rarely look into that information anyway. Of all “fancy” tools, I liked the ease of Netdata to set up and the amount of information that you get. However, beware that their in the process to make their free / homelad offering worse. I’ve been eyeing beszel and don’t forget CLI based tools that are avaible such as atop, btop, htop or glances.
If you want to delve deeper into the rabbit hole of monitoring, I can recommend you to read this article below: https://matduggan.com/were-all-doing-metrics-wrong/
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).
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.