MostlyGibberish

I switched to buckwheat pillows a few years ago and I've been a fan. It's a really interesting texture that you can move and shape really easily, but then when you apply pressure to it, it firms up and holds its shape. So, you get a really supportive pillow that's molded to your head and neck (For reference, I'm a side sleeper). The only downside I've noticed is the filling degrades relatively quickly, and after about a year it loses a lot of its volume and doesn't hold its shape as well, so you'll need to replace it. The bright side is that it's fairly cheap, and entirely biodegradable.

In a few days I'll be moving to a new state to be closer with my long distance girlfriend of a year. I've been feeling pretty directionless and stuck for a long time now, so I'm looking forward to being able to start a new chapter of my life.

Android has a similar feature. It's called "Lockdown mode" on the shutdown menu. Locks the phone and turns off any biometric unlocks.

Not as long as there are minorities to blame for everything.

The only thing stopping them is the fact that anyone who wants the data can just utilize the federation protocol to take any data they want, and there's not a lot anyone can do about it. You can't sell something that's trivial to get for free.

If the question you're really asking is "what's stopping content on Lemmy/Mastodon/etc from being used to train an LLM?" the answer is, nothing.

Definitely a consideration. In my case, the vast majority of my services are running in docker on a single host box, including the reverse proxy itself (Traefik). That unencrypted traffic never goes out over a wire, so for now I'm not concerned.

I'm not super paranoid about security, but I do try to have a few good practices to make sure that it takes more than a bot scanning for /admin.php to find a way in.

• Anything with SSH access uses key-based auth with password auth disabled. First thing I do when spinning up a new machine
• Almost nothing is exposed directly to the Internet. I have wireguard set up on all my devices for remote access and also for extra security on public networks
• Anyone who comes to visit gets put on the "guest" network, which is a separate subnet that can't see or talk to anything on the main network
• For any service that supports creating multiple logins, I make sure I have a separate admin user with elevated permissions, and then create a non-privileged user that I sign in on other devices with
• Every web-based service is only accessible with a FQDN which auto-redirects to HTTPS and has an actual certificate signed by a trusted CA. This is probably the most "paranoid" thing I do, because of the aforementioned not being accessible on the Internet, but it makes me happy to see the little lock symbol on my browser without having to fiddle around with trusting a self-signed cert.

Right. If you want to debate with people you have a rapport with, great. But if you're just being a contrarian and only talking about why you don't like something other people enjoy, they're gonna think you're a dick.

Spotify is the only service I actively use. I'm not big on music fidelity, so for my purposes, it provides value.

The Hulu and Disney+ bundle because my mom and girlfriend use it, and it's not worth convincing them to use my Jellyfin server.

Prime Video, just because I have Amazon prime, but I don't think I even have the app installed on any of my devices.

These days, if I'm watching something on my own, I don't even bother looking for it on streaming apps. I just legally acquire a Blu-ray copy and add it to Jellyfin.

Right, but he was (allegedly) killed by another rich, connected, corrupt person to stop him from taking anyone else down with him. Which adds another wrinkle to the whole thing. When you try to hold someone like that accountable, they kill you and get away with it.

One of the things I like about containers is how central the IaC methodology is. There are certainly tools to codify VMs, but with Docker, right out of the gate, you'll be defining your containers through a Dockerfile, or docker-compose.yml, or whatever other orchestration platform. With a VM, I'm always tempted to just make on the fly config changes directly on the box, since it's so heavy to rebuild them, but with containers, I'm more driven to properly update the container definition and then rebuild the container. Because of that, you have an inherent backup that you can easily push to a remote git server or something similar. Maybe that's not as much of a benefit if you have a good system already, but containers make it easier imo.

I've always been hesitant to host any services on a device with a non-removable battery. Having a battery constantly charging and discharging isn't great for it and could potentially be a fire hazard. I know modern devices have gotten much smarter about how they charge, so maybe it's not as much of an issue anymore, but still something to be aware of depending on how old your phone is or how you modify the firmware.

Personally, with how cheap you can find a mini PC or SBC, I would just save up a bit (maybe even sell the device you're planning to host on) and keep an eye out for deals. You're going to get a lot more freedom and power with those devices, and not have to try to hack around the limitations of a mobile OS.