• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle












  • Limeey@lemmy.worldtoGames@lemmy.worldDays Gone now on GOG ($16.49)
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    10 months ago

    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.
    :::







  • Due to how federation works, the federated instance needs to accept and process the activity. Each application can define its own “optional” activity properties, but the activitypub specs define mandatory properties and some optional properties for coherence across the fediverse.

    The way lemmy implements this is to use the activitypub-federation-rust library that the lemmy devs built. Through this, activities in Lemmy are sent using HTTP and have a failure retry:

    It is possible that delivery fails because the target instance is temporarily unreachable. In this case the task is scheduled for retry after a certain waiting time. For each task delivery is retried up to 3 times after the initial attempt. The retry intervals are as follows:

    one minute, in case of service restart
    one hour, in case of instance maintenance
    2.5 days, in case of major incident with rebuild from backup

    In the case of votes, the activity is a “like” - some other federated applications understand this and will accept it, but others won’t. For example, peertube does not have a like activity, and I don’t believe they would handle it.

    However votes are shared across instances. When a user “likes” something from another instance, Lemmy will notify that actor (the page) that the activity (a like) was emitted by another actor (you).

    Hope that clarifies things. I’m still learning all this myself so if anyone can contribute or improve my answer, please do!