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
My biggest concern with hosting it on a Pi is storage. SD cards are not made for write-heavy applications like Lemmy. If you want to host it on a Pi, I suggest adding a real hard drive over USB and configure Lemmy to use that for storage.
While I agree, it seems like OP only wants to house his account on his instance, and be federated so he can browse externally
I understand that, but his instance will get all the posts and comments he subscribes to, which will be written to the database every few minutes.
Please correct me if I am wrong, but this feels like a flaw with how Lemmy (perhaps other fediverse apps as well, I'm not sure) is designed. Why do I need to store all posts made to a community that one of the users on my instance subscribes to? Would it not be better to simply store my user's posts, and comments, and the posts made to any communities hosted on my instance? Why do I need to store information from other instances, and users?
It would put the more popular instances under enormous stress, if they had to serve every single subscriber from any other instance. This would also kill the user experience. It's much better to serve everything locally, so that an instance admin can scale their resources to the number of users on their instance, a number they know.
I actually am interested to see how the fediverse's concept of federation scales out, as numbers keep growing. Even with just instances syncing between each other, I feel that this might be too much at a certain point.
From what I understand, media (images, videos, etc.) is not cached. Does that not mean that, in the worst case where every post contained an image, the instance would be serving every subscriber, anyways?
For binary data that is correct, yes. But that is stuff an instance admin could choose to hide behind a CDN, as it's easily optimized and cached.