• 0 Posts
  • 141 Comments
Joined 9 months ago
cake
Cake day: August 21st, 2024

help-circle
  • lime!@feddit.nutoAsklemmy@lemmy.mlTTRPG mechanics doubt
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    8 hours ago

    sounds something like call of cthulhu rules.

    If you successfully use a skill during play, without the help of Luck points, mark the box next to it. Between scenarios, you get to roll to improve any skills you marked. To improve the skill, roll 1d100. If you roll higher than your skill, it improves by 1d10. After you’ve rolled for all the marked skills, erase the marks.

    personally i think xp is too fiddly. i prefer systems like fate where you can just rewrite skills to fit your style of play better.





  • lime!@feddit.nutolinuxmemes@lemmy.worldRequirements
    link
    fedilink
    English
    arrow-up
    4
    ·
    10 days ago

    x86 starts with the 8086, which is 16 bit. AMD64, IA-64 and x86-64 are all both 64-bit and x86.

    when referring to specifically 32-bit x86 it’s common to use the terms i386 or IA-32, but i think just “32-bit x86” gets the point across more clearly. if you need more specificity, just mention which processor you have and people can figure it out from there.











  • you’re calculating the sha256 (i think) hash of the previous transaction block’s hash plus your block of transactions. What’s making it proof-of-work though, is the stipulation that “the hash has to start with at least five zeroes”, with “five” being an adjustable difficulty value. To be able to get that specific hash an otherwise meaningless number (a “nonce”) is included, and by increasing this number by one you can change the hash value.

    so basically, all these servers are running hash calculations on the same thing over and over again with a single number changing between runs until they get an “approved” hash value. whoever gets there the fastest gets their block added to the chain, then everyone else has to start over with that hash as the “previous” one.

    It’s called “proof of work” because it’s difficult to find a suitable value, but it’s trivial to check that it’s correct. you just need the nonce. so by presenting that nonce to everyone, you’ve proved that you “did the work”.

    as for the reason why they do this, if each block’s hash is dependent on the hash of the block before it, it means the entire chain is resistant to tampering. you can’t insert a block in the middle without recalculating the entire chain.