I have an account on kbin. Recently I saw a post across my feed in which a magazine that I follow (that’s based on a Lemmy instance) was celebrating over 1k subscribers. When I visited, I saw only 240 or so.

I decided to check it out from a Lemmy account and saw well over 1k. I also saw massive amounts of content that was not being pushed to my kbin account. Even when looking at specific users, I could see only the occasional post they made was visible to me on kbin while on Lemmy I could see massive amounts of content that they had posted to this magazine.

It bummed me out because one of the things they shared is extremely niche and I’ve never seen anyone else out in the wild interested in that topic and I would have loved to engage… But it never made it to my kbin feed.

Is this an issue with kbin vs Lemmy? Is there hope it will be fixed? I feel bad because I don’t want to use Lemmy and have loved kbin but am certainly jarred that I’ve been missing out on 80% of the content from a magazine I’ve been invested in engaging with.

TIA

  • r00ty@kbin.life
    2·
    1 year ago

    This is where things get even more confusing. Kbin DOES have boosts. Plus upvotes and downvotes. So, mastedon boosts become boosts. Lemmy upvotes become upvotes. Lemmy downvotes become. Well nothing right now. There’s a lot of things that are still work in progress and even though they all talk the same protocol there are concepts that are interpreted differently.

    There’s also the standard, and then what’s generally used. I fixed an issue recently with kbin, which was happening on the rare occasion I had an interaction with “lotide” (another activitypub program). Lemmy and kbin (and probably mastedon, I dunno) always put “To” and “Cc” as a json array even if there’s just one element. But lotide doesn’t if there is only one item (often the case in To). This is fine as far as I can see in ActivityPub’s structure. But, kbin expected an array. These kind of things are going to be ironed out now there’s far more content moving around. The errors will be appearing in our logs and they will be gradually resolved.