Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)D
帖子
0
评论
83
加入于
3 yr. ago

  • Isn't this almost the inverse argument to the android vs iPhone thing? Like the iPhone being (traditionally) more expensive for the "same technology from 5 years ago"? I don't really have a horse in this race, I'm a firm believer in use what you like and is easiest/best for you. But I do feel compelled to call this one out a bit.

  • I might recommend fileflows over tdarr- but either way some kind of similar solution is almost mandatory with the grab bag of arbitrary encodings you find out there.

  • Atomic OS's (especially Fedora based) with Nvidia are going to be a bit of a pain. Did you follow all the instructions found Here ? I personally gave up on silverblue/kinoite after I tried Bazzite. Similar bases, but the Bazzite devs paid special attention to GPU and accessory drivers/implementations that are otherwise much more painful in Fedora Atomics. You can always do a clean rebase then re-run the steps above (only the OSTree section).

  • Software-wise, it seems that the relatively fast adoption of flatpaks and other containerized formats somewhat solves the typical dependency hell that was so common in Linux just a few years back (and to some extent still is an issue today depending on your distro and use case). The hardware support side is a little harder. That's going to be up to vendors to play nice with the Kernel team and/or introduce reasonable userland software that doesn't break the golden rule. Until Linux gets more market share the latter isn't likely to happen. A nice side benefit of the emergence of immutable and/or atomic distros is that users can play around and try things with much lower risk of bricking their systems, so I'd also consider that a step closer in the "it just works" department.

  • Xbox controllers (Xbox One and newer) have been absolutely solid for me with the xone driver + xpadneo, regardless of distro. Bazzite has everything I need baked in, so it was completely plug and play. Not a very interesting answer, I know. But it still blows me away that it "just works."

  • Very true. But brute force checking through tons of different settings for each camera you need to configure is not fun. I couldn't seem to find any kind of "known working configs" database or anything either. Every camera seems to be different in what it expects, outputs, authenticates, etc. Once it's set up, I agree, maintaining the config is easier. Having all your cameras match in model and firmware version probably makes the whole endeavor MUCH easier.

  • AmCrest and Frigate together are SO good. Integrating Frigate with Home Assistant was also insanely easy for quick viewing and notifications. That initial Frigate config is a bit of a bear- but once you're past that I cannot speak more highly of it.

  • hunter2

  • Alright, where's my replacement once my current Fitbit dies? What company makes a watch that tracks steps, heart rate, sleep, spO2, notifications, is generally water resistant (light swimming) and has a battery that lasts ~5+ days? Bonus points for open firmware/hardware that doesn't require me to design my own apps/systems for each of those items. I don't even use most of what my Versa 3 can do, but I know it won't last forever and I'd at least like an idea of where to go if/when it breaks down.

  • Proton experimental and (at least as of yesterday) I had to opt into bleeding edge beta as well or I'd just get black screen at launch.

  • No stuttering for me on Linux... Runs as good as it ever has but the visuals are even that much better due to the engine upgrades. Not a fan of the new UI, but the old UI was clunky too, so I can't really say it's even a step backwards.

  • On windows the article mentioned being a microcode patch via Windows update. Linux would be similar- but via a kernel update most likely. I'd assume that a general BIOS update would also do the trick, but then you're relying on motherboard vendors and it's unlikely many would provide such an update to older hardware, even if it's still widely used.

  • Difficult to exploit, already in the process of being patched. Truly, the most breaking of news.

  • I think they meant it as "once infected may be impossible to disinfect." But it sure doesn't read that way at first glance.

  • I've had good luck with AsRock as well. Before this most recent generation I was Sapphire all the way. But they charge a good premium now that I don't feel is worthwhile if you're in the ~7600xt range or lower.

  • Here's my vote for Bazzite. If your use case is simple computing and games? I don't know if you can do much better.

  • Even with nvme drives which supposedly "don't need" to use BFQ, I STILL always swap it since it maintains responsiveness across the system during heavy IO loads. I used to have similar full system freezes when downloading steam games which notoriously overload your IO in Linux. BFQ was the solution every single time.

    Edit Try following the instructions detailed in this post to add a systemd rule to set the scheduler: https://stackoverflow.com/questions/1009577/selecting-a-linux-i-o-scheduler

    The second answer that shows an actual rules.d file example has always worked for me. If using nvme or old school spinning rust you'll need to change it up a bit. Instead of "noop" set it to "BFQ".

  • Try swapping to BFQ io scheduler and see if that makes a difference.

  • He retains the "Cold Take" name and property- so here's hoping he continues it, whether that's under some new media company or even just as a solo content creator.