• emptyother
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    Oh, that explains why I havent gotten a single upvote on any of my comments for the last 6 days. My lemmy.world account cant see a single programming.dev comment I have made anywhere (or at least in lemmy.world, startrek.website, and sh.itjust.works).

    • Die4EverOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Yep, things are really slow because of this bug. If you could please share your experience with example links in the GitHub bug report it might help. Especially if you can get your instance admin to join in the comments and help with looking through the logs.

      https://github.com/LemmyNet/lemmy/issues/4039

  • lowleveldata
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    I have noticed the same thing. My comments since 2 days ago have not been sync to other instances. Works fine before that.

  • AtegonMA
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 year ago

    (for people not in the discord or instance admin matrix since its been getting talked about there)

    Other instances have reported similar problems

    Im guessing its a bug with 0.18.5 instances interacting with non 0.18.5 instances.

    • programming.dev (0.18.5) - report about content not showing on sh.itjust.works which is on 0.18.4
    • lemdro.id (0.18.5) - report about content not populating from lemmy.studio and sopuli.xyz which are 0.18.3 and 0.18.4
    • midwest.social (0.18.4) - content not showing up on lemmy.ml which is on 0.18.5
  • aport
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    For a moment I thought 0.18.5 introduced federation-wide shadow bans.

    • Deebster
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I was getting that feeling too, which made me check that my posts were even visible. I’m kinda relieved it’s “just” a bug. A pretty bad one, though.

  • Deebster@infosec.pub
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    It seems to vary between instances, even ones on 0.18.5. For example, lemmy.world and programming.dev seem to be struggling to talk to each other (can’t see or search for posts, for example), but infosec.pub (which hosts this account) seems able to communicate with both.

    [edit] infosec.pub can post to programming.dev and that post federates over normally. Posts from programming.dev on itself or infosec.pub do not federate over to infosec.pub, but can be searched from infosec.pub (whereupon they show up normally).

  • nieceandtows
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I just noticed that anything in the past 4 days of mine isn’t visible on any other instance.

  • mark
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    1 year ago

    IIRC, this is how it works by design. Posts don’t get federated to another instance unless someone from that instance interacts with it e.g. searches for it, comments on it, etc

    • AtegonMA
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 year ago

      Thats only the case for communities, not posts in an already fetched community

      • mark
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        What do you mean by “already fetched”? I’ve been on the fediverse for quite a while and I’ve never seen new posts from a community be automatically federated across every other instance in the fediverse without someone from those instances interacting with it (e.g. following the community, searching it, etc). Can you point me to where it says it works the way you say? Not saying you’re wrong. But would be news to me.

        • AtegonMA
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          1 year ago

          That is what im saying. The thing is with that community above the community has already been interacted with (fetched) in that instance with the op having been making posts in it for a very long time and all previous posts federated. It sounded like you were saying that happens on the post level instead of the community level

          Im guessing that this is a bug that got introduced with 0.18.5 since it hasnt been a problem until now

    • Die4EverOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      To convert the process into Mastodon terms, a community is like a dummy user, it’s not like a hashtag. Making a post to a community is like doing a mention tag to it, like @communityname@instancename, so the community’s home instance should always see all the posts to it. (This is the part that I noticed wasn’t working)

      The community boosts every post to it, so every user who is subscribed/following the community can see the posts that it boosts, which means the instances hosting the subscribers/followers will receive copies of the posts, so federation is automatic there because of the boost.