Ironically, I have to root every time I install a ROM just to bypass the detections 🤦♂️
alphapuggle
joined 1 year ago
I shut my account down a few days ago anyway. Got an email that said paying with PayPal would require a debit or credit card through them. No thanks lol
Frankly both of these maps are deceptive (though the top one is albeit more so). The dot gets colored the primary color in that region, and visually makes the Democrats seem way more dominant when it's much more bipartisan. A gradient would make this map better
This is just a theory, I don't have knowledge of the inner-workings of either Linux or Windows (beyond the basics). While Microsoft has been packing tons of telemetry in their OS since Windows 10, I think they fucked up the I/O stack somewhere along the way. Windows used to run well enough on HDDs, but can barely boot now.
This is most easily highlighted by using a disk drive. I was trying to read a DVD a while ago and noticed my whole system was locked up on a very modern system. Just having the drive plugged in would prevent windows from opening anything if already on, or getting past the spinner on boot.
The same wasn't observed on Linux. It took a bit to mount the DVD, but at no point did it lock up my system until it was removed. I used to use CDs and DVDs all the time on XP and 7 without this happening, so I only can suspect that they messed up something with I/O and has gone unnoticed because of their willingness to ignore the issues with the belief they're being caused by telemetry
I would check out the inovelli switches. Not exactly inexpensive, but definitely home assistant friendly
Uhh do we know if this extends to sites.google.com?
Actively going through this rn, could use it
I still can't do half the stuff in the windows settings app that I could in the control panel, and every update removes an option in control panel without an adequate replacement.
Inb4 "use Linux" I DO but Nvidia and Wayland is still BORKED (even with v555) and when I'm done with work I just want to load up a game and not have to fuck with drivers and never actually play. Sue me.
The CVE has to do with the utility not correctly identifying private IP addresses supplied to it in a non-standard format, such as hexadecimal. This would cause the 'node-ip' utility to treat a private IP address (in hex format) such as " 0x7F.1..." (which represents 127.1...) as public.
This is a ridiculous expectation. Providing addresses in an unsupported format doesn't yield correct results? Who wouldda thunk it. Clean up your fucking code and pass it in as expected, or make your own damn node-ip.
Got a lot less racist, but definitely more crazy
My professor made me install TeamViewer to our lab computers despite strong pushback from me, and perfectly functioning ssh access through the campus VPN. I can't wait to send this to him.
Great! Now do it to Windows