Ah, sorry, I confused you for the original commenter. The first sentence is a bit nonsensical, it is a bit rude and snarky, but I meant it as a joke, since I had the wrong impression the person having issues with flatpak steam is asking about issues with flatpak steam.
I don’t have a reference, but I’ve been seeing random individuals asking for help and finally saying they fixed their issue by switching away from flatpak, so… You, I guess? Your.problem might be a perfect example of one of the many problems that keep popping up, that seem to only happen on the flatpak version.
I think you’re wrong about one thing - it’s not about compute cost, but about complexity of accounting for latency. You could check if the player can see the enemy they’re claiming to have shot, but you really need to check if they feasibly could’ve seen the enemy on their computer at the time they sent the packet, and with them also having outdated information about where the enemy was.
The issue gets more complex the more complex the game logic is. Throw physics simulation into the mix and the server and clients can quickly diverge from small differences.
Ultimately, compensating for lag is convoluted, can still cause visible desync for clients (see people complaining about seeing their shots connect in CS2 without doing damage), and opens up potential issues with fake lag.
More casual games will often simply trust the client, since it’s better for somebody to, say, fly around on an object that’s not there for other players, than for a laggy player to be spazzing out and rubberbanding on their screen, unable to control their character.
I suppose the thing I’m worried about is more general Linux SteamVR support than the streaming itself… But duh, the headset can run games on Linux standalone, so they’ve gotta have SteamVR working well. The only question is, am I behind on the news, or have they been holding back the updates internally?
I do believe they called out that the steam machine is designed to work with the frame, right? I’d have expected to see Linux SteamVR updates leasing up to this, to get it fully fixed up and tested ahead of time, though I might also have missed something…
Apertus was developed with due consideration to Swiss data protection laws, Swiss copyright laws, and the transparency obligations under the EU AI Act. Particular attention has been paid to data integrity and ethical standards: the training corpus builds only on data which is publicly available. It is filtered to respect machine-readable opt-out requests from websites, even retroactively, and to remove personal data, and other undesired content before training begins.
We probably won’t get better, but sounds like it’s still being trained on scraped data unless you explicitly opt out, including anything that may be getting mirrored by third parties that don’t opt out. Also, they can remove data from the training material retroactively… But presumably won’t be retraining the model from scratch, which means it will still have that in their weights, and the official weights will still have a potential advantage on models trained later on their training data.
From the license:
SNAI will regularly provide a file with hash values for download which you can apply as an output filter to your use of our Apertus LLM. The file reflects data protection deletion requests which have been addressed to SNAI as the developer of the Apertus LLM. It allows you to remove Personal Data contained in the model output.
Oof, so they’re basically passing on data protection deletion requests to the users and telling them all to respectfully account for them.
They also claim “open data”, but I’m having trouble finding the actual training data, only the “Training data reconstruction scripts”…
Ironic that, by upvoting this comment in agreement, I’m doing the opposite of what you advocate for…
Intentionally and knowingly calling a MTF trans person a man is transphobia. Dunno about jail, but I’d be down to have legally enforced punishment for that. To be fair, that should probably cover all cases of (intentionally and knowingly) misgendering people, in a similar fashion to defamation.
I think they decided not to, with some (IMO fairly) snarky comment on how that was just a proposal and people were getting needlesely outraged.
I don’t think either has ntsync support enabled by default, but it’s supposed to have better accuracy or performance, thanks to putting the needed APIs directly in the kernel, right?
I had the impression cloud was about the opposite - detaching your server software from physical machines you manage, instead paying a company to provide more abstracted services, with the ideal being high scalability by having images that can be deployed en masse independent of the specifics of where they’re hosted and on what hardware. Pay for “storage”, instead of renting a machine with specific hardware and software, for example.
Dual booting is problematic, as mentioned you’re messing with your partitions and could mess up your windows partition, but also windows can, unprompted, mess up your Linux bootloader. As long as you’re careful with partitions and know how to fix your bootloader from a live image, there’s no real issue, but it’s worth keeping in mind.
By the way, I recommend rEFInd for the bootloader when dual booting, it doesn’t require configuration and will detect bootable systems automatically.
A VM sounds like a good idea to try a few things out, but do keep in mind performance can suffer, and you might especially run into issues with things like GPU virtualization. If you want to properly verify if things work and work well enough, you’ll want to test them from a live system.
As a final note, you can give your VM access to your SSD/HDD - if you set that up properly, you can install and boot your Linux install inside a VM, and later switch to booting it natively. You still have the risk of messing up your partitions in that case, but it can be nice so you can look things up on your host system while setting up Linux in a VM.
it also won’t wake up from a month in sleep with an untouched battery the way a Switch does.
Any time I left my dock unplugged (after cleaning or whatever), next time I wanted to use the switch or joycons for something I found the battery drained :P
Not to say it isn’t better, or even way better, but calling it untouched seems a bit too exaggerated.
In this regard, I think Gigabyte just has you put the firmware in some accessible location (like on a USB drive) and update from BIOS?
I’ve got one light in a room that makes a quiet whining noise when on, seemingly only after a minute or so (maybe after it warms up a bit). Thankfully I can just keep it off just fine, but occasionally I’ll turn it on for a bit more brightness, and realise it’s still on a while later by the annoying noise.