My disclaimer is that I am excited using the fediverse as alternative from Reddit (I have switched to Mastodon from Twitter).

I have been trying a combination of lemmy.world, kbin and a lemmy app like MemmyApp. Each one, I look at “All” and try various things like “hot”, “active”, “top day” and etc. Each one produces different results. And it is not even close. Rarely are there same posts across each. Also, on lemmy.world, after I sort on one of these, a few seconds go by and it won’t stop scrolling with a blast from same communities and users.

So… what is it I am doing wrong? How do I make my experience more enjoyable? Am I the only one?

(Note: I am aware that kbin/lemmy have their own local and therefore, that would be different, but the “All” filter?)

  • pruwyben@discuss.tchncs.deEnglish
    1·
    1 year ago

    “All” will be different on different instances - it’s basically all of the communities/magazines that anyone on that server follows. On large servers this’ll cover just about everything but not on smaller servers. Plus there is probably a lot less cross-subscription between Lemmy and Kbin than within each. The two may also have different algorithms for the hot/active lists.

    The scrolling thing is a bug with Lemmy. It’s been resolved with version 18 but some instances, including lemmy.world, haven’t updated yet.

  • tallwookie@lemmy.worldEnglish
    1·
    1 year ago

    my limited understanding is that the federating of information between disparate instances is not real-time. it takes a while for things to filter through the fediverse

  • snailwizard@lemmy.worldEnglish
    1·
    1 year ago

    I think for now it’s working as intended. There is an unprecedented amount of new users, after all. I imagine that over time, probably by the end of the year, communication between instances will be much more seamless once bugs get squashed

  • itsnotlupus@lemmy.worldEnglish
    1·
    1 year ago

    Welp, I’m new too, but I think this is more or less working as intended.

    The federation mechanism is a “best effort” thing, so there’s literally no guarantee that you’ll get the same view for the same thing loaded through two different instances.

    I started writing a userscript to “normalize” URLs so clicking on a link to kbin.social on a different instance would transform the link URL to keep you on your original instance, but with the distinct possibility of missing content because of it, I’m not sure it’s actually a good idea.

    The auto-refresh-and-btw-lemme-close-the-image-you-were-looking-at behavior isn’t happening on every instance, but it definitely happens on lemmy.world. Maybe this is an artifact of the websocket approach, and that’ll go away in 0.18? No idea.

    At this point, the usage pattern I’m leaning toward is to find good communities/magazines, subscribe to them, and stick to the “subscribed” view. The most consistent results will always be with subs that are local to the current instance, so if most of your subscriptions are on instance X, you probably don’t really want to have your account on instance Y.

  • I_will_eat_that@lemmy.worldEnglish
    1·
    1 year ago

    I keep getting that “blast” of posts you describe, too. Glad it’s not just me. Probably just growing pains as others have said