qw3rty01

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

No, leaking is explicitly safe in rust: https://doc.rust-lang.org/nomicon/leaking.html

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.

It already has a self-hosting option: https://github.com/omnivore-app/omnivore/tree/main/self-host...

It's just not documented well.

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.

Unfortunately that ruling was overturned and APIs were found to be copyrightable: https://en.wikipedia.org/wiki/Google_LLC_v._Oracle_America,_...

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

I'm not sure if there's a JS shim or not, but rust has been a supported language for a long time with that workflow: https://developers.cloudflare.com/workers/tutorials/hello-wo...

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

Some providers like digitalocean use a serial connection for the terminal, so it works even when the network configuration is completely broken somehow (totally not because you set the input policy to drop without making an accept rule first)

Just want to emphasize the last sentence of the parent post, some of what you were describing really sounds like either leading to, or full blown depression, and want to mirror the recommendation to get professional help even if it feels like it would be a waste of time or bother people around you

He means more programming languages

But the person saying something outrageous would undermine the point of the study--to determine if deep fakes were indistinguishable from actual footage. If it's given away by something unrelated to the deepfake method, then you're adding in an external bias unrelated to the realism of the deepfake.

Unless I misunderstood the goals of the study of course.

I really wish they took actual things the individual said in the past, but used a deepfake for them actually saying it. Most of the deepfakes were easy to spot, but a couple weren't clear at first that they were fake, only to be given away by the content of their speech.

Any reasonable person would read "Companies we monitor" as "Companies that pay for and rely on our services", if that's not your relationship with the companies, then it's just using deception, and probably also violating trademark

Well the linux foundation picked it up when mozilla dropped it so it's not dead, but the last commit was also 8 days ago so not very active either

Correct, although it looks like converting some parts to safe code may be a future goal

it doesn't convert pointers to references, it just uses pointers, so the borrow checker isn't invoked.

it's been a while since I've used chrome, but iirc it signs in on the browser automatically when you sign in on google

Google has shut down a bunch of popular services: https://killedbygoogle.com/

I wouldn't use them as a standard for keeping services up.

Turns out there's been some work, and the rust part has actually been the main issue: https://github.com/rust-lang/miri/issues/722

The hardest part would probably be getting LLVM (written in C++) to compile to webassembly, since that's what rust uses as a compiler backend.

Maybe that would be true if they hadn't already been making it harder and harder to not use edge as the default in windows for the past few years.

the problem is a lot of the "disable asap" steps require a step before that so the machine is still accessible afterwards (such as adding a non-root user before disabling root login, adding an authorized key before disabling password login, etc)

They do mention it, just not directly:

> Right now we have excess green energy that we just throw away. We can store this excess renewable energy in chemicals.

The idea is that it can be used to store excess energy from green sources

In the article, the idea was to store excess green electricity (from solar/wind farms for example) by capturing CO2 that is generated from fossil fuels. I do agree that claiming it will address climate change is a bit of a stretch, since that CO2 is still going back into the environment when the methane is used, but it does mean getting more energy per unit of CO2.