I make games

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

help-circle


  • mozingo@lemmy.worldtoMemes@lemmy.mlA retro problem
    link
    fedilink
    English
    arrow-up
    42
    arrow-down
    3
    ·
    3 months ago

    This happens because the connector is at an angle. Since it’s at an angle, the screw presses against the side and jams itself in place. All you have to do is tilt the connector the other direction and the tight screw loosens right up. Easy peasy.




  • mozingo@lemmy.worldtoMemes@lemmy.mlLooking at you, Google and Unity.
    link
    fedilink
    English
    arrow-up
    26
    arrow-down
    1
    ·
    8 months ago

    So two? I can think of way more shitty tech companies without Indian CEOs than with.

    Amazon, Twitter, Reddit, Bandcamp, Facebook, Unity, EA, Tumblr, Activision-Blizzard, Spotify, AirBnB, Uber, Snapchat, Netflix, Zoom, Bytedance, Hulu, Tinder, Epic, FTX, Apple, Tencent, Verizon, Cloudflare.

    I’m honestly having trouble thinking of any other companies than Google and Microsoft. Very much not “most”.





  • You’ve almost got it. The thing is when you view content posted to another instance you’re not actually accessing the other instances, you’re viewing a copy of those posts stored on your instance. Federation works by distributing copies to all federated instances.

    So if a big company like Google did as you said, and then suddenly defederated from everyone, you wouldn’t actually lose any of the content. All those posts up until the point of defederation would still be stored on every instance they were previously federated with. You would just stop getting new posts from that point forward.

    There’s a bit of weirdness though, since the “true” post on the hosting instance is what handles syncing/distributing copies. So any new posts you made to those communities or comments on those posts couldn’t be copied back to the true post and then spread to the other instances. So everyone ends up with a desynced “ghost community”. So while you might see new posts/comments in those ghost communities from people on your instance, they don’t get synced to any other instance. (If you’re on an instance that beehaw.org recently defederated from, you can see that in action right now.)

    So at the very least, the content would still be backed up, but you’re right in that people would need to “start over” and create new communities with new mods and new posts if they wanted the content to be federated. We just wouldn’t lose the old content.