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

help-circle









  • The email analogy kinda works here.

    • Imagine an email server dies forever. All of the email that it sent is still out there. If you are on another server, any emaills to/from people on that server are stil in your local email storage.
    • Likewise, a post that was made to kbin.social is still out there, if someone outside of that server was subscribed to that kbin.social community (“magazine”) when the post was made.
    • To find out the “new” server… well in an ideal world the old server would at least have a notice to that effect. But this case involved a medical emergency, so that didn’t happen.
    Click here for an additional detail which may be amusing
    • See: https://lemmy.world/c/13thFloor@kbin.social This is the copy of the kbin.social community “13th floor” that was made on lemmy.world to show people on lemmy.world.
    • Now look at: https://lemm.ee/c/13thFloor@kbin.social This is the copy of the same community, but made for the lemm.ee instance. You’ll note that it is missing a post that was made on July 6th. That’s because the July 6th post was made by a user on lemmy.world. Because kbin.social was down by then, the post didn’t “federate” from lemmy.world through kbin.social to lemm.ee.
    • See https://lemmy.world/c/synthwave@waveform.social for another example. waveform.social was an instance that died, but people were still posting to the lemmy.world copy, but only lemmy.world people were able to see those posts because they were not federating. So in comments we just decided to make any new posts to another community on a “living” instance, and we put a notice to that effect.




  • I wouldn’t do version control that way, but I’ve used Word to keep track of what I’m working on during integration tasks. It’s nice because you can drop in code, error messages, and screen captures. E.g.: the tool looks like this: (image) but gives an error like this: (error message) and I think the problem is in file.py around lines XYZ: (code snippet) when I run the command (command used), and I think the answer is in (a couple links I found).