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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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
Imagine a world where all these rust devs would write new software instead of manically reimplementing existing software in rust...
Imagine a world where we're all using 30 year old software because it "still kinda works".
restic is 8 years old though
And? I didn't mention restic, nor did the person I was replying to. I was under the impression we were both talking about software being rewritten in Rust in general.
restic is living proof that is neither 30 years old nor "kinda works". It also doesn't suffer from typical memory access problems because it's not written in C.
Given that this whole post is about restic, this felt relevant to point out. You're apparently not talking about rewrites in Rust in general, but rather rewrites in Rust of software the likes on GNU and the Linux kernel.
Aren't most CVEs out of bounds writes/reads?
Rust helps prevent that, so more secure software seems like a good thing
So long as they don't abuse
unsafethat is