suicidaleggroll

Fun fact, Edge still has this stupid behavior even on Linux, so highlight and middle click doesn't work properly since as soon as you highlight it pops up that stupid menu. You have to go into the menu and disable it before highlighting works correctly again.

Signed - someone who is fortunate enough to be able to use Linux on my work machine (yay!) but is still forced to use Edge on it (boo!)

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

If they can charge 30% less without Apple's fees, then why are their prices the same whether you buy on their iOS app or direct on their website? Why have they been overcharging users who don't buy through the iOS app by 30% all this time?

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

To be fair, I don't know either. I mean he's supposed to, and he swore an oath to, but if nobody is going to enforce that then must he really? What happens if/when he doesn't?

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

Yeah that's about 2 and a half round-trips between Dallas and Houston, that's...not a lot to be calling this thing ready to go and pulling out the safety drivers.

I wonder how these handle accidents, traffic stops, bad lane markings from road construction, mechanical failure, bad weather (heavy rain making it difficult/impossible to see lane markings), etc.

You'd think they would be keeping the safety drivers in place for at least 6+ months of regular long-haul drives and upwards of 100k miles to cover all bases.

Yeah unfortunately it's no guarantee that blue states are better. Many are, but not all. Colorado, California, and New York all score a 'C', still not great but much better.

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.