It's gonna be so great getting old with them running the world.
Based on the current situation, why do you think they will run anything? From the currently available data, the oldest fucks (then, we) will run the show until they (we) fall over dead (and sometimes beyond, looking at Moscow Mitch).
This isn't really the usecase, you'd be better off just playing it with VLC from a BD/DVD drive with the menu plugins. Netflix won't have DVD menus either. Ripping is necessary for this to make your physical copies accessible via Jellyfin. May want to check ARM (Automatic Ripping Machine) to streamline the process. Legally, this is perfectly fine in most jurisdictions, because you are creating a backup of your purchased property.
Can you share more info on this? I'm interested in the technical aspect how this is done, specifically which devices it uses?
For instance, say, a smart speaker, may have Bluetooth and WiFi, but I'm not sure any halfway comprehensive network stack I'd even implemented that could be used as a proxy, let alone autonomously remotely reconfigured to do so.
I get this, but european Brands lobbied to not implement or stifle the supply chain transparency laws, soooo... none of them guarantee "no slave labor" either. Actually, given their opposition to the laws, it's reasonable to assume they indeed use slave labor too. So what does that leave the end buyer with?
I do not know for sure, but the repo did contain the dependency litellm with version specifier >=1.65.0 (if I recall correctly) and an early march build did use the version 1.81.0 per the uv.lock (version before the compromised litellm==1.82.7 and litellm==1.82.8 )
Not saying that the Dev was compromised, but it is possible, and it could be some Github precaution to disable repos with that dependency where a pip install at the wrong time could have compromised all the Devs credentials.
Their exact location cannot be pinpointed; instead, they exist in a probability cloud where they are likely to be found at any given time.
That's what this hype cycle is founded on. If I lend you $5, you have $5 you can lend further. Now, we each still have a right to $5, so we can lend that debt obligation again for $4.50. Now we have, somehow, a market value of $19.
After leaving reddit, i've kept an account. Every so often I go on there and generate some slop and post it. Usually run it through 2 models, at least one obscure HF one. So far, nobody noticed.
These paid advertisements articles are funny, because they basically just admit they can't tell the difference and are publicly stating this. Heh, slopgobblers
Adding to this (which is a solid recommendation and answer BTW), you can try out podman kube play <your-file>.yaml(see here) before going full k8s or k3s setup to familiarize yourself with the concepts, without moving too far away from the docker-compose ease of use.
Regarding question 1, any distro works, but if your are looking specifically for a lightweight, fast to deploy node host os, I recommend opensuse microOS/leap micro or similarly, fedora coreOS. With both you can drop a combustion/butane/ignition config file in a usb installer partition, so you can quickly integrate fresh installs in your cluster (ssh, network config, user accounts, package installs) see https://opensuse.github.io/fuel-ignition/
Likely not. This is a spectacularly dumb move, the product isn't that good and Samsung / SK Hynix are high if they think they they'll get paid if the market so much as sneezes and things go sideways
Fair enough, that's true. I guess my gripe is with the narrow use case and the debugging and/or prompt/context tuning to get what you want. I still feel that if you don't get what you want on the first try, it's faster to write it yourself than spending time "debugging" the input and maybe get a 60% chance on correct output, which in most cases, still needs debugging. And god forbid, a framework is rewritten.
I just wished it was a bit better before we hit the plateau of diminishing returns.
TBH, it's not really that great at that. Is average at best and grossly misleading and flat out wrong at worst. It may bring slight speedups for average development on boring legacy enterprise code, but anything really novel and interesting? Detrimental.
A backdoor for you is a backdoor for me.
Do it. It'll be fun to wreak havoc on the financial institutions. Let's randomize those numbers.