Does the B70 definitely support SR-IOV from day one?

Anecdotally, comparing to recent (but still older than these) generations of Intel chips I can run my M2 Max MacBook Pro with 78% battery health for longer (without any special considerations) than colleagues running their Windows Intel laptops in Power Saver mode, while performing similar tasks.

I work in an office, but Swedish law protects blue- and white-collared jobs the same in this regard.

Apex Legends at least was running fine on Steam Deck prior to november 2024 when they instituted this change, and I can tell you from personal experience it had very little impact on cheaters, which was their excuse for the change (supposedly most cheaters were connecting via Linux clients).

The oldest iPhone OS that natively boots on my particular one is 1.1.4, 1.1.1 (which is the highest version number where you can trivially escape the OOBE via the emergency dialer) fails to initialise the FTL (flash translation layer), probably because the chip is sufficiently different from that used in the older phones.

It would bring me great joy to be able to relive emergency dialer hacktivation again, but I have lost that particular iPhone 2G, and only have this 16GB one left.

Also, if I want to add another domain that should be accepted and reverse proxied to my application, in Caddy I just do this:

    example.com wp.example.com caddyfreakingrules.example.com {
      root * /var/www/wordpress
      php_fastcgi unix//run/php/php-version-fpm.sock
      file_server
    }

Another thing, does nginx with the above configuration automatically load new certs if the ones that were there when the process spawned have since expired? Because not only does Caddy automatically renew the certs, it is handled transparently and there's zero downtime (provided nothing changes about the DNS pointers of course).

Caddy is freaking awesome!

Bonus, if this were your Caddyfile (the entire thing, this is all that's needed!):

    {
      admin off
      auto_https prefer_wildcard
      email hostmaster@example.com
      cert_issuer acme {
        dir https://acme-v02.api.letsencrypt.org/directory
        resolvers 1.1.1.1 1.0.0.1
        dns cloudflare {env.CLOUDFLARE_API_TOKEN}
      }
      ocsp_stapling off
    }

    example.com wp.example.com caddyfreakingrules.example.com {
      root * /var/www/wordpress
      php_fastcgi unix//run/php/php-version-fpm.sock
      file_server
    }

    # This is simply to trigger generation of the wildcard cert without
    # responding with the Wordpress application on all of the domains.
    *.example.com {
      respond "This is not the app you're looking for" 404
    }

The result of which is that Caddy will only generate one cert for the above 3 sites, and Let's Encrypt won't leak the existance of the wp.example.com and caddyfreakingrules.example.com domains via certificate transparency.

Also, adding features on its own is great, but obviously stuff like what happened here can't be allowed to happen, and those Samsung or LG smart fridges that became advertising boards is obviously also not acceptable...

Easy to call the bullshit out, hard to actually define the responsibilities of a manufacturer in a law.

I'm donating to them and hoping they eventually get those implemented.

This is what bcachefs is based on.