Showerthoughts maybe?
Showerthoughts maybe?
Why would I recommend Fileflows? It was a little more user friendly in my experience without requiring pulling in configurations from other sources. I know there are repos chalk full of Tdarr settings and configs, but for simple setups and DIY I preferred the Fileflows interface. The end result is basically the same, so pick your poison.
Isn’t AMD’s HEVC/265 still decent, specifically? I feel like I read that somewhere years back. 264 has always been a weak spot for them, however.
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.
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.
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.
My friends and I all LOVED the pick-up nature of SG1. We’re all adults with busy lives, so hopping into a ~5 minute casual match was just so easy. And the casual nature made it feel like we could have success without “grinding” the game. I guess that is explicitly not the intent of SG2.
The shift from “we’re making a fun and relatively casual arena shooter with a neat gimmick and extremely rewarding fundamentals” to “we’re making a generic e sport shooter” was swift and, frankly, uncalled for.
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.
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.
Ooooh okay. Yeah, I avoided the playstore version. I’m pretty sure I had read somewhere early on that the Playstore version would lack features or otherwise be behind in some ways due to complying with certain Google specific requirements to be allowed on the storefront. Kind of like KDEConnect.
I’ve got it opening YouTube links by default… At least from within other apps. In Firefox I can also hit “open in app” and it pops right up. Casting works too.
Both glowing portions are natural gas pipes. Perhaps it’s somehow ignited inside the pipes and is super heating them but also somehow NOT travelling outside the two glowing sections and burning the house down???