There is, check out the Music Assistant add-on for Home Assistant.
👽Dropped at birth from space to earth👽
👽she/they👽
There is, check out the Music Assistant add-on for Home Assistant.
Ah, I see you also just got it for free on Epic 😅
The dev of this developed Caddy? Hmm… at least there’s talent behind it. I’m a little worried about creating that sort of record, but this guy seems earnest in wanting to liberate personal data.
It’s wild to me that more people don’t know about Unit 8200. Israel is up there with Russia, USA and China when it comes to state-sanctioned cyber attack capabilities.
The OS can’t get to the point of loading cpu microcode without that outdated, embedded microcode. The reason it can persist is because there aren’t a lot of good ways to see what that UEFI microcode actually is once it’s installed. Plus, only the UEFI tells you that it has successfully updated itself. There is no other more authoritative system to verify that against. So the virus could just lie and say it’s gone and you would never know. Hence needing to treat it as the worst case scenario, that it never leaves.
Hey, that’s really fair, thanks for being honest :)
Except that doesn’t at all explain the wider recall of 100 million units. Not every single one of those airbags were faulty. First of all, how could we know? Testing an airbag is a potentially dangerous thing to do, let alone on an enormous scale that would require under-qualified persons to run the tests. Secondly, it’s not a 100% failure rate. If it were, it would have been picked up far sooner than it would take to sell 100 million units. If it happened just as severely no matter the unit’s age, it would have been picked up during crash-testing. What actually happened was an analysis of statistical averages that showed a far higher rate of failure than there should have been.
The similarities to me come from a comparison to Schrödinger’s cat. In the airbag example, you don’t know if the unit in front of you is going yo fail until you “open the box” by crashing. With the AMD vulnerability, you don’t know if ur motherboard has been infected by any virus/worm/etc until a “crash” or other signs of suspicious behaviour.
In both cases, the solution to the vulnerability removes that uncertainty, allowing you to use the product to it’s original full extent.
Look at it this way, imagine if this vulnerability existed in the ECU/BCU of a self-driving capable car. At any point someone could bury a piece of code so deeply you can’t ever be sure it’s gone. Would you want to drive that car?
Personally, I think I should be able to expect a company to understand their target demographic well enough to know that those “features” wouldn’t be well received. But I also personally don’t consider ads and crypto garbage to be features. I guess if you do, then it’s the perfect browser for you. However, I don’t really want to contribute to Google’s monopolisation of browser engine development anymore. Nor do I want to use a browser developed by a homophobe. So even if Brave may be slightly “better-working” I would not consider it better at all.
As well, even though I’m a Blahaj member, I’m going to take the time to point out the “Bee Nice” rule of the instance we’re currently on. It feels like you’re skirting dangerously close to violating that, considering you implied I’m a troll for calling out the prejudicial politics of the founder of a piece of software, which you didn’t at all address in your comment. I’m going to attach some resources about it here, if you care to read them at all:
(Some of these are older, about the push for him to step down as Mozilla CEO, some are newer and urging him to leave Brave, or for people to boycott it.)
Sorry, I reread it and I understand now that you were referencing the AMD chip in a comparison. I guess I still would compare it most to the Takata airbag situation. You’re right that nothing happens on it’s own, but once you’ve “crashed the car” then it kind of is a lot like an airbag not going off. It infects your computer on a hardware level, and any future OS running off that motherboard is potentially vulnerable in a way that’s impossible to tell.
“this window only breaks if you’ve already crashed the car”
No, it’s usually more like “this thing will break and cause a car crash” or “this thing will murder everyone in the vehicle if you crash”. And companies still will not fix it. Look at the Ford Pinto, executives very literally wrote off people’s deaths as a cost of doing business, when they’d turn into fireballs during even low speed rear-end collisions. Potentially burning down the car that hit them too.
Edit: I mean, just look at the Takata airbag recall. 100 million airbags from 20 different carmakers recalled because they wouldn’t activate during a crash.
That’s nice. A quote still would have been more approachable for most, while those that were more curious could have followed the link to the document.
a free tier
Alternatively, you can just host this stuff yourself and never pay. A Pihole is just DNS-filtering. There’s a million guides to do this on the internet already. You can also do it more directly with some routers, I run DNS filtering on an ASUS router with the merlin third-party firmware. It’s possibly the simplest thing you can host yourself. Like others have pointed out though, it isn’t a replacement for uBO. They both complement each other and I would recommend both to people who are able. The one major advantage it has is being able to block some ads in mobile apps. But it cannot block as many in a browser.
You mean by building the add-on directly into the browser? No thanks. I like my browser dev to work on my browser and my ad-block dev to work on my ad-block. They are both good at what they do on their own, I don’t need them to mix.
Those features are opt-in.
They are now. They were opt-out to begin with. This is one of those “fool me twice” situations. That, and the founder of Brave is also an outspoken homophobe. He financially backed Prop 8 in California to overturn same-sex marriage, and left Firefox because it was too woke. I seriously would rather Chrome at that point. They’re just regular levels of corporate evil, not “every person who uses my browser is proving my identity politics” level of evil.
It’s not exactly super helpful to just link to an 86 page SEC filing. Maybe you could provide a quote?
AV1 Image File Format is an open, royalty-free image file format
While I am by no means trying to defend Google, or their monopoly, I’m struggling to see how this time is a “clear example” of monopolistic behaviour?
Like, take for contrast the Moving Picture Experts Group (MPEG) image format HEIC, which Apple has adopted as it’s main high-res format on iOS. It’s proprietary, and that fact is indeed worrying. However, the only reason I can figure out for Google’s move here being a ‘bad’ thing, is if you’re nostalgic about the .jpg extension…
I always did? A friend pointed out to me once the “correct” pronunciation. I like this way more.
Ah okay, thank you heaps for clarifying :) That’s awesome that you’ve been able to limit the overhead like that, I’m excited to test it out!
That doesn’t necessarily seem to be the case:
Does this automatically use nvidia-patch in the container drivers to unlock as many NVENC streams as possible? I believe, from their documentation, that it’s possible to use the patch with docker, with an unpatched host.
Otherwise, is this something that could be implemented? I’m happy to submit a feature request if needed :)
It does still have some issues, but it is being heavily worked on and has been for 12-18 months at this point. Has taken huge strides, and if you’re in the beta channel you’ll see lots of work being done.