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

help-circle
  • Oh, make no mistake; prior FS games have no modding support. In fact, they encrypt the all game files with RSA nowadays (which is awful for read speeds because RSA is slow but whatever). Current modding support is based off of a robust reverse engineering community that’s documented most of the file formats and a significant portion of the important code. And that’s while contending with Arxan which, while not as awful as Denuvo, still impedes RE. They’d basically have to implement something as draconian as Denuvo to make things more difficult than they are.





  • I’d be interested in setting up the highest quality models to run locally, and I don’t have the budget for a GPU with anywhere near enough VRAM, but my main server PC has a 7900x and I could afford to upgrade its RAM - is it possible, and if so how difficult, to get this stuff running on CPU? Inference speed isn’t a sticking point as long as it’s not unusably slow, but I do have access to an OpenAI subscription so there just wouldn’t be much point with lower quality models except as a toy.



  • This is a use-after-free, which should be impossible in safe Rust due to the borrow checker. The only way for this to happen would be incorrect unsafe code (still possible, but dramatically reduced code surface to worry about) or a compiler bug. To allocate heap space in safe Rust, you have to use types provided by the language like Box, Rc, Vec, etc. To free that space (in Rust terminology, dropping it by using drop() or letting it go out of scope) you must be the owner of it and there may be current borrows (i.e. no references may exist). Once the variable is droped, the variable is dead so accessing it is a compiler error, and the compiler/std handles freeing the memory.

    There’s some extra semantics to some of that but that’s pretty much it. These kind of memory bugs are basically Rust’s raison d’etre - it’s been carefully designed to make most memory bugs impossible without using unsafe. If you’d like more information I’d be happy to provide!









  • sleep_deprived@lemmy.worldtoMemes@lemmy.mlThis community lately
    link
    fedilink
    arrow-up
    62
    arrow-down
    4
    ·
    1 year ago

    Typically this thinking is mostly correct - e.g. Manifest v3 - but not in this case. If websites see enough users using chormium, via user agent or other fingerprinting, they’ll be more willing to require WEI. And unlike Manifest v3 etc. this affects the whole web, not just users of one browser or the other.

    In every case monopolies are bad. Including in tech.