Eskating cyclist, gamer and enjoyer of anime. Probably an artist. Also I code sometimes, pretty much just to mod titanfall 2 tho.

Introverted, yet I enjoy discussion to a fault.

  • 0 Posts
  • 238 Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle




  • Flawless Advance can now be interrupted. Shining Wonder’s bounce range was nerfed. Kinetic Pulse was made less annoying. Smoke Bomb T3 no longer provides invincibility, which allowed Haze to play like she had three counterspells. Shiv’s Killing Blow no longer auto-targets and must be aimed. Vindicta’s flight duration was reduced. Wardens ult isn’t as invincible anymore (it now only has resists during channel). Silvers ult now has an actual cooldown.

    Victor did get buffed. In exchange his survivability was nerfed and he is now easier to kill. He has more burst, but less of the sustain that makes him so annoying. It’s not enough yet, but I approve of the direction.

    Calico was changed so as to be less annoying to play. She’s likely to be nerfed again as the stats come in, but Valve won’t know by how much before the mechanical changes made to her kit see real play.

    All in all, multiple things that were unfun, have been addressed. There will always be stuff that is annoying. But IMO, there are now less of them.




  • I’d like you to realize that “the USA who is the least likely country to implement these laws” is literally the opposite of current reality.

    They are making some of the greatest efforts to make legally mandated user and age tracking a thing, as well as legally mandated user identity based content-gating.


  • So this is not a concern to you?

    The fact that there are people in leadership positions that want this, and have reasons why they want this, is below note. And not worth opposing?

    This will lead to infrastructure, that should not exist, existing.

    That it can be avoided is not a solution. It should not be built in the first place.


  • Is your argument really “this won’t affect linux, so it doesn’t matter” ? At the very least, FOSS development by anyone in California will be a problem, as the law quite literally names “persons” as potentially liable.

    The reality remains, the US is the most thirsty for this kind of thing. Not the least.

    And they are already working on an even more overreaching version that will close loopholes in the current legalese.


  • Windows, and any other OS will be illegal in California unless it implements this.

    Apple, for one, is headquartered in California.

    So, the OS wont work until the user verifies their age somehow.

    Moreover, even if an OS somehow could know the users age - that doesn’t automatically mean all other software that exists automatically reads it and responds to it as necessary. Does the law compel anyone making software to recognise this?

    Did you not read my comment? Anyone writing software for an OS that implements this, can be sued (in California) if their application ignores the API signals from the OS and allows access to age-restricted content.

    Or is your argument really “this won’t affect linux, so it doesn’t matter” ? At the very least, FOSS development by anyone in California will be a problem, as the law quite literally names “persons” as potentially liable.

    The reality remains, the US is the most thirsty for this kind of thing. Not the least.


  • You may want to look into what the legal requirements actually are, and how it changes who is liable. It is outright draconian.

    Essentially, it requires the OS to find out the age of the user, and then inform ALL software that is run by API. Any software that theoretically could use the data, and still allows a child to see something they should not have, will be liable.

    You claimed that the US was the least likely to do this sort of thing…

    Instead, despite the incompetence, they are clearly spearheading this globally along with the UK. Making it most decidedly the first place that will have to deal with this crap.

    Not the last.





  • It combines capacity without any fancy striping. It can still provide some performance benefit as different blocks of the same file can be stored on different drives, but it doesn’t stripe data across the drives for performance.

    It also allows you to just add more drives later. The drives don’t need to be the same size or type. You can also remove drives, provided there is enough free space to move the data on a drive to the ones that will remain.

    It really just pools the storage capacity into one big volume.

    If a drive fails, it still takes the whole volume with it tho. But as long as you monitor smart, it is fairly simple to try ejecting a failing drive from the device group before it takes the whole thing with it.



  • MentalEdge@sopuli.xyztoLinux@lemmy.mlSeeking guidance on BTRFS RAID
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    21 days ago

    If you just want to combine their capacities, and don’t need redundancy, just use single mode?

    No need to use a raid mode for multi-device btrfs.

    Edit: You could also do two volumes.

    Split each drive in half. Use the first half of each drive for a raid1c2 volume to get 1.5TB of redundant storage for important data.

    Use the second half of each drives for a raid0 volume to get 3TB of faster storage for games.