Local timeline
@armando@rollenspiel.social this is absolutely true. To be fair, the encryption we use today is much more complex (even if often hardware assisted) than the one we used 20 years ago. Still, software is generally bloated.
@stefano Yes, the performance here is on a totally different league. No difference from the #littleOne instance on the VPS.
So I can say that armv7 is giving an optimal experience.
@andrew@this.wplr.rocks I can't exclude it. I'll retry with the ethernet adapter and see what happens-
Now on a Raspberry Pi Zero 2 W - powered by NetBSD (armv7) - with an USB ethernet card, as the internal wifi seems to lock when the traffic goes up.
It's blazing fast
@release_candidate@bsd.cafe I still have four of those A+. They’ve been on for more than 10 years and still rocking!
...let's lower the barriers even further!
Now this instance is running on a Raspberry Pi A+ (1 core @ 700 MHz, 256MB RAM), so even less than the Raspberry Pi Zero W it was running on before.
On NetBSD, of course!
Edit: it suffers a bit. I don’t know if it’s for the lower ram or lower speed sd card or the external WiFi adapter, but it’s slower than the Zero W. Still usable, but not optimal. I’ll try with the original B and will see if / how different it is.
#littleFedi #NetBSD #RunBSD #OwnYourData #Decentralization #OwnYourVoice
@napierge@bsd.cafe @adele@social.pollux.casa @mastoblaster@mastoblaster.app thank you for mentioning me. Yes, both with #littleFedi (as a platform) and #MastoBlaster (app), we're trying to make sure the Fediverse is light on resources and accessible. You don't need tons of javascript to say "hello".
We all share the same planet
Posting this little friend of mine from my tiny instance, running on a Raspberry Pi Zero W with NetBSD.
I'm hoping for lots of interactions, partly because I'd really like to see how far this little setup can go. 😉
But there is also a story behind this photo.
This little one was born free. For quite a long time I used to meet them almost every day, and I watched them grow up. They would come towards me, always keeping a little distance, and meow at me in that friendly way cats sometimes do.
This is the last photo I have, taken just before the Covid lockdowns.
When we were finally allowed out again, I never saw this little one, or any of their brothers and sisters, again.
I like to imagine that during those strange months they simply enjoyed having the world a little more to themselves. Wandering around freely and peacefully, without too much human interference.
And then perhaps they grew up and moved towards the little woodland they always liked to visit, living a free, happy and full life there.
Wherever you are now, hello, little one. ❤️
@Holocene@techtoots.com on littleFedi you can disable media caching, just leaving the proxying on (if you want to)
@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.
@Holocene@techtoots.com GoToSocial will also reprocess (by default) all the media files, and that will use resources.
@knapjack@vivaldi.net no. But we have a "low power mode" that will lower some specific settings.
The preset selects one database connection and one queue worker, a bounded memory cache, one image decoder, a 13 million pixel bound on decoded images (enough for a 4032 by 3024 phone photo), a 1600 pixel cap on stored uploads, cheaper thumbnail resampling, and no dynamic gzip.