matja

* Don't rely on vendor-specific compression and/or encryption which may vary between different tape drives. * If you do use encryption, try to ensure you have a way to recover from corruption in the middle of the bitstream (see parent's point on two copies, or CTR/GCM mode, or FEC/erasure coding). * Index the contents (file names, sizes, at least), or use an archive format that puts the index at the start of the tape (note: tar does not).

Dimensional error.

Do they mean 18 GWh per day = 64.8 TJ / day = 750 MW ?

Or is this thing really going to use twice as much power as the largest nuclear power plant that currently exists?

On current GPU hardware/firmware... The cynic in me imagines in the future GPU vendors wanting to implement only loading signed weights to your card, aligned with your "subscription level", for your "safety".

Configuring my OS to prefer IPv6 addresses of DNS responses significantly reduced the number of web captchas I see (on NAT444 with native IPv6).

IPv4 is old and broken, use IPv6.

Also: https://stopdisablingselinux.com/ - SELinux can mitigate this.

curl && tar -x && ./configure && make install ? Guess what, it's the same with more steps.

    CREATE TABLE passwords (
      email VARCHAR(MAX),
      password VARCHAR(20) UNIQUE -- unique passwords are more secure.
        -- NOTE: "20" here because we used to use SHA1 hashes
        -- but there was an issue with storing binary in CP437
        -- so we just renamed the field.
    )

I suppose the subjects moved past the camera perpendicular to the lens direction, so you only see one side.

Are there any examples of what it looks like with a line scan camera when a subject goes past at an angle?

Also, for anyone setting up a tripod with a tripping hazard in public, do consider public liability insurance :)

Everything in their statement can be true and it be a bad thing for consumers of non-HBM RAM.

"HBM capacity to expand to 250,000 wafers a month"

So let's say their current HBM capacity is 100k wafers/month (pure speculation/random number for illustration), and their total RAM capacity (including HBM( is 300k wafers/month, then non-HBM capacity reduces from 200k to 50k.

Edit: e.g. the tree in one of the images in the page: https://www.dxomark.com/wp-content/uploads/2026/09/PoleHDR_D...

But then, saying while "let Some(item) = iter.next()" everytime is tedious, so they give you .iter() - for any type that is efficiently iterable.

Nothing stopping you using a manual loop that you need to update if you change the container type.

ZFS and btrfs were designed from the start to handle this, by using checksums on every piece of (meta)data and redundancy to return the same data as was stored to the kernel, and rewrite the bad data.

I've tested my own machines running ZFS by random writes out of band from the filesystem/kernel and it has always found and fixed them.

    "call_back_day": {
      "criteria": {
        "none": "The user does not want a call back.",
        "today": "The user wants a call back today.",
        "tomorrow": "The user wants a call back tomorrow."
      },
      "instructions": "When does the user want a call back?",
      "type": "choice"
    }

I think the IBM 7030 Stretch CPU (from 1964) would be a likely contender for being one of the first 64-bit CPUs.