![](https://programming.dev/pictrs/image/385658d9-e355-4571-a811-b0d61d6dbc9d.jpeg)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
64 for the wan interface
Nitpicking, but the address for the wan interface wouldn’t have a prefix, so the host would just set it as a /128 (point-to-point)
64 for the wan interface
Nitpicking, but the address for the wan interface wouldn’t have a prefix, so the host would just set it as a /128 (point-to-point)
I used to use it, but then I switched to MPV, as it works a lot better with hardware acceleration. MPV supports more methods for hardware decoding (e.g. nvdec), and also MPV will keep the frames in VRAM when doing hardware decoding, and do additional processing and presentation using the GPU, while VLC copies everything back to system RAM and processes the frame on the CPU.
At the time I switched hardware decoding with copy-back would actually result in twice the CPU usage compared to software decoding, but that was a long time ago. Also, I would get tearing in VLC and not in MPV.
Something with OpenWRT. Turris Omnia is pretty good.
You’re right, that might work
That requires root
Sounds like a typical COBOL dev
Could be that the graphics card is outputting an HDR signal (Rec. 2020 color space), but the monitor is in SDR mode. That would result in desaturated colors.
Already daily driving it on my laptop, which uses AMD graphics, and my work laptop, which uses Intel graphics. For Nvidia, there’s missing explicit sync (which should be fixed soon), and Steam completely freaking out (might get fixed by explicit sync). Kwin also seems a bit unstable on Nvidia, but I haven’t tested it for extended periods of time.
I also have a computer with display on an Nvidia card via reverse prime, which suffers performance issues on Wayland. Might be improved on Plasma 6, but that computer runs OpenSUSE Leap, so it won’t get that for some time.
There is also the issue of picture-in-picture, but that can be worked around with Kwin rules.
That doesn’t say that. Although the article linked from there does, for Pixels.
And thanks to specialized Pixel hardware, Pixel 8 and 8 Pro owners will also be able to find their devices if they’re powered off or the battery is dead.
Have they done anything about the lack of security? Last I checked, anyone could mount an NFS share and access it as whatever user they wanted, without authentication.
Where is that mentioned? I can’t find that in the article
That though would make it break when the host system updates glibc, just like it does in snappy.
The GDPR has nothing to do with copyright
How can it tell the difference between spaces used for indentation and spaces used for alignment, if you use the same character for both?
I get horizontal scroll even if I view the post on lemmy.world though
Huh, I guess must be something dependent on the client. On the web I can scroll horizontally in the code box instead:
What’s so hard to read about that?
What do you mean by “attach an audio to an image”?
Yes, though OpenSSH has already switched to a quantum resistant algorithm for key exchange (Streamlined NTRU Prime, combined with x25519 in case SNTRUPrime turns out to be weak), and that’s the stuff that needs to be switched as soon as possible to preserve forward secrecy. Authentication keys are less urgent.
It’s better in one way, in that updates are applied on reboot rather than pulling the rug put from under running applications. But I agree that it doesn’t go all the way, as it doesn’t provide a verifiable base system with clearly separated modifications. OSTree would be great.
Another possibility would be to distribute a base image as a btrfs send stream (possibly differential against previous versions) containing a compose-fs image and associated files. And then OS extensions could be installed with systemd-sysext.