qw3rty01

A lot of them run BSD, not linux, which wasn't affected

It can also cause kidney damage which can be life threatening, especially when you’re dehydrated (which is pretty common after drinking); tylenol is a lot safer than ibuprofin when used as directed, it only becomes dangerous when glutathione is depleted (at which point it becomes a lot more dangerous, which is why you should never drink while taking Tylenol)

This is exactly the opposite of what he’s saying, using Arc everywhere is hacking around the borrow checker, a seasoned rust developer will structure their code in a way that works with the borrow checker; Arc has a very specific use case and a seasoned rust developer will rarely use it

So in this case it is still a form of safety that’s well-defined in rust: cancel safety. The io-uring library doesn’t have the same cancel safety guarantees that everyone is used to in epoll libraries. In Tokio, the cancel safety of `accept` is well documented even though it works the way you’d expect, but in monoio, it’s literally just documented as `Accept` with no mention of the cancel safety issues when using that function.

as someone who has been working to make nix my main system for several months now, there are some very clear areas of improvement that would make things easier:

- [any] documentation, the majority of nix modules are undocumented and so the only way to figure out what settings are available is to find and read the source code (and even then it could be using a module to convert the definitions to the target config format, in which case there’s even more guessing, but at least the official documentation of that package gives you something)

- coding standards; lots of modules have different variations of camel case, snake case, adjective-noun, noun-adjective, etc so it’s not clear what the correct format of a setting is for an arbitrary package

- flakes just need to be both an official feature and set to be the default way to interact with nix, it just has too many upsides

- Better errors, the current errors are just horrible to read and you end up picking out 1 or 2 spots in several paragraphs of irrelevant code snippets and stack traces

- up to date resources, since the official docs aren’t very beginner friendly, third party resources end up being the way people learn (vimjoyer has been a godsend), but half the time when you try to use those resources, they’re out of date and lead to broken nix configs, having solid official updated documentation to help new users get started in nix would go a long way here

Incorrect, the case was appealed to the supreme court and the appeal was denied, so the lower court ruling held.

What was ruled by the supreme court was that Google's usage of the API (which had already determined to be copyrighted) fell under fair use in copyright law.

almost all of these are non-commercial; all but 1 of the commercial incidents from the past 10 days are due to striking birds in flight, and nothing with airport taxiing

The article answered that question:

> I found some trucks that were literally priced $10,000-$15,000 over MSRP, and I encountered many of the shady business practices that the FTC is now trying to ban.

because it's not ± a few hundred dollars, it's thousands of dollars, and claiming online that it's one price and charging a lot more once you get there

No, because you're framing it like they're blocking or challenging every user that comes to their site. Instead, when 90% of your malicious traffic comes from VPNs/TOR, it makes way more sense to just block or challenge those specifically even if it causes an inconvenience on the ones who use those services in a non-malicious way.

Chaos Gorilla has already existed for over a decade