All of this user’s content is licensed under CC BY-SA 4.0

  • 15 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle
  • What I like about the Gadsden flag, as opposed to this one – according to how I interpret it, anyways – is that it advocates for the use of one’s voice before violence. The main symbol on the Gadsden flag is a timber rattlesnake. If you think about such a rattlesnake in nature, when you get too close to them, or provide them with a reason to feel wary, or uncomfortable they won’t immediately attack you, but will instead provide you with an auditory, nonviolent warning. It’s only when one ignores their warnings, and continues to harass the snake, or give them a reason to think that they are under immediate threat of harm that they will fight back, and will not hesitate to do so. In all other circumstances, the rattlesnake will mind it’s own business, and let you do the very same. I find this behaviour admirable of a creature, and it is, in my opinion, the true ethos of libertarianism. The Canada goose, on the other hand, won’t hesitate to harass you. they will routinely attack people just relaxing in a park. They provide little warning to someone that they find threatening, and will often choose to immediately strike out. This is not behaviour that should be emulated, or admired, in my opinion.










  • Flatpak – It’s not without it’s own issues, of course, but it does the job. I’m not fan of how snaps are designed, and I don’t think canonical is trustworthy enough to run a packaging format. Appimages are really just not good for widespread adoption. They do what they are designed to do well, but I don’t think it’s wide to use them as a main package format.












  • I don’t really understand this reasoning. Some server would still need to receive those requests at some point. Would it not be better if those requests were distributed, rather than pounded onto one server? If you have a server caching all the content for its users, then all of its users are sending all of those requests for content to that one single server. If users fetched content from their source servers, then the load would be distributed. The only real difference that I can think of is that the speed of post retreival. Even then, though, that could be flawed, as perhaps the source server is faster than one’s host server.



  • I ran a S.M.A.R.T short test, and, yeah, the hard drive is quickly dying:

    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: FAILED!
    Drive failure expected in less than 24 hours. SAVE ALL DATA.
    Failed Attributes:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x002f   001   001   051    Pre-fail  Always   FAILING_NOW 1473
    



  • That disk certainly isn’t healthy.

    For my own future knowledge, what, exactly, in the logs, led you to that conclusion?

    image the whole thing with ddrescue

    Since you mention “image”, I’m assuming that I would need a drive at least equal to the size of the source drive to store the image? The issue is that the source drive is 2TB in size, so I would need to source another 2TB drive (at least) to store the image.