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!
view the rest of the comments
It still defends against one failure mode (the website gets hacked but you're ok) but yeah, obviously if you get hacked and the hacker knows how to get your vault out then you're 100% screwed.
My suggestion is always hardware 2FA, even though it's not as mature as the other systems. Personally I have two Yubikeys (in case one breaks/gets lost) but it does mean that I need to add TOTPs to both of them each time I add a new 2FA.
I'm fairly certain hardware based 2fa has been around since the early 90s maybe even earlier. It's not the maturity that's the issue, as I'm fairly certain its significantly older than application based, but that it's extremely inconvenient for the user to have to buy a physical key and keep it safe
I don't mean that it's not old, I mean that it's still got some more room for improvement. Passkeys, for instance, are an attempt at improving the user experience.