100% on my instance!
I’m the only user and placed one pixel, but hey! I won!

Good bot

Hey, when life gives you lemons, buy more storage!

Already fixed, will be in next release

If a new user on my instance was able to subscribe to a comunity on another instance, and all the posts/comments/likes of that community was being fetched so it was browsable on my instance - I would see no issue.

But as of now, if a user wants to browse content from several communities on different instances - and discover new interesting comunities on different instances - while being a user on a instance filled with "like minded users, they would need a user on all instances which hosts communities of interest to 1) discover these communities 2) view the posts from these communities.

What you are describing are single entities of communities, which defeats the purpose of federation completely, in my opinion.

I understand the idea of the “fediverse”, but personally think that the “no backfill” is the biggest missing piece of the great puzzle.

If I, 2 years from now, wanted to create an instance on the ever-so-popular fediverse, why should I? I can’t attract any new users, as they’ll lack all of the historical posts that makes a community a community (the inside jokes, the posts we still remember, that sort of thing).

Where we are today, better load your instance up with content from the popular communities at the popular instances, to ensure you are able to attract new users in the future.

I get why that defeats some of the purpose of the fediverse, but as for “new instances” it is crucial to have content - or else you have no new users.

I’ve played around with the Lemmony script, and altered it to take only popular instances in account. Right now it only parameterize by active users pr community, but I’ve changed it to also look at users pr instance, so you can subscribe to e.g. top 10 communities of the top 50 instances, so you have the content on your instance for new users joining… But this is just me playing around (and causing the load on the popular instances) with the dream of some day being able to provide my users with the content they would also be able to view on the major instances.

Allright, so this is isn’t the parameter that’ll speed things up by itself.

I set it to 10 (a bit more cautious than you, but this is somewhat new ground for me) and didn’t record more req/s, but it feels like the instance is a bit slower in terms of loading times. After I have tucked the kids in tonight I’ll snoop around netdata (where I’m monitoring the servers) to see what (or if something) has changed.

Seems like a great place to look.

I installed via Ansible, so the config doesn’t include the pool_size by default.

I can see that the default value is 5
I’ll go straight ahead and fiddle with this, but do you (or anyone else) have any recommendations, based on how postgres is working and memory/cpu loads?

(I’m not about to bump it to 100, but maybe someone has already found the “natural limit”)

Sync for Lemmy released yesterday and has what you are looking for.