That was my point

If it’s for more than a minute I’ll screw in VGA and DVI cables

20 years ago there were 2000000000 fewer people in the world.

To send to the same account?

I haven’t paid anything for it

As long as there are no problems with the btrfs code? Hahahahaha!! There are.

It was forked but somehow lacked a huge amount of functionality that Emby had (and still has) Like I think it only supported films, not music or TV shows. The app infrastructure was awful across fire stick, Roku and android and wasn’t backward compatible with the Emby apps. I just didn’t see the point of forking it if you’re just going to make it worse or only address the server side and neglect the clients. The whole thing has to work together with good clients and server.

Last time I tried it it was a much worse experience than Emby across all devices and for all media types. I don’t understand all the love it gets.

I do play and I absolutely guarantee any guitar I would try assemble would play so so badly. Setting up a guitar is an exercise in precision engineering with wood.

KDE Connect

Signal

Email

Using Eternity and very happy with it, just as I was when it was Infinity for Reddit.

Everyone saying it’ll be fine is speaking theoretically. Practically I can attest to full and total file system corruption under this scenario.

BTRFS deciding it’s corrupt and refusing even read only access.

Edit: You beat it by trashing the disk, using any other file system, restoring from backup and accepting any losses.

Careful. You might get hit by a bus.

I gave up trying to setup a Mastodon server in docker. Lemmy was pretty tricky at the time as the docs were wrong. My email server was a bit tricky, but I’ve not really done much to tinker with it in the proceeding 6 years, so was worth it.

I have it as ls -alFh

Another thing that makes no sense is if my ISP provided prefix changes -which it will- this affects the IP addressing on my local network. Ain’t noboby got time for that if you’re managing a company or having anything other than a flat home network with every device equal.

IPv6 is just people shouting NAT BAD, but frankly having separate address ranges inside and outside a house is a feature. A really really useful feature. Having every device have a public IP6 address I’d an anti-featute.

On my local network I want governance over my devices. I want specific firewall rules per device, so I can, for instance, block YouTube only on the kids devices. I want this to be centrally managed, so configured on my opnsense router. I want all devices to use IP6. Unfortunately none of this is possible.

To setup firewall rules I need DHCPv6, not SLAAC so my IPs on my local network that I manage are well known and fixed. Android devices don’t support DHCPv6. And the designers of IP6 were daft enough to set the priority of IPv4 above that of their new protocol. So basically if you have any IPv4 addresses on a device, they’ll be preferred by basically all operating systems - because that’s what the spec says. So you can’t run dual stack in a meaningful way.

TL;DR: IPv6 on a local network has not been thought through at all even though it’s incredibly old, it’s really immature.

I’ve lived in 14 different houses. I can’t remember any of the moves being particularly bad. Hard work, yes. Have had a couple of sofas not get through doors. Worst related thing was moving into first unfurnished place and assembling the new wooden bed on day 1 with a manual screwdriver that wrecked my hands and left me exhausted. Next day I bought an electric screwdriver and it’s remained one of my top purchases of all time.

ll

df -h

du -sch

Ctrl+r