cron @ cron @feddit.de

Posts

13

Comments

218

Joined

2 yr. ago

This looks great! It would be even better if they improve the handling of multiple accounts on the steam deck.

I bought the steamdock from Skull & Co. This dock works fine, however it does have very few connectors (USB-A, HDMI, USB-C).

It's also nice that you can easily return games if they don't run well on your system (at least with steam).

Just as a side note, the load factor can also mean that processes are limited by IO:

Unix systems traditionally just counted processes waiting for the CPU, but Linux also counts processes waiting for other resources -- for example, processes waiting to read from or write to the disk.

Source

But you should also take into consideration that this article did not get a huge attention. It is almost a week old and has a few thousand viewers.

True. And communication was also not ideal.

This reminds me of how Google handled the stadia shutdown. Now many controllers have got a second life thanks to the option to enable bluetooth.

Thanks for the suggestion, after switching Bluetooth off and on again, both controllers are able to connect again. This is at lot faster than removing and pairing.

Still unclear to me why this happens. Does anyone have this problem with other (non-stadia) controllers too?

Yes, I would go for the OLED. There is no OLED with 64 GB, only with 512 GB and one TB. Alternatively, you could go for the 64 GB IPS model, which is quite cheap.

Every Steam Deck can be expanded with micro SD cards. I don't notice a difference where the game is stored, but I also don't track startup times with a stopwatch ;) But please buy a decent micro SD card if you plan to extend your storage.

It's really astonishing how many vulnerabilities cisco publishes every year.

I think the file server analogy isn't really fair. Nextcloud is better compared to Microsoft 365 or Google GSuite.

All of these offer file storage, but also much more.

You're right, the new open source driver does not support the 1000 series and older, only Turing (2000 series) and above.

The autotldr-bot only summarized the first page, so here are some more quotes. Basically, the performance was almost identical, with two notable exceptions.

Across a variety of demanding GPU benchmarks the NVIDIA R550 open kernel driver continued to perform on-par with the proprietary driver for these GeForce RTX 40 graphics cards.

While running Blender 4.0 the proprietary kernel driver seemed to yield slightly better performance. It was just fractions of a second but was rather consistently showing the proprietary driver having that slight advantage here, unlike in other workloads.

There was the small advantage too that during periods of brief downtime using the open kernel driver appeared to deliver slightly lower GPU power consumption than the proprietary driver.

Does anyone have an idea what's the point with the proprietary driver now? Does it have any features missing in the open driver?

Maybe call your provider and ask them? Sometimes they hide settings in the user UI but can easily disable DHCP for you.

Another option that is sometimes offered by the provider is another, more capable router model. This might cost a little more.

What benefit do you hope to get?

Streaming 4k content is not a problem, transcoding on the fly to lower resolutions is hard and requires good capacity planning.

I'm not convinced that a pile of old HDDs is a good fit for your homeserver.

• Many small disks will consume more energy than fewer large disks. Currently, the best capacity per price seems to be in the 20TB segment. A similar argument can be made for noise.
• The HDDs you have might not be perfect for 20/7 usage. I personally would recommend using disks that are made for continuous usage.

Start with what you have, but if you outgrow your setup, buy proper hardware. And make backups.

No, but thats what TLS does absolutely fine.

Remotely hacking into my server is probably harder than just walking into my home with a warrant and confiscate everything.

I'm unsure about the end-to-end encryption aspect. While this feature is great for a cloud service like ente.io, it doesn't really help much in a selfhosted scenario - and might make backups more complicated. Any other opinions on this?