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
When I first heard of the fediverse without understanding the architecture I envisioned something like torrent networks, where the larger the network the stronger the network. After learning more I'm not sure that's the case yet. Hopefully that is the endgame.
I would want to be in a place where I could enrich an existing community by self-hosting and synching content of that community and offering my small chunk of bandwidth to that community. I realize there is no community synching between instances, but I feel that's where it should be to prevent corporate control of communities in the future.
You can read the ActivityPub protocol... I don't think it will become like bittorrent, as there peer-to-peer concept doesn't seem to exist in the spec.
Having said that, while we are running into implementation limitations on the larger instances, the problems are being tackled. A couple of us are chatting on
[!lemmyperformance@lemmy.ml](/c/lemmyperformance@lemmy.ml)
and[!lemmyfederation@lemmy.ml](/c/lemmyfederation@lemmy.ml)
to see if we can come up with good ideas to present to the devs to help Lemmy scale. You're most certainly welcome to join in on the fun!ActivityPub define an inbox forwarding feature. I haven't dug too deep into Lemmy source code to see if Lemmy implement this, but if it does, this feature would allow more efficient propagation of activities (e.g. A -> B -> C instead of B <- A -> C where A is the originator).