

In what way? I’ve been using triple monitors for close to a decade now and my KDE switched from X11 to Wayland at some point without me noticing, so I’m wondering what I missed.


In what way? I’ve been using triple monitors for close to a decade now and my KDE switched from X11 to Wayland at some point without me noticing, so I’m wondering what I missed.


Demonstrating the need for jail breaking firmware for smart TVs (and repealing the DMCA anti-circumvention clause that enforces Tivoization) in two different ways at once:


If all you want is file sharing, like the blog post author wants, I don’t understand what’s wrong with something like a plain old SFTP server.


The weaker (permissive instead of copyleft) license alone is a reason to be suspicious of both the project and OP. At this point, it’s just telegraphing plans to eventually go proprietary and enshittify.
To be fair, Github sucks at conveying that sort of info to begin with, and OP linked to a particular plugin instead of the main project. Once you actually get to the main project’s main page / README file, a “dashboard that displays your feeds” seems straightforward enough.


That’s the thing, whether or not they’re valid depends on the person you’re asking.
No it fucking doesn’t! There are people who think that, but they’re wrong.
Moral relativism is bullshit.


How to migrate your watch history, apparently: https://www.florianjensen.com/2024/08/21/how-to-migrate-from-plex-to-jellyfin/
I mean, sure, in terms of OS choice.
I think there are some other decisions that give it a run for its money if you don’t limit the scope to computing, though.


IMO the trouble is that there are so many of the things now that I need a damn flowchart to understand how they work together and which ones I need.
(No, seriously: I want to set up an *arr stack but don’t understand how. Could somebody please send me a flowchart??)
I read OP’s question as him streaming from a Jellyfin server to this box, not using this box as a Jellyfin server itself. Could be wrong, though.
Also, it’s my understanding that transcoding is 100% about hardware support for the codecs and that integrated graphics that have it (TL;DR: 12th gen Intel) are going to perform pretty much just as well as even a high-end discrete gaming GPU for that task.
(I say “gaming” GPU because I was reading about the Arc Pro B50 the other day and it has two separate sets of transcoding hardware, so it presumably would actually perform better in terms of the number of simultaneous streams it could handle. But short of something like that, it apparently doesn’t make much difference.)


They should move the “KDE Neon” name to this new immutable version.


But why? Is there really not already some other project that does that, that the dev could join instead?
I hate it when Free Software installers present the GPL as if it’s an EULA. It’s not! You don’t have to agree to it to install the software!
You only have to agree to it if you decide to do something that copyright law otherwise does not allow (e.g. redistribution of a modified version), and it is the act of doing that thing itself that signals your acceptance, no button-clicking necessary.


an i5-7500 should be faster
4 cores worth of Kaby Lake is faster than 32 cores worth of Interlagos?


Nothin’ I’m running, that’s for sure!
It’s not really that there are services that require that much processing power for a single request; it’s that it’s designed to handle normal requests for hundreds or thousands of users at once.
I suppose that supporting 0.5TB of RAM means it could deal with quite a big LLM, but any sort of halfway-modern GPU would absolutely run circles around it in terms of tokens per second, on any model that fit in their VRAM.


My drives are 3.5" 💀


It has an HBA, 3 hard drives, and 3 SSDs. I was going to add a couple more hard drives (just to try to get some more use out of old ones I had lying around), but 0.5TB ones might not have enough capacity to be worth their power draw.
Like a VM virtual disk? Those are exclusive to each VM and can’t be shared, so if you want multiple VMs to access the same data then NFS would be needed.
But containers with bind mounts don’t have that limitation and multiple containers can access the same data (such as media).
Just to be clear, are you saying that when you’re using bind-mounted ZFS pools, it’s okay to write from two containers (or both the proxmox host and a container) at the same time?
Also, I think I managed to accomplish that for a VM by creating a Proxmox Directory pointing to a path in a zpool, adding it to the VM using virtiofs, and mounting it within the VM. I’m not sure if writes from both the VM and the host are safe in that case either, though.
deleted by creator
Ah, my monitors are all identical and stay plugged in all the time, so it’s a much less complicated use-case than yours.
I do have one issue where, because I picked the wrong 9070XT on launch day and couldn’t exchange it due to lack of availability, one of my monitors is on HDMI instead of DisplayPort and takes annoyingly longer to wake from sleep or change modes than the other two. But I think that’s more likely a hardware or driver problem than a Wayland one.