I’m interested in possibly hosting my own Lemmy instance - just for my own account. I was thinking of hosting it on Raspberry Pi (possibly the 1GB Pi 4 B), but I couldn’t find much for definitive information on what the hardware requirements would be for such an instance to know if this is even possible. How much storage is required? Is the Pi 4 CPU powerful enough? How much memory?
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.
Oh, my misunderstanding. I didn’t realize that would be written to his own db like that
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.