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
I've been following the software forge federation some time ago, and didn't feel to pick up even when it was discusssed initially. It is a neat idea on high-level, though it requires forges to implement it, which has a risk of not picking up (just look at how much iterations of social media federation protocols was there, until ActivityPub arose).
On the other hand, all of the forges are based on a distributed technology out of the box:
git. Most of the "modern days" comforts there are, are just built on top, and there are different ways to approach it.As an example, you can send patches directly to the author in email. Is heavily implemented and suggested by https://sr.ht/ (1) — a software forge, which focuses on building a federated workflow by using email for communication (which is federated by design). This way, you can create "Pull Requests" without having account on the forge — all you need to do is just submit a patch. Author is very vocal about supporting it (2), and provides quite useful guides to learn (3), (4)
Generally, I'd say that e-mail is the only federative implementation you can get so far :)
Yeah I guess git via mail would solve some of those problems. Maybe I'd just need to get used to it, but generally I prefer a web ui for those things, including Issue tracking etc - I know there's tools for that via email and there's good reasons to use it, but somehow it doesn't feel right to me. I'll give Drew's articles another look, thanks for posting.
The web ui with integration of email ecosystem for all those things are one of core selling points of https://sr.ht/
Indeed, not sure I want do host sourcehut though. Looks like a complicated setup and only supports Alpine but not (Docker) containers.