view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
That doesn't mean we should underestimate these CVEs, or the fixes. Blindly repeating what you say can do more harm than help. Maybe you know what you are doing (even then I don't agree with you) but your statements can do harm to people that don't (entirely). They skip on security patches, because they heard that its pointless and maybe 99.9 percent people will be okay, but how many won't?
As I said, not every "attacker" is intentional skilled hacker. And what if physical security is out of your hands. If you have server somewhere in "cloud" you have to trust someone is protecting the stuff. So what, you won't patch vulnerability because you are "sure" they have good physical security, or maybe then you take it seriously? What about social engineering? You can have good security measures but the people are always the weakest link. You may never be sure you are 100 % secure.