this post was submitted on 03 Jul 2023
28 points (100.0% liked)
Philippines
1613 readers
4 users here now
Mabuhay at maligayang pag-alis sa Lemmy! ✈️
An abandoned community for the Philippines and all things Filipino! 🇵🇭
Started out as a Reddit alternative during the blackout from Jun 12-21, 2023 with over 1k members in just a few days. Fizzled faster than the "I Didn't Do It" kid after a month until it became the internet's Centralia in less than a year.
Filipino artists whose works were featured on our daily random thread covers.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
TL;DR: Accessing lemmy.world from a faster instance feels faster because you're probably not really accessing lemmy.world.
There's likely two contributing factors as to why lemmy.world has been acting up lately:
From my experience, it seems like there's an issue with how the lemmy.world's frontend interacts with the backend. But it doesn't seem to affect users from other instance because as I've said, they're not really accessing lemmy.world.
To elaborate, there was a post weeks ago on how beehaw defederating with lemmy.world affects the lemmy.world users. Of particular interest is an explanation on how ActivityPub works.
So if I'm understanding it right, if you're reading and commenting on this particular post, you're really interacting with a copy of it in your instance. Your instance and lemmy.world will then synchronize the data through the ActivityPub protocol to ensure users from both instances sees the same content. This is a backend-to-backend interaction and thus may not be completely affected with lemmy.world's issues.