this post was submitted on 18 Jun 2025
27 points (93.5% liked)

Lemmy.world Support

3456 readers
2 users here now

Lemmy.world Support

Welcome to the official Lemmy.world Support community! Post your issues or questions about Lemmy.world here.

This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.

This community is subject to the rules defined here for lemmy.world.

To open a support ticket Static Badge


You can also DM https://lemmy.world/u/lwreport or email [email protected] (PGP Supported) if you need to reach our directly to the admin team.


Follow us for server news ๐Ÿ˜

Outages ๐Ÿ”ฅ

https://status.lemmy.world/



founded 2 years ago
MODERATORS
 

I've mostly been a .world user, but have this alt account on .ca as a backup. I logged into it to make sure I didn't have anything in my inbox, and noticed that everything loads so much faster. In both cases I'm using the browser interface from my tablet, sorting by all. On .world, there's a pause before the text comes up, then the thumbnails and graphics slowly populate. On .ca, it all pretty much loads instantly.

Is it just the number of users being a lot bigger? More community activity? Hardware differences? Running different software versions? A combination of these? I'm curious.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] AFKBRBChocolate 5 points 2 days ago (1 children)

Excellent, thank you. I just cleared my cache and it does seem to have helped a fair amount. Not nearly as fast as in a private window, but probably as fast as .ca is now. Much appreciated, I'm glad I asked.

I guess that would explain why people who access it with an app don't seem to have the same issue, correct?

[โ€“] [email protected] 3 points 2 days ago

probably, this caching is just affecting the default lemmy web interface.

other apps or web interfaces may have their own caching implementations, though for web based stuff it's typically fine to leave it up to the browser, as long as there are suitable cache-control headers sent by the server.