• 0 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: July 9th, 2023

help-circle
  • In theory it makes it possible for other games to use the same items to make stuff in their games (I doubt this in practice)

    I’ve heard this before, but there’s literally nothing preventing games from setting up some shared items on their own without NFTs. Nobody does it because companies want to keep their IP, and worrying about external items would be a nightmare to balance.

    NFTs solve like 1% of the problem of sharing items. So much more goes into making them actually work. For example: NFT id 5551337 is owned by the player: now what? How do you figure out what 3d model to render? What actions can you perform? How does it integrate with other systems? All of that is going to have to be custom for every game involved on a per-item basis.


  • I understand what you mean. Water vapour (i.e. clouds, fog, the visible part of what comes from boiling water which any normal person would call steam) vs Gaseous water (i.e. most of the atmosphere, and the non-visible part of boiling water also called steam).

    Vapes work by boiling PG/VG which starts as a liquid (i.e. the juice), and generates both vapourized and gaseous PG/VG. If it was water, any normal person would consider this steam. This isn’t a chemistry or physics class.





  • Well, I’m impressed they actually did test JUST the vape liquid, even though they’re still calling them e-cigs.

    Quoting from the journal itself:

    There were no significant differences in changes of BAL inflammatory cell counts or cytokines between baseline and follow-up, comparing the control and e-cig groups. However, in the intervention but not the control group, change in urinary PG as a marker of e-cig use and inhalation was significantly correlated with change in cell counts (cell concentrations, macrophages, and lymphocytes) and cytokines (IL8, IL13, and TNFα), although the absolute magnitude of changes was small. There were no significant changes in mRNA or miRNA gene expression. Although limited by study size and duration, this is the first experimental demonstration of an impact of e-cig use on inflammation in the human lung among never-smokers.

    The way I read this, it seems like there’s a small correlation with inflammation, but there’s no measurable risk of developing lung cancer from it (they were doing cancer research after all). Personally for an adult, I feel like “inflammation” is kind of a nothingburger, just stop vaping for a while and you’ll be fine. But for kids developing habits, I can understand the concern.





  • Vaping is not the same as smoking and can be done perfectly safely with no drugs involved at all (i.e. flavor only vapes). It’s barely different than inhaling steam.

    Edit: I’m willing to admit when I’m wrong, and now think “relatively safely” is a better way of putting this. There’s a few concerns that I’m perfectly happy to live with as an adult, but I get that kids won’t have spent as much time trying to understand the risks.




  • I think you’re missing the point of what I’m asking. In what way are regular salted passwords insecure? Sure you can keep adding extra steps to encryption, but at a certain point you’re just wasting CPU cycles.

    I have no doubts about Argon2 being secure, I just think the extra steps are unnecessary for anything I would build (i.e. not touching financial transactions or people’s SSNs). By design argon2 uses a lot of memory and CPU time to make bruteforce attacks much harder, but that’s more of a downside when you’re just doing basic account logins on a low end server.

    I’ll happily retract my point about external dependencies. It’s available in most languages, and notably std C++ contains neither argon2 or sha256/512 hashing, so that kind of makes my original point invalid anyway.



  • I’d rather see a paper explaining the flaws with salted passwords rather than “just use this instead”.

    My initial reaction is that this overcomplicates things for the majority of use-cases, and has way more to configure correctly compared to something basic like a salted sha256/sha512 hash that you can write in any language’s standard library.

    If the database of everyone’s salted password hashes gets leaked, this still gives everyone plenty of time to change passwords before anything has a chance of cracking them. (Unless you’re about to drop some news on me about long time standard practices being fundamentally flawed)