Post by @txt_file@chaos.social
This post received a lot of comments and reactions, which is great!
It also proved that my little Raspberry Pi Zero W, powered by NetBSD, could handle the load.
Now - to help me test how much load it can tolerate - please boost and react to this post! 🚀
@stefano
This is the first genuinely operational littleFedi instance.
It has been online since 1st July, is single-user (just me), and runs on a Raspberry Pi Zero W powered by NetBSD, directly on its SD card.
It consumes just under 1W.
Its database is this size:
-rw------- 1 little wheel 109289472 Aug 26 15:14 littlefedi.db
That is, just a little over 100 MB. Yes, MB.
Its average CPU load is extremely low.
It is perfectly usable both from the web interface and from Mastodon API apps.
I have 179 followers and 169 followings, and it doesn't bat an eye.
I promise myself to use it more, and I will.
You don't need Big Tech to communicate with others.
You don't need an expensive data center to exist online.
Because we are people, and the bits are just extensions of our voice.
EDIT: littleFedi allows to transform posts into blog posts, having its own SSG (Static Site Generator). The one generated by this post is reachable by clicking here.
1
❤ 1
👍🏻 1
1
1
1
1
1
1
1
1
1
1
1
1
1
@stefano here is a reply as you wished.
My biggest problem with the (multi user) mastodon instance I care for is the mastodon cache folder. Do you have a huge uSD or how do you handle that?
Cache folder on my instance fills the 100 GiB it has and I found no option to limit mastodon to fewer GiB.
@txt_file@chaos.social littleFedi allows to just proxy the images, so it won't store remote media locally. It will just proxy the requests, so the remote instances will see them coming from your instance, not your client. Or you can disable it and just request the remote media from the originating instances. That way, you don't need a huge media folder, just a small one to store local media files.