mlfh

https://grapheneos.org/faq#device-lifetime

You can buy a used Pixel 8 and it will be supported by Graphene through 2030 at the very earliest, probably the best support lifecycle you can possibly get on a phone.

Ctrl+r was a life-changer when I first learned it.

There should be a section in the configuration about dhcp, which is how ipv4 addresses are given out on your network. What happens is when a device first connects to the network, it sends out a broadcast with its mac address - the dhcp server (in this case, your router/firewall) hears this, and sends back a reply allocating an address. You should be able to see a list of currently allocated addresses, and hopefully configure reservations to make those allocations permanent. To reserve an ipv4 address for a specific device, you need that device's mac address.

Each item on that current allocations list should have a hostname, a mac address, and an ipv4 address. If it's not clear by the hostname which device is the tv, you can look up each mac address and deduce from there (the first part of each address is unique to a specific manufacturer).

Once you have an ipv4 address reserved for the tv, you can set your outbound firewall rule to block it.

Ipv6, as I mentioned, is much more complicated. It might be possible to disable it completely on your router, and that's likely the only way to block the tv from using it, but then your whole network will lose ipv6 capability across that boundary (probably not a lot of downside to that, though).

Good luck!

If your firewall can set outbound rules, and you can control DHCP on your network so that you can reliably know the TV's IPv4 address, you can block the TV from reaching beyond the local network there with a "deny all from source address of TV" type rule.

If your router/firewall is handling IPv6 though, it gets a lot more complicated, since the TV could have any number of addresses that change often.

When it comes to privacy and security, I think you should treat all cloud providers equally. Use a client with client-side encryption so that the only thing that touches the provider is encrypted data.

Rclone is an example of a good client that can do this, and can even mount your cloud storage as a filesystem with its encryption layer in between.

I'd recommend a full battery calibration before running the command one more time, if you haven't already (charge the battery fully, leave it on the charger at 100% for a while, then fully discharge until it shuts itself off, leave it for a bit, then fully recharge while off). If the calibrated values line up with a full:design ratio of ~80%, especially with a 10-year-old battery with almost 700 cycles on it, my take is that's pretty great.

That said, I think the best way to get an accurate feel for the health of an old battery is to put it through one full cycle of normal use and time how long it takes to die.

"Another aspect they tested was the effect of combining LSD and isolation, where the subjects would be dosed and isolated for months at a time with minimal food and water."

Straight-up fucking evil.

Best gun-pants ergonomics, tucked in the front

If you're genuinely worried about this, you shouldn't be using untrusted machines for remote access.

Apache Guacamole might be a good option. "Clientless" (browser-based), supports various mfa, uses ssh/vnc/rdp on the backend.

However, if the data on that machine is sensitive, or if that machine has access to other sensitive things on your network, I'd suggest caution in allowing remote access from untrusted machines on the wider internet.

The resolution is actually quadrupled by doubling the value of both axes. In this case going from 1500x1424 (2.1MP) to 3504x3327 (11.7MP) multiplies the total number of pixels by 5.4

With the same level of jpeg compression you'd expect it to jump from 700KB to roughly 4MB. Since both images are the same file format, the rest of the file size difference is likely attributable to less jpeg compression being used in the larger image.

He volunteered.