

I think they should at least do an annual “Year of the Linux desktop!” episode!
I think they should at least do an annual “Year of the Linux desktop!” episode!
I wouldn’t say it has anything to do with the financial affluence of the gamer, but I agree with you that the vast vast majority of gamers simply do not care. Like with a lot of things, that same majority would be better off if they did.
Depends on the game. Apex, Riot, ubisoft, and EA all ban vm players. A list of other companies do as well.
Easy way to get yourself banned in online games just an FYI. Most online games will detect and ban virtual machines now since they’ve become commonplace in cheat/hack communities.
No, not at all, I just don’t expect the level of reliability they provide with how complex the stack is, and that is a complicated stack. (For a literal light bulb).
Reddit is dead to me, and given their stance on their apis, should be dead to pretty much all hobbiests deeply interested in self hosting.
There’s a difference between Matter (the interoperability standard) and Thread (The preferred matter communication protocol) and you’ll see a lot of devices advertised as “Matter over thread” which is important because for those you’ll need a matter bridge device to act as an edge router for the mesh “thread” network the devices create. These can be had cheaply though and if you’re one of the like 1 in 3 Americans with an iPad you already own one.
Hue do be having that “it just works” track record. Which is absolutely divine magic in my opinion because if you took one small look at their back end infrastructure stack you’d never imagine it could be… Reliable… Somehow? Like… Look at this…
I’d recommend against it. Apple’s software ecosystem isn’t as friendly for self hosting anything, storage is difficult to add, ram impossible, and you’ll be beholden to macOS running things inside containers until the good folks at Asahi or some other coummity startup add partial linux support.
And yes, I’ve tried this route. I ran an m1 mac mini as a home server for a while (running jellyfin and some other containers). It pretty consistently ran into software bugs (less maintained than x64 software) and every time I wanted to do an update instead of sudo whateveryourdistroships update, and a reboot, it was an entire process involving an apple account, logging into the bare metal device, and then finally running their 15-60 minute long update. Perfectly fine and acceptable for home computing, but not exactly a good experience when you’re hosting a service.
Wait… You want us to pay humans? - Every triple A gaming company since 2010.
Embrace. Extend. Extinguish.
Those words proved the folly of the “free as in freedom” open source many moons ago.
How I imagine you responding to your singular downvoter:
While I almost completely agree with you, never underestimate the power of using the right tool for the right job. HDMI is actually far more resilient to signal corruption in my experience than display port since it implements TMDS and the cables are more commonly well shielded since they expect them to be used in device dense environments, which isn’t really applicable to anyone familiar with technology (don’t group up your cables next to something with significant RF noise/leaks, duh.) but does matter for the end user use case these see. The fees hdmi charge are a scam though fr and we could ask better from the industry.
And a pickup of gains from sending just the delta of changed data for one of their passive update beacons.
If you have an old desktop to repurpose, jellyfin is best ran on one of those with an Intel a380 gpu as long as the motherboard supports resizable bar. Cpu-wise jellyfin doesn’t really do anything intensive, and intel’s gpus all come with the same 2x video pipelines so upgrading to a 770 wouldn’t add any performance. If you’re buying new, my recommendation would be to get one of those intel white label laptops xpg made for a while. They can be had around $300-500 and come with a intel arc gpu you can use for encoding, resizable bar, decent ram, and a decent cpu. Great little jellyfin boxes.
I see what you mean and understand you. It’s very idealistic and I appreciate the thought of it, but it just won’t apply to a modern world full of varied people in the way you wish. The reality of it is that most people simply are not interested in participating and it’s not in the best interests of any project to expect to change that. Contributions from someone who shares no passion or interest will be less qualitative at best. That’s not even to mention that you’re likely missing the forest for the trees, as most open source software is built upon hundreds of other projects. You cannot reasonably expect participation on that scale. You can encourage, desire, or structure an income stream to support it; but you cannot expect it as it’s just not rational.
Not sure what part of the open source community you’ve been diving into, but the expectation of contribution to the project is not realistic nor logical as there’s not “always” something a person can contribute and you’d absolutely run afoul of “too many chefs in the kitchen” (even Wikipedia acknowledges this and has structured editing in a way to help alleviate the issues). Though open source for me, and a lot of others, has always embodied passion, a desire to aid the community, and a drive to prevent closed alternatives. None of that is based around “co-op” style expected contribution development. Hell, even Stallman famously addressed my “free as in beer” statement, saying that open source is more akin to “free as in speech” overall, but since this particular project is not monitizing and are GPL 2 licensed, they are absolutely free as in beer.
I understand this, but we need to be reasonable and avoid extremes. This software is extensively free (as in beer) and requires development support. As long as the prompt doesn’t cross any lines into exploitive territory I think it’s fine. It would be nice for them to have explored other fundraising avenues first though and have saved this as an exhaustive “final” option.
N…not quite…