it's running wpa_supplicant, not iwd. It's vulnerable to the similar exploit in CVE-2023-52160 but the patch will likely have to come from unifi, as wpa_supplicant hasn't been updated in years as far as I know.
No, but we are still in the era of mom has to physically annihilate her body in order to produce a child, and also in the era of mom requires actual physical recovery time before performing strenuous physical activity. I get the equity in offering dads extra leave to help take care of mom but it's disingenuous to suggest that they both have the same requirements.
Would it still be illegal if it's based on time? Like I'll make this up but suppose their policy was men get 2 weeks paternity leave, but women get 2 months maternity. It might actually make sense then.
I don't know if there are any for the switch specifically, but Modern Vintage Gamer on YouTube does a really good deep dive series he calls "impossible ports" where he covers the technicals of how a port of a game was made for a console and why it's crazy that it works at all. Portal on the N64 and halflife on the PS2 are the example that first come to mind.
It's free, you host it yourself. It's built off of nagios, compatible with nagios plugins, supports snmp or agent based checks. It can email, SMS, slack or discord you when something breaks, you can write your own custom checks in any language that can output to a local console... I could never imagine even looking for something else.
factory reset went back to the shitty upgrade version I upgraded to :(. But I will say that I haven't let it update since that initial terrible upgrade assuming it might get worse. Maybe I should try upgrading it once more and then lock it off if the next version is decent?
I connected it because it was in that like 2 year span where they had that a small android tablet as a remote. Legitimately cool feature but I should have known better than to let it update.
Vizio is fantastic if you’re using your own source, I wouldn’t rely on their smart stuff though.
I'd still refute that claim. I bought a vizio tv about ~7 years ago and it was perfect when I first bought it. A few software updates later and now the TV will switch to it's internal bullshit any time there isn't an input source for greater than ~3 seconds. It's infuriating that if my nvidia shield takes a second too long to push out a video signal the TV will just switch inputs on me. There is no way to disable this antifeature. The best part is after I noticed this behavior, I (at the network level) prevented all outgoing communication from this TV and it is still perfectly happy to just switch to a blank internal input whenever an external source takes slightly too long.
"If I can't track you, fuck you I'll make your TV basically unusable"
I certainly wasn't just born good at this. Unironically if you want to learn how something works, try to automate it. By the time it's automated you'll understand basically every part of it at at least a basic high-level.
If one doesn't exist, it would seem to be a fairly straightforward (if not a smidge tedious) thing to implement. Ever thought about learning web development?
No hate if you disagree, your reasoning is sound. I just think that naming, especially in the new tech space, goes beyond pedantry. We have words that are specific enough to describe two similar technologies, but we only retain shared understanding of those words if we collectively use them. It may be the case that AR evolves to be commonly understood as encompassing both technologies but they are fundamentally different in how they work, whatever we choose to call them.
Just because developers name libraries things doesn't make them accurate. Generally when something is misnamed it's because of backwards/intercomaptibility or just design decisions that differ from original implementations and it's no longer feasible/reasonable to refactor to a different name.
Examples:
windows 7 was version 6.1, windows 8 was version 6.2, windows 8.1 was version 6.3
Java 5 was versioned as 1.5, continuing the convention from previous releases 1.2-1.4
Hell, where I work we use an automation workflow with functions called stuff like "create_and_assign_citrix_security_groups_to_static_containers" that has long since been adapted to work with vmware and other non-virtualization platforms like k8s. Refactoring those functions would mean refactoring any external automation that uses these libraries, just like refactoring versioning schemas would break compatibility with any external software that relies on an assumption that windows >xp would be 6.X.
it's running wpa_supplicant, not iwd. It's vulnerable to the similar exploit in CVE-2023-52160 but the patch will likely have to come from unifi, as wpa_supplicant hasn't been updated in years as far as I know.