• 0 Posts
  • 16 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle




  • dragontamer@lemmy.worldtoAsk Lemmy@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    3 months ago

    Not: Gilgamesh is the oldest still surviving written story.

    There was writing older than Gilgamesh. There were cities and culture before 2000BCE. Its just so old that nothing at all survived beyond that time period.

    There’s the Bronze Age Collapse, Burning of the Great Library, and many other events that destroyed history in the 1000BCE period. Those old people may have had older records than Gilgamesh, but all we have today is Gilgamesh if that makes any sense.



  • dragontamer@lemmy.worldtoAsk Lemmy@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    3 months ago

    King Arthur isn’t “one story” though. King Arthur is closer to 1100s-era fanart / fanfiction culture.

    EVERYONE was making King Arthur stories back then. And guess what? They contradicted. That’s why we have Excalibur vs Sword in the Stone (sometimes they’re the same sword. Sometimes they aren’t. Its a big contradiction because there’s no singular author).

    The Chinese Great Novel “Journey to the West” is truly one story by one author with multiple millennia of copycats. Meanwhile, King Author is basically a millennia of copycats without anyone knowing who the original was to begin with. Very different fundamentally.




  • Also, David basically brought a gun to a knife fight against Goliath. Seems like Goliath should have been considered the underdog :3

    Its been suggested that the combat could have been a ritualistic slaughter. Much like the Gladiator Ring was ritualized slaughter, to appease the masses.

    IE: David vs Goliath, if it were to ever have happened in true history, would have always been written down like the story. The concept of “true history” wasn’t invented until centuries after that particular story. The purpose of writing in the Bronze Age was to build shared culture and shared stories.





  • dragontamer@lemmy.worldtoMemes@lemmy.mlYou sure are, dipshit.
    link
    fedilink
    English
    arrow-up
    34
    arrow-down
    5
    ·
    edit-2
    5 months ago

    Their eyes are still closed. Unless you walk up to that neighbor in the next day or so and show him the clip, he won’t see it or believe it.

    Hell, it’s already too late and your neighbor is probably already making excuses about how Elon Musk is just sharing his hearts energy or some shit.


  • That’s not what storage engineers mean when they say “bitrot”.

    “Bitrot”, in the scope of ZFS and BTFS means the situation where a hard-drive’s “0” gets randomly flipped to “1” (or vice versa) during storage. It is a well known problem and can happen within “months”. Especially as a 20-TB drive these days is a collection of 160 Trillion bits, there’s a high chance that at least some of those bits malfunction over a period of ~double-digit months.

    Each problem has a solution. In this case, Bitrot is “solved” by the above procedure because:

    1. Bitrot usually doesn’t happen within single-digit months. So ~6 month regular scrubs nearly guarantees that any bitrot problems you find will be limited in scope, just a few bits at the most.

    2. Filesystems like ZFS or BTFS, are designed to handle many many bits of bitrot safely.

    3. Scrubbing is a process where you read, and if necessary restore, any files where bitrot has been detected.

    Of course, if hard drives are of noticeably worse quality than expected (ex: if you do have a large number of failures in a shorter time frame), or if you’re not using the right filesystem, or if you go too long between your checks (ex: taking 25 months to scrub for bitrot instead of just 6 months), then you might lose data. But we can only plan for the “expected” kinds of bitrot. The kinds that happen within 25 months, or 50 months, or so.

    If you’ve gotten screwed by a hard drive (or SSD) that bitrots away in like 5 days or something awful (maybe someone dropped the hard drive and the head scratched a ton of the data away), then there’s nothing you can really do about that.


  • Wait, what’s wrong with issuing “ZFS Scan” every 3 to 6 months or so? If it detects bitrot, it immediately fixes it. As long as the bitrot wasn’t too much, most of your data should be fixed. EDIT: I’m a dumb-dumb. The term was “ZFS scrub”, not scan.

    If you’re playing with multiple computers, “choosing” one to be a NAS and being extremely careful with its data that its storing makes sense. Regularly scanning all files and attempting repairs (which is just a few clicks with most NAS software) is incredibly easy, and probably could be automated.