Not on my Galaxy S23+ from Google Fi
pixelscience
joined 1 year ago
It's because it actually is a security risk with the Chinese government having the ability to do who knows what with a frightening amount of data. There is also the option of selling the company to one that isn't related to the Communist Party government, but no one seems to be talking about that option.
The only slippery slope is more apps owned by a foreign government that is not exactly our friend.
If the app was owned by North Korea, would you be cool with it too?They aren't banning Instagram and Facebook.
I got so tired of them that I actually answered one a few weeks ago. I was shocked that an actual person answered.
I asked to be taken off and she was very nice and they actually did it.
Haven't received one since.
You can see the awful, misaligned panel gaps in those photos.
TWO MONITORS!
Like they're going to just take the lack of those fee profits off the bottom line. Look forward to the new and/or increased yearly fees now.
Nice find!
I'd be curious to see RTINGS do a review of the panel on it.
I thought I was 43 for probably close to a year, and even told everyone that asked I was until I had to get my own health insurance and found out I was actually 44.
Except if you care about anything having to do with picture quality, brightness, contrast ratio or features such as HDR etc, then it's going to be a really shitty TV. They're made for the menus at McDonald's, not a device for modern media.
I think it's more of a "don't be an asshole, cause it could be you" type of situation.
view more: next ›
I've generally had good luck with hardware and things just worked under linux. But one day I upgraded a few machines on my network to 2.5G ethernet. Several already had the ports, but my little NUC NAS box didn't, so I installed a 2.5G usb ethernet dongle. No matter what I did, I couldn't get it to work. It would show up and NM would act like it was up and there were no errors or anything, but it just wouldn't actually function.
Eventually, I found out that it has a built in USB data partition that contains the drivers for windows. The card was coming up as a usb disk first when the hardware was assigned and not a network card which it should have been.
I had to write a blacklist the usb modules first, which I had done before, but I had to also write a udev rule to automatically add the network card and driver on boot. It wasn't that difficult to actually do, but I had just never had to do anything with udev rules before. Took me a good three days of troubleshooting to finally get everything to work correctly on boot.
ACTION=="add", ATTRS{idVendor}=="20f4", ATTRS{idProduct}=="e02c", RUN+="/sbin/modprobe r8152" RUN+="/bin/sh -c 'echo 20f4 e02c > /sys/bus/usb/drivers/r8152/new_id'"