Local timeline
@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.
littleFedi doesn't need a Raspberry PI to run.
It can run on a Raspberry PI - and this is totally different.
Thank you, friends!
The instance held up perfectly, without flinching! I also took advantage of the surge to identify a few areas for improvement, and they've been pinned down. New patches will be rolled out over the next few days.
The release is getting closer and closer...
@DK4HAA@mastodon.radio it probably can - but I can't test it as I miss the solar panel (but have a good power bank, and Italian sun would surely help)
@ricardo@bsd.cafe mmm...maybe I should contact the Raspberry PI company and ask for some money for (indirect) sponsorship 😆
@ivor@ivor.org @nantucketlit@mastodon.social From my own direct experience (strictly anecdotal and humorous): the more competent someone is and the further they are in internal ops, the less they need powerful or recent hardware.
@coreysnipes@hachyderm.io I can see the caption: "Hey, we don't need those clouds to communicate and be a part of the Fediverse!"