• 1 Post
  • 112 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle
  • In isolation it’s not great, but in conjunction with your own advocate talking about you not following a doctor’s orders? It doesn’t bolster confidence that the individual would follow doctors orders in the future.

    It means she hasn’t been able to quit drinking!

    Yes, that’s exactly the point. It’s quite unlikely her medical troubles started when she was hospitalized.
    A history of not following medical advice casts doubt about a future of following medical advice.

    Yes, addiction is a disease that the individual may lack the ability to control. That doesn’t change that it’s a risk factor for non-compliance that’s absent in others who need the transplant.


  • Not made up, I just read a couple other articles that mentioned it.
    It’s also part of the whole “the only people who can talk freely are the people with an interest in the doctors being wrong”.

    People aren’t turned away because they didn’t exercise or because they work too much or they don’t get enough sleep or they didn’t follow doctor’s orders. So, in Nathan and Amanda’s case, you’re seeing someone being told, ‘You didn’t follow doctor’s orders, so we’re not going to help you. We’re going to let you die’

    As a quote from the other interested party, as well as the “in documents shared with CTV News, notes show […] their decision was based on ‘minimal abstinence outside of hospital.’” is pretty much spelling it out.


  • It actually takes surprisingly little if it’s done consistently and without giving your body time to rest.

    A standard drink has roughly 14g of ethanol in it. People with notable liver damage tend to have a history of a decade or more drinking 30-50 grams a day, or two to three drinks.
    People who drink more than 80g a day for a decade are almost guaranteed to have liver problems (~5-6 drinks).

    Obviously drinking a half gallon a day is worse, but consistent long term drinking is also not great.

    It is essentially a poison that’s only around because it’s easy to make and traditional at this point.




  • Well, stopped drinking when she got the diagnosis, not before, relapsed into drinking while on the transplant list, and as they said in the article there are a lot of criteria for a living donation, and it’s only an option if you otherwise qualify for a donation because of the possibility of rejection requiring an urgent transplant.

    A different article said they were trying to raise funds to get the transplant done at an unspecified European hospital, so “yes”. I think it’s telling that they didn’t go to the US, a north American country, or specify the country.
    It’s worth remembering that the only people who can talk freely are the people who were decided against and are talking about suing.

    No one wanted her to die, but with organ transplants it’s a case where you’re more or less picking who will die. Phrasing it as being punished for bad behavior is unfair to the people who need to decide which people are likely enough to benefit, which isn’t easy.




  • In the sense that they have a manager? Sure. In the sense that there’s one individual dictating the design of the software? I’ve never even been on a team with that dynamic, to say nothing of the entire codebase.

    Modern software teams tend to eschew design by decree.

    What’s the dynamic that you’re thinking is typically what teams use?


  • I’m not sure I’d construe a manual you can find, or a variety of guides, as a negative. :) most days my usage of git consists of “pull, commit, push, merge” in different orders. You might be overestimating how much effort goes in to managing the tool.

    Most of my professional experience has been working on projects that consist of multiple teams of between 4-6 developers, and between 5 and 40 teams. I’m not entirely sure what you mean about git not mirroring the development patterns of most “real life” projects.
    “Real” projects are frequently developed by groups of people working on the same goal adjacent to other groups working on related but distinct goals.


  • We very clearly work in different professional environments. :)

    In no particular order: Administrating a git server is similarly trivial. A repository is a folder (easy to backup, easy to repair, easy to host), and setting up a new server usually a matter of ssh key management. Don’t even need to install sqlite or anything beyond the git package. Or, because the tool has wide support, you can install a wide selection of tools that manage it for you, or use a free hosting service, or a paid one.

    I’m startled that you would say you can’t think of anyone who would care. My entire professional experience has been developer stories about bad jobs often include details about using old or esoteric VCS systems, usually met with “ew” or “wtf” comments. Sets the flavor of the story.
    Personally, in a business environment, I would take using anything except git for the org as a red flag. It’s a sign that someone in leadership at the company values doing things unrelated to the core mission “their way” above doing it the easy or “paved path” way.

    The standard tool is indeed not constant. Before git existed, using CVS would have been the better choice, as well as for years afterwards until it had clearly been usurped. Most projects aren’t Linux when it made the switch to git.

    You joke that no one really “knows” git, but… This is literally the first time I’ve ever seen a fossil command. I just searched for “fossil manual” and I get analog watches. It’s not even available in any of my systems package managers.
    Developer familiarity is a big advantage that I think you’re downplaying in comparison to “there are metadata files in .git”, which I don’t know has ever been relevant to me in any significant way.
    (Also, I thought the different systems all work basically the same? 😛)

    I’d handily agree people should be using the best tool for the job. Familiarity and ease of use are significant factors in what makes a tool better.
    Ability to integrate with other tools is also a major factor. Setting up continuous integration or code review tools with git is trivial with any number of different systems.

    What are any of the tools you’re using doing better than git? The biggest selling point you’ve shared for fossil is that it’s functionally similar to git, and that it has better merging. I can’t find anything related to merge conflicts outside of years old forum posts, and barely anything relating to merges at all, so I’m not entirely certain what makes it “better”.

    If it’s biggest advantage is that it’s similar enough to git that you can pick it up fast, why wouldn’t I just use git?




  • File1, file2, file_3.new, etc would be bizarrely stupid. A home rolled solution involving rsync, tar, gzip, crons or inotify would also be bizarrely stupid.

    https://en.wikipedia.org/wiki/List_of_version-control_software anything on that list that’s marked anything other than “active” as a more serious answer. So like DCVS, visual source safe, or bitkeeper. Anything that’s not getting bug fixes or maintenance.

    Anything that doesn’t have significant enough usage to give confidence that bugs or glitches are being caught by common usage would be risky, since you don’t want to be the person to find that edge case.

    There’s things other than git that aren’t wrong, but I see little compelling reason not to use the most ubiquitous tool.


  • There’s a difference between “can’t code” and “can’t work”.

    A lot of people use git for version control: super good idea, basically anything else is at best unorthodox, at worst bizarrely stupid.
    A lot of people also use github for repository hosting, continuous integration, code review, deployment, packaging, etc, etc. this is more of an opinion thing than a standard practice thing, and there are plenty of other ways to get the same tools, either all in one package or from a variety of different ones, self hosted, in the cloud, or some hybrid in between.

    If GitHub goes down, you can make code changes and everything to your hearts content. But you might not be able to run your full integration testing pipeline on it, get a code review, or package your software.

    If your local build process pulls packages from GitHub or refreshes a remote repository automatically, it can also powerfully mess that up, but that’s nothing to do with git. You can use “ctrl-c/v” backups and still have a build process that tips over when GitHub goes down.


  • Paul Eggart is the primary maintainer for tzdb, and has been for the past 20 years.
    Tzdb is the database that maintains all of the information about timezones, timezone changes, leap whatever’s and everything else. It’s present on just about every computer on the planet and plays an important role in making sure all of the things do time correctly.

    If he gets hit by a bus, ICANN is responsible for finding someone else to maintain the list.

    Sqlite is the most widely used database engine, and is primarily developed by a small handful of people.

    ImageMagick is probably the most iconic example. Primarily developed by John Cristy since 1987, it’s used in a hilarious number of places for basic image operations. When a security bug was found in it a bit ago, basically every server needed to be patched because they all do something with images.


  • Yup, that would indicate that likely a bot is trying to guess it’s way in.

    You are still safe.

    The only weird thing here is that Microsoft lets such things bother you instead of guessing that you didn’t teleport to Brazil and instead putting a little extra burden on the Brazil end before sending you an email.

    If you’re still feeling worried, the biggest thing you can do is enable two-factor auth (which you should do anyway), or even better: enable something like passkeys which are very secure and also easier than username/password.

    Two-factor/password manager is the “remember to brush and floss” of the security industry, so… Please do those things. :)


  • That is wonderful advice and I’m glad you pointed that out. :)

    If I knew how to give directions to the page, I would, but unfortunately I don’t know the Microsoft site layout, only the URL that their help center directed to.

    In mitigation of my indiscretion: it’s generally safer to trust a person you approach out of nowhere than to trust someone who approaches you out of nowhere.
    Since they chose the venue and asked the question, the likelihood that an attacker is present in the replies is lower than the expectation that an unsolicited email is from an attacker.

    But it’s also entirely correct to be distrustful of anything anyone asks you to click on, triply so if it involves security or login pages.


  • It is actually safe to ignore them. It means either someone has an email address similar to yours, or a bot of some sort has you email address and only your email address.

    Essentially, someone or something goes to the login screen, enters your login, and says “I don’t have the password, let me in!”.
    Sending a code to your email like this is the first step in letting someone in without the password, or more specifically to having them reset it.

    Since the email is to check “did you ask for this?”, doing nothing tells them that you did not.

    If you want some extra peace of mind: https://account.live.com/Activity should show you any recent login activity which you can use to confirm that no one has gotten in.

    Also, use two factor, a password manager, and keep your recovery codes somewhere safe. The usual security person mantra. :)


  • It’s a delightful PR gimmick by a most definitely not a tech company, since there’s not much cutting edge technology going on in the world of “flamethrowers are perfectly legal in America and that’s our business model”.

    In addition to strapping a flamethrower to a generic quadruped robot, they also strapped one to a drone.