Back then, there was less hardware acceleration for the regular desktop stuff. Probably it just copied the data from the software rendering, and there it just defined that this part of the screen was hardware accelerated and this region pointed to vram instead of regular RAM.
They basically did. I bet they just used an ORM in the backed and then pointed the API endpoint to the user entity without filtering the fields. This results in a dump of the user table (although row by row indexed by users instead of a full dump)
Not a fever dream, I remember this, too. You basically got a "transparent" image through which you could see the rendered live (or game, as it happened with those, too). As soon as you closed the video player/game, or saved and reloaded the image, the effect was gone and you were stuck with a... I think it was just a black image?
I'm unsure, I use both. In theory it should wear out less, since you're loading slower and with less current. In practice it generates heat and this gets generated in the coils that are right near or on the battery, which then again causes wear... I'm not sure which effect is stronger, or whether it's a trade-off and doesn't do much of a difference.
Hmmmm I didn't know that, every comment that I read, didn't mention this fact. I'm running my own Searxng instance and Meta engines can be quite powerful, especially when you can adjust them a bit and filter out what you consider "spam" results (e.g. pinterest)
I was wondering the same, but I didn't find any information on how it builds the search index. I guess it takes quite a while until it's usable. Also, it might be very dependent on the speed if the internet connection and also the available storage.
Maybe, but knowing the ease of sudo, I really hate using runas. Most of the time, I just want plain old admin privileges. Mostly I don't care whether I can impersonate another user with this.
Depends on how much current the drive draws. If the m2 SSD needs more current than your regular thumb drive, your phone might not supply enough power and it stays unusable.
Besides that, as long a the enclosure uses the standard protocol and the filesystem is supported by Android, it should work
Also it's just wrong advice, since you explicitly need --no-preserve-root for it to work... /s
Jokes aside, please don't troll anyone with things, that can have severe consequences. Yes, they should have a backup. Yes, they should know how to restore from it. Yes, they should have tested it prior. Yes, you shouldn't blindly trust people online.
But even then: Assuming my backup works and I can easily revert the damage. Maybe I need to complete an assignment until tomorrow and just lost 1-2 hours because my PC was busy doing the restore? There's always a high chance of collateral damage
And if they don't update it soon, you might want to reconsider your choice of instance.
The advisory went up about 4h ago. About 3h ago, my instance admin sent out an announcement that the patch had been applied. That was before I even heard about the issue.
Back then, there was less hardware acceleration for the regular desktop stuff. Probably it just copied the data from the software rendering, and there it just defined that this part of the screen was hardware accelerated and this region pointed to vram instead of regular RAM.