This is just a guess, but I’d imagine that happens because the websites use JavaScript to load the actual content of the page, but Lemmy is just parsing the HTML that is returned.

Also, I really doubt you’d have much luck convincing website authors to completely change their architecture just to get previews to work on Lemmy.

The repo owner claims to have permission from contributors to relicense (and rewrote some other parts where they couldn’t get permission?): https://github.com/stenzek/duckstation/pull/3295#issuecomment-2348988362

I don’t really understand the rest of that comment though…

Yep, I’m genuinely unsure if the conversations actually happened or not. I’ve gotten different answers to that from different people.

At work we have a contractual design deliverable that was due yesterday, I still can’t get anybody to tell me what I’m supposed to be designing/building. I’ve got the contract, but its so vague that it’s more unhelpful than it is helpful and there’s apparently been 9 months of conversations with the customer, none of which have included engineering, nor has anything from them been written down. So we’re designing something just based on rumors.

So we’re in crunch mode, but also we don’t know what we’re trying to accomplish… 😩

They may block IP addresses associated with consumer ISPs. Assuming that’s the case, I would guess you’re seeing that as an HSTS/TLS error because their network is trying to trick your browser into redirecting to/displaying an error page hosted by some part of their network.

Unless you’re working with people who are too smart, then sometimes the code only explains the how. Why did the log processor have thousands of lines about Hilbert Curves? I never could figure it out even after talking with the person that wrote it.

C was originally created as a “high-level” language, being more abstract (aka high-level) than the other languages at the time. But now it’s basically considered very slightly more abstract than machine code when compared to the much higher level high-level languages we have today.

Tell them if you have to go back to the office, you quit.

Nah, never say “or I’ll quit”, you just say you won’t go to an office. End of statement. You don’t make any sort of threat or give them an ultimatum, just set your boundaries. Make them fire you, if you’re valuable and/or well liked odd are they won’t and you just get to keep working remote.

deleted by creator

IMO, the best free option is https://freedns.afraid.org/. The biggest downside of that one is that you have to login a couple times a year (IIRC?) to keep it active. I actually still use this even though I have a paid domain, I just CNAME my real domains to the afraid dynamic name. That was easier than changing the config every time I become unhappy with my domain registrar and have to reconfigure everything after swapping.

Apex Legends is verified: https://www.protondb.com/app/1172470

The finals doesn’t work because of anti-cheat: https://www.protondb.com/app/2073850

Edit: World of Warships is playable: https://www.protondb.com/app/552990

Less commercial interest means only hobby level development

Podman is developed by RedHat: https://github.com/containers/podman/graphs/contributors

The day Firefox shutters its doors is the day the internet truly dies.

*the web

The internet has so far been doing a much better job surviving as a proper decentralized system than the web.

Unfortunately, no. Samba needs a different label. Doing that relabels things so that only containers (and anything unrestriced) can access those files.

IMO, yes. Docker (or at least OCI containers) aren’t going anywhere. Though one big warning to start with, as a sysadmin, you’re going to be absolutely aghast at the security practices that most docker tutorials suggest. Just know that it’s really not that hard to do things right (for the most part^[1]).

I personally suggest using rootless podman with docker-compose via the podman-system-service.

Podman re-implements the docker cli using the system namespacing (etc.) features directly instead of through a daemon that runs as root. (You can run the docker daemon rootless, but it clearly wasn’t designed for it and it just creates way more headaches.) The Podman System Service re-implements the docker daemon’s UDS API which allows real Docker Compose to run without the docker-daemon.

The light is visible, the flashing isn’t.

The top white rectangle is a multi-color LED (presumably RGB). Can’t make out what’s in the bottom, but I wouldn’t be surprised if it was some form of light sensor for (literally) flashing new information onto the tag.

Update the controller firmware.

I’ve got the “Xbox Wireless Controller”, the one that has a little bit of a grippy texture on the handles & the ‘d-pad on a circle’ d-pad. And I was seeing the same thing before updating the FW ~a year (maybe even two?) ago.

Unfortunately, doing that requires a Windows PC or an Xbox.

Yeah I had the exact same thought - “huh, transparent case and charging led” - but I hear they’re going to come out with an update to adjust the intensity of it, so that may help that.

Oh, nice. I’m also wondering if I can’t paint part of the light pipe so it doesn’t shine outward (as much?). Or print some sort of replacement with opaque sides. We’ll see if I ever decide I’m bothered enough by it to actually do that.

I also upgraded from OG 512 - personally love the OLED so far. Screen is really nice, battery life will be great to have on my business trips, and the clickiness of the Steam and … buttons is a definite improvement. Do you need any of these things? No… but they are really nice things.

Yep, totally agreed. Though, I finally started one of my 4 HDR games (Death Stranding) and if I knew it was going to make this much difference, I might have been clamoring for it sooner. Though, I don’t know if DS is hamming it up/designed more for HDR at the expense of the quality without it.

I upgraded to an OLED from an OG 512. I definitely don’t think it was a “must have” upgrade, but I was never really bothered by the LCD.

The only thing I have approaching a complaint, which is more of a “huh I didn’t actually think about that”, is that on the LE the charging LED shows through the transparent case from the front. I think I can probably come up with some way to fix that (or at least make it much dimmer from the front).