2
submitted 11 months ago* (last edited 11 months ago) by [email protected] to c/[email protected]

Each Fediverse server instance has its own local user accounts. But because they on a federated social-media network (called the Fediverse) with other server instances, each server instance needs some "awareness" of user accounts on other server instances.

Part of this "awareness" tends to be caching the profiles, bios, avatar images, etc, of user accounts on other server instances — i.e., remote user accounts.

Some of these images can be very large. And can cause the cache of remote user accounts to take up a lot of drive space. Which often translates to a higher monthly hosting costs.

This could apply to any Fediverse software.

But this particular example of it happened to Pixelfed.

The conversation started here:


https://mastodon.social/@[email protected]/111152253455206463

I also talked to Basit Ali (from #SpaceHost) about it, and he said:

"I noticed it as well when migrating @atomicpoet’s pixelfed instance [to #SpaceHost], the remote avatar cache was like 80% of the storage. Also it wasn’t downsizing the avatars before caching, some avatars were in megabytes."

There are different ways this could be addressed.

you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 1 points 11 months ago
this post was submitted on 08 Oct 2023
2 points (100.0% liked)

Fediverse UX

20 readers
1 users here now

Discussion about user-experience (UX) of the any part of the Fediverse — Mastodon, Akkoma, Bonfire, BookWyrm, Castopod, GreatApe, Epicyon, Firefish, Friendica, Gancio, GNU social, GoToSocial, Guppe, Hubzilla, Immers Space, Kbin, Ktistec, Lemmy, Misskey, Mobilization, Nextcloud, Owncast, PeerTube, Pixelfed, Pleroma, Plume, PostFreely, PostMarks, Socialhome, Takahe, WriteFreely, and any other Fediverse software.

founded 11 months ago
MODERATORS