• 1 Post
  • 29 Comments
Joined 1 年前
Cake day: 2023年6月13日
  • Limeey@lemmy.worldtoGames@lemmy.world•Days Gone now on GOG ($16.49)English
    2·
    8 个月前

    Agreed, I was pretty annoyed with parts of the main story.

    ::: Spoiler warning

    Imo boozer should have died, that would have made finding Sarah more emotional. His miraculous recovery always felt bullshit.

    Also Sarah’s character was ridiculous. I get that it’d been 2 years, but she didn’t care at all that deacon was alive. Their “keep it secret” thing was fine but like even in private she didn’t give a fuck, which was weird to me. And her whole “I can save them” arc was really weird.

    I remember thinking that there must have been a lot of cut content, because the end of the story progresses really fast compared to the rest, I had expected more build up.

    And finally, it would have been nice if at the end boozer and Sarah weren’t just boringly “sitting” at lost lake. like, they are badasses after that story but at the end they’re just content with sitting around while deacon goes off. The end game could have been vastly better than it was.
    :::

  • Limeey@lemmy.worldtoAnnouncements@lemmy.ml•We're the creators of Lemmy, Ask Us Anything. *Starts Monday, 7 Aug, 1500 CEST*English
    4·
    11 个月前

    The search process basically works by looking for the “@” sign in the search term, if the name isn’t found locally, then it uses the apub process called “webfinger” to identify the instance and request the information from it. This process relies on the host server being online, correctly receiving the request, correctly responding, and then your server correctly ingesting that response before emitting the reply to you.

    So if no one on your instance has already gone through this process, then there’s a couple chances for the chain of actions to fail, but once that community is “subscribed” and created locally, then your search without the “@” will fetch the “local copy”. Once that local copy exists, it “announces” itself to the home instance, this then tells the home instance to start emitting all the apub info to your local instance (new posts, comments, votes, etc).

    So I believe what you’re seeing is first the get_communities takes a while to go through all of that. Because of that, while waiting the UI sets the results to “empty” until the actual return comes in, once the results come back and the UI updates the state, you see the community in the list. But until that community is “copied” locally, you can’t manually go that community from your local instance url simply because it doesn’t exist locally yet.

    The issue also comes down to the fact that no instance needs to update. So if you’re requesting a v0.17.x instance community from a v0.18.x instance, the api’s changed and they may not communicate properly to your home instance. I’m sure there are other points of failure too.

    But I believe the lingering “pending” state should be mostly fixed, if you’re using an instance that’s on 18.3 then I don’t think you should encounter that much…

    EDIT: It should be noted, that once you search for the remote community, it will fetch the entire community, including all posts and comments, and populate the cache (which I believe lasts for 3 days as of 18.3 unless someone subscribes to it, at which point it’s effectively “saved” locally). This means big communities might be extremely slow to respond to the apub request