Because of the fediverse partial mesh, leading to incomplete timeline view, or inconsistency depending the instance you’re on.
People tend to flock on primary, massive instances because they are well know of course, but also because this is where you have the most complete view, and from there your posts reaches many other instances.
Also different instances hide different communities and so they don't show up at all unless you are a direct subscriber.
I learned about this on my instance when some news communities were hidden, turns out my instance has quite a list of hidden communities, which isn't a bad thing, but it can contribute to the incomplete timeline issue and if you don't know about the hidden communities feature its very hard to diagnose why you're not seeing what you expect to see.
In my case I wasn't subscribed to some of the news communities because I would catch the top posts in /all, which keeps my subscribed feed focused on things I'm actively interested in. So hidden communities are a challenge when you use /all and /subbed in that way.
I'm pretty sure .world being slow is a web frontend problem. It often takes forever to load in my browser, but the same content loads quickly in the Voyager Android app.
I should probably try the several alternative web UIs they have available to see if they're faster than the default one, but I can't be bothered to walk over to my desktop PC right now.
HorreC
in reply to cm0002 • • •some_guy
in reply to HorreC • • •Septimaeus
in reply to cm0002 • • •Ⓜ3️⃣3️⃣ 🌌
in reply to Septimaeus • • •Because of the fediverse partial mesh, leading to incomplete timeline view, or inconsistency depending the instance you’re on.
People tend to flock on primary, massive instances because they are well know of course, but also because this is where you have the most complete view, and from there your posts reaches many other instances.
Septimaeus
in reply to Ⓜ3️⃣3️⃣ 🌌 • • •fuzzzerd
in reply to Septimaeus • • •Also different instances hide different communities and so they don't show up at all unless you are a direct subscriber.
I learned about this on my instance when some news communities were hidden, turns out my instance has quite a list of hidden communities, which isn't a bad thing, but it can contribute to the incomplete timeline issue and if you don't know about the hidden communities feature its very hard to diagnose why you're not seeing what you expect to see.
In my case I wasn't subscribed to some of the news communities because I would catch the top posts in /all, which keeps my subscribed feed focused on things I'm actively interested in. So hidden communities are a challenge when you use /all and /subbed in that way.
grue
in reply to cm0002 • • •I'm pretty sure .world being slow is a web frontend problem. It often takes forever to load in my browser, but the same content loads quickly in the Voyager Android app.
I should probably try the several alternative web UIs they have available to see if they're faster than the default one, but I can't be bothered to walk over to my desktop PC right now.
Ⓜ3️⃣3️⃣ 🌌
in reply to grue • •Maybe, but backend / database load is more likely, isn't it ?
You can look at your browser developer tools and see downloads sizes, durations, where CPU time is used on client side ;)
memes reshared this.
jackeryjoo
in reply to grue • • •