If we find out “I do not consent” opts out, I’m fine with it.

That’s exactly what it does. I got the prompt on my system, I said no, and it said ok and everything proceeded on like normal.

I’ve always wondered - and figured here is a good a place to ask as anywhere else - what’s the advantage of object storage vs just keeping your data on a normal filesystem?

We tried the first half and they all shot each other, mission accomplished?

Agreed. I’ve also been very impressed with Perplexica (linked to a self-hosted LLM on Ollama). It ties into SearXNG and will perform web searches, dive into the results, and summarize what it finds. Not just the pages themselves, but the specific information on those pages that addresses your original questions, including references which link back to the pages that were used to generate the summary. It’s easy to identify hallucinations when it links to the specific page where it got the information from (though I have yet to experience any hallunications with Perplexica yet).

Syncthing could be used to replicate a directory somewhere, but that doesn’t address backing up the phone itself (apps, settings, SMS messages, etc.). Only option I’m aware of is iCloud. You can connect the phone directly to iTunes on a computer and back it up that way, but that only works with a hardwired USB connection and can’t be automated, so it’s a non-starter for a regular backup system. Android probably has more options, I’m referring to iOS specifically here though.

Agreed, but most people don’t backup at all. Then complain very loudly when they lose everything and blame everyone else other than themselves. Saw it daily fixing people’s phones.

I’d love to back up my phone locally, if there was an option, but AFAIK there isn’t, so I’m stuck. This is a problem with companies forcing you into their cloud ecosystem and removing your ability to bypass it and control things yourself. It’s only getting worse.

How about XPipe?

https://xpipe.io/

It can even auto-configure itself by parsing out your ~/.ssh/config so you can keep everything defined there for easy CLI access but also use the GUI when desired.

Trying to find common ground between the rational and the batshit insane, is a futile endeavor.

Just FYI - you’re going to spend far, FAR more time and effort reading release notes and manually upgrading containers than you will letting them run :latest and auto-update and fixing the occasional thing when it breaks. Like, it’s not even remotely close.

Pinning major versions for certain containers that need specific versions makes sense, or containers that regularly have breaking changes that require you to take steps to upgrade, or absolute mission-critical services that can’t handle a little downtime with a failed update a couple times a decade, but for everything else it’s a waste of time.

How about Dawarich?

https://github.com/Freika/dawarich

I haven’t used it myself, but I have it in the backlog of things to try out

I had something almost identical to this happen to me on Friday. Last year our company moved to a super locked down version of Teams, to the point where I couldn’t even open images that people put in the chat because of security issues, instead the image they posted would be replaced with an error image saying that I wasn’t allowed to open images, blah blah blah. That problem was resolved a long time ago though.

On Friday I was trying to send an image of some data processing to a colleague, and every time I put it in Teams, it would show up as that stupid error message. I spent a solid hour trying to figure out why that problem was back, was my computer not authenticating with MS properly, etc. Turns out my file browser was sorting by time order instead of reverse time order, and the screenshot at the top of the list from May 2 2024, was a screenshot of the error message that I used to send to IT when they were investigating the problem.

I haven’t finished it yet, but Archimedes Engine by Peter F Hamilton has been really interesting so far

Edit: and if you haven’t read them yet, Dragon’s Egg by Robert L. Forward and Project Hail Mary by Andy Weir are both really good

I’ve never understood this. You guys know you can have multiple Firefox windows, right? What’s the point of tab groups when you can just group related tabs in a different window? Between multiple workspaces, multiple monitors, and multiple browser windows, I never feel the need to have more than 5-10 tabs open on any one of them at a time. More than that and I’m clearly doing something wrong and need to clean up anyway.

They likely streamed from some other Plex server in the past, and that’s why they’re getting the email. The email specifically states that if the server owner has a plex pass, you don’t need one.

I got the email earlier today and it couldn’t be clearer:

As a server owner, if you elect to upgrade to a Plex Pass, anyone with access to your server can continue streaming your server content remotely as part of your subscription benefits.

I run all of my Docker containers in a VM (well, 4 different VMs, split according to network/firewall needs of the containers it runs). That VM is given about double the RAM needed for everything it runs, and enough cores that it never (or very, very rarely) is clipped. I then allow the containers to use whatever they need, unrestricted, while monitoring the overall resource utilization of the VM itself (cAdvisor + node_exporter + Promethus + Grafana + Alert Manager). If I find that the VM is creeping up on its load or memory limits, I’ll investigate which container is driving the usage and then either bump the VM limits up or address the service itself and modify its settings to drop back down.

Theoretically I could implement per-container resource limits, but I’ve never found the need. I have heard some people complain about some containers leaking memory and creeping up over time, but I have an automated backup script which stops all containers and rsyncs their mapped volumes to an incremental backup system every night, so none of my containers stay running for longer than 24 hours continuous anyway.

People always say to let the system manage memory and don’t interfere with it as it’ll always make the best decisions, but personally, on my systems, whenever it starts to move significant data into swap the system starts getting laggy, jittery, and slow to respond. Every time I try to use a system that’s been sitting idle for a bit and it feels sluggish, I go check the stats and find that, sure enough, it’s decided to move some of its memory into swap, and responsiveness doesn’t pick up until I manually empty the swap so it’s operating fully out of RAM again.

So, with that in mind, I always give systems plenty of RAM to work with and set vm.swappiness=0. Whenever I forget to do that, I will inevitably find the system is running sluggishly at some point, see that a bunch of data is sitting in swap for some reason, clear it out, set vm.swappiness=0, and then it never happens again. Other people will probably recommend differently, but that’s been my experience after ~25 years of using Linux daily.

The bottom hits when all (or most) of the bad news is on the table. People know what’s happening and what the future looks like. It doesn’t happen when the pain is gone, just when people know what that pain will look like for the foreseeable future. For example, in 2022 the bottom happened when rate increases started to slow down, not when they stopped completely, just when inflation was starting to level off and we dropped from .75pt hikes to .5pt and people could see a path forward.

We are not at that point yet in the current crash, nobody has any idea how bad it’s going to get, none of the indicators show the problems yet because they’re all lagging, and consumers haven’t been hit yet by the high prices and supply chain crashes because manufacturers and retailers are still running off of back stock.

I could be wrong of course, but I don’t think I am.

Way too early. We haven’t even begun to see the results of these policies yet. Inflation results don’t yet take tariffs into account, the mass layoffs that are currently happening don’t show up in unemployment stats yet, the massive GDP shrinkage isn’t showing up yet, supply chains that are in the process of crashing haven’t yet affected consumers. This is a dead cat bounce, which literally every single crash in history has, and every time there are people shouting that the pain is over and now is the time to buy back in, right before the bottom drops out.

Market self regulation assumes informed consumers that are smart enough to know what things mean

Not just smart enough, but informed enough. That means every person spending literally hundreds/thousands of hours per week researching every single aspect of every purchase they make. Investigating supply chains, performing chemical analysis on their foods and clothing, etc. It’s not even remotely realistic.

So instead, we outsource and consolidate that research and testing, by paying taxes to a central authority who verifies all manufacturers keep things safe so we don’t have to worry about accidentally buying Cheerios that are laced with lead. AKA: The government and regulations.

I self-host Bitwarden, hidden behind my firewall and only accessible through a VPN. It’s perfect for me. If you’re going to expose your password manager to the internet, you might as well just use the official cloud version IMO since they’ll likely be better at monitoring logs than you will. But if you hide it behind a VPN, self-hosting can add an additional layer of security that you don’t get with the official cloud-hosted version.

Downtime isn’t an issue as clients will just cache the database. Unless your server goes down for days at a time you’ll never even notice, and even then it’ll only be an issue if you try to create or modify an entry while the server is down. Just make sure you make and maintain good backups. Every night I stop and rsync all containers (including Bitwarden) to a daily incremental backup server, as well as making nightly snapshots of the VM it lives in. I also periodically make encrypted exports of my Bitwarden vault which are synced to all devices - those are useful because they can be natively imported into KeePassXC, allowing you to access your password vault from any machine even if your entire infrastructure goes down. Note that even if you go with the cloud-hosted version, you should still be making these encrypted exports to protect against vault corruption, deletion, etc.