Someone overreacted here, but it wasn't just the police. Who calls the cops over a water gun, for crying out loud?!
This is why you don't train a bot on the entire Internet and then use it to offer advice. Even if only 1% of all posts are dangerously ignorant . . . that's a lot of dangerous ignorance.
Fortunately, this particular piece of bad advice is unlikely to poison any fool who goes through with it, since PVA glue is not considered an ingestion hazard, but "non-toxic" doesn't mean "edible", it just means "not going to poison you when used in the intended manner". "Non-toxic" can still be quite dangerous if you mistake something intended as linoleum pigment for a dessert topping.
This has always been the case with the right wing. They believe that wealthy white straight cismen are the perfect expression of humanity, and everyone who deviates from that mold should be punished. Their "freedom" exists only for people they regard as the top of the hierarchy and basically consists of the freedom to be greedy assholes.
I wish people would get this through their heads and stop electing them. It doesn't matter what the talking head du jour does or doesn't say—the Conservative Party of Canada's track record is clear all the way back to the days when it was the Reform Party, and even the most apparently innocuous member of it is complicit.
The Liberals are quietly corrupt in spots and sometimes stunningly inept, but the Conservatives are nasty. It's past time for the NDP to have their chance to screw up the country instead.
They are not revealing user names on the site.
You mean, "They are not currently revealing user names on the site." This may easily be the first temperature increment in a frog-boiling process.
(Cynical? Yes, but the world keeps reinforcing that attitude.)
Bunch of things going on here.
On the one hand, Snapchat shouldn't be liable for users' actions.
On the other hand, Snapchat absolutely should be liable for its recommendation algorithms' actions.
On the third hand, the kid presumably lied to Snapchat in order to get an account in the first place.
On the fourth hand, the kid's parents fail at basic parenting in ways that have nothing to do with Snapchat: "If you get messages on-line that make you uncomfortable or are obviously wrong, show them to a trusted adult—it doesn't have to be us." "If you must meet someone you know on-line in person, do it in the most public place you can think of—mall food courts during lunch hour are good. You want to make sure that if you scream, lots of people will hear it." "Don't ever get into a car alone with someone you don't know very well."
Solution: make suggestion algorithms opt-in only (if they're useful, people will opt in). Don't allow known underage individuals to opt in—restrict them to a human-curated "general feed" that's the same for everyone not opted in if you feel the need to fill in the space in the interface. Get C.O. better parents.
None of that will happen, of course.
Anyone who is actually surprised by this has not been paying attention.
For gaming, you should be using the most current version of nvidia's proprietary drivers that supports your GPU, unless that GPU is really old. Have a look at this page: https://www.nvidia.com/en-us/drivers/unix/legacy-gpu/
If your GPU isn't listed there, use the most recent driver you can find.
If your GPU is on the 470.xx supported list, try 470.223.02, as that seems to be the last in the series.
If your GPU is on the 390.xx supported list, try 390.157.
If your GPU is on one of the other lists, it's a really old chipset and you should be using the Nouveau driver that's built into the kernel.
If you're using the nvidia proprietary drivers on a system that also has Nouveau installed, make sure you've blacklisted Nouveau so that you're loading the correct driver.
Dual-graphics laptops are a bit of a bear to work with under Linux generally. Good luck.
Godot isn't even officially supported on ARM, so I don't expect to see it on RISC-V anytime soon. It might work anyway (if you compile it yourself). Or it might work (slowly) via x86_64 emulation in qemu. But if having Godot working is a make-or-break for you, I'd say this architecture isn't appropriate for you yet.
Short version: some people (I'm one of them) object to systemd on grounds that are 75% philosophical and 25% the kind of tech detail that's more of a matter of taste than anything else. The older sysV init is a smaller program, which means that it has a smaller absolute number of bugs than systemd but also does less on its own. Some of us regard "does less" as a feature rather than a bug.
If systemd works for you and you don't know or care about the philosophical side of the argument, there is probably no benefit for you in switching.
Linux, and much of the open-source software that goes with it, has been multi-architecture for a long time. If you take something that already runs pretty decently on x86, x86_64, PA-RISC, Motorola 68000, PowerPC, MIPS, SPARC, and Intel Itanium CPUs, porting it to yet another architecture is, while not trivial, at least mostly a known problem.
Windows, by contrast, was built for descendants of the Intel 8088, period. It's unsurprising that porting it is a hard problem and that results aren't always satisfactory.
(Apple built on top of a modified BSD kernel, and BSD has also been ported around quite a bit, so they also have a ports-are-a-known-problem advantage.)
GIMP has the closest thing to feature parity. If you're looking for similarity of UI and workflow, you're not going to get it. Adobe throws millions of dollars that open-source projects don't have at streamlining their UI. UI specialists that will work for free are unicorns, so most open-source UIs are designed by volunteer generalist programmers. Which means that said UI gets the job done, but isn't optimized for the workflow of people who don't think like the original programmers.
Personally, I might shift the same picture through Darktable, GIMP, Inkscape, and even Scribus, depending on what I was trying to do with it. (Text on a path -> probably Inkscape, then export as PNG and import into GIMP as a layer.) Is that less convenient than performing all the operations in one program? Possibly, but since I don't like Photoshop's UI either, I'm willing to give up on "one-stop shopping".
(So who, for my money, had the best UI? Probably Paint Shop Pro, twenty or so years ago when it still belonged to JASC. Of course, it was a simpler program too, and so had less junk in its interface.)
Fact is, if you're a pro, you've invested years into learning Photoshop's interface and how to get the best results out of it. You're in the position of a baseball player who's decided to start all over again with basketball. Any attempt to transition to other software is going to be really, really frustrating for you, and likely drop your productivity into the toilet for a few months at least. Plus, you're going to need some features that average users don't care about, especially if you're preparing work for print.
I hate to say it, but you may honestly be best off running Photoshop in a VM rather than trying to move to other software, at least until you can set aside a couple of months where you have no urgent projects (if that ever happens).
The problem isn't that it didn't. The problem is that anyone thought that it should have.