"V for Victory" is Nazi too, right? Think about how the occupied French must have felt when they heard that on the BBC, after all the Frenchmen killed by those English longbow archers.
Meanings evolve.
Sure. I'm sure Trinidad and Tobago, and Albania, are definitely Nazis. And those anarchists with their black and red flags, they're definitely Nazis too, right?
Seriously though, in this case, it's the unofficial war flag of Ukraine.
It was originally associated with the WWII nationalist Banderite movement, which has some dubious history but is important in the 20th century story of Ukrainian nationalism. However its usage has evolved and is used widely, albeit unofficially, in modern Ukraine, by lots of military-associated groups who have nothing to do with Nazis or fascism.
One of the main selling points of it is that it trolls people who uncritically believe that Ukraine is run by Nazis.
Way too obvious. They could have left it standing for at least a few weeks before an uhhh... "electrical fire".
Of course, no-one is going to get prosecuted for this.
I can only imagine they're shutting it down to replace it with something with different branding, based on an LLM. Microsoft has gone all-in on LLMs and I'm sure they'd love some of that virtual assistant action if they were able to differentiate themselves.
If we hypothetically assume this is true for a moment, then consider:
-
No SAMs would have been fired if there were no Russian missiles attacking Odesa, and thus indirectly it's still Russia's fault.
-
The Russian-designed and manufactured S-300 (and presumably the closely-related S-400) are dangerous to use over populated areas if they have no working safe abort or engagement minimums safety features, therefore they are even more dogshit than we thought they were. So, Russia is still at fault here for supplying unsafe SAMs, and no-one should buy any Russian SAMs in future if they care at all about their civilian population. If we assume that the anonymous Twitter source is indeed correct, then this is probably why Russia isn't saying anything about it.
I'm sure once the war is over we'll get some proper analysis from people with actual warhead ballistics knowledge though, and not just some anonymous propaganda.
Nice to see Google doing the responsible thing here, because Apple certainly didn't when AirTags were launched.
I still think having cheap, socially acceptable, easily-accessible, highly effective tracking devices with months or more of battery life is something out of dystopian fiction though. It's not good for society in the long run.
This is the end of official updates for them, they're not bricked.
Older Chromebooks do have a shitty support lifecycle, it can't be denied. Newer (post 2020 launch) Chromebooks come with at least 8 years of updates, although that's from product launch, not from when you buy them. That is comparable to Apple's support lifecycle.
It is possible to install ChromeOS Flex on out-of-support Chromebooks, though likely you will lose some features. You can also install generic Linux on them, but it's got to be said it's a slightly annoying experience.
Apple users have been sending text messages interchangeably between their phones and computers/tablets for years.
As have Android users. Microsoft Phone Link/My Phone Companion and KDE Connect have supported this for years on their relevant PC platforms. The Phone Link Android app is even preinstalled on Samsung devices. There's a teensy bit of setup but nothing complicated. KDE Connect even supports stuff like using the phone as a touchpad, remote keyboard, or media/presentation controller.
If your PC is a Chromebook then you don't even need these. If you sign into the phone and Chromebook with the same Google account, the integration just works, much as it does on Apple devices.
Most of your arguments can be boiled down to "everything is really slick if you use an all-Apple ecosystem". Which is fine, but the same can be said about Android - if you use an all-Google ecosystem with Pixels, Chromebooks and Google Workspace then most, if not all of your complaints about Android go away. Pixel Android is more consistent and less buggy than most vendor versions of Android. Integration with Chromebooks works out of the box. Google Workspace MDM is simple and straightforward, and you don't really need to buy a separate MDM solution.
The difference is that Android at least makes a decent effort to cater for a heterogeneous ecosystem. With Apple, if you're not entirely onboard with an all-Apple ecosystem then it starts getting messy quickly.
Cotton mostly, not wool, hence Manchester's old nickname of Cottonopolis. Wool tended to go east to Yorkshire, where it was worked in Halifax, Bradford and Leeds. Yorkshire has a lot of sheep, and used to have even more. But otherwise yes, you are correct. The damp climate of North-West England was an important part of it becoming dominant in the 19th century cloth trade, because it made the fibres easier to work with. Cotton fibres are a serious fire risk if they are dry.
At least for me, there is a big difference between naming things at home and naming things for work.
Work "pet" machines get systematic names based on function, location, ownership and/or serial/asset numbers. There aren't very many of them these days. If they are "cattle" then they get random names, and their build is ephemeral. If they go wrong or need an upgrade, they get rebuilt and their replacement build gets a new random name. Whether they are pets or cattle, the hostnames are secondary to tags and other metadata, and in most cases the tags are used to identify the machines in the first instance, because tags are far more flexible and descriptive than a hostname.
At home, where the number of machines is limited, I know all of them like the back of my hand, and it's mostly just me touching them, whimsical names are where it's at.
Ungulates. Because who doesn't like a hoofed animal?
My client machines are even-toed ungulates (order Artiodactyla) and my servers/IoT machines are odd-toed (order Perissodactyla). I'm typing this on Gazelle. My router is called Quagga, both after the extinct zebra subspecies and the routing protocol software (I don't use it any more but hey, it's a router).
Biological taxonomy is a great source of a huge number of systematic (and colloquial) names.
Very hard to guess what's going on here without some logs. It could be a lack of enabled hardware decode acceleration, or an unaccelerated on-the-fly transcode using so much CPU that it's causing the decode to be choppy, or it could be a driver issue with the encoder, or decoder, or some other configuration issue with the media server or client.
Have a look at the logs and see if you can see anything suspicious. If you can't, then upload some log files somewhere and ask for help again.
Details of how to get the logs from Plex media server are here:
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
Also, when you say you have a crappy graphics card, what is it exactly?