thiagobbt

While upstreaming is incredibly important for long-term support it isn't nearly as exciting as the reverse engineering work the people mentioned were responsible for

They usually already have mics to do automatic EQ calibration

Imagine there's a machine that you can deposit dollar bills and it registers in an internal database how much you have. The machine calls these stored values as wrapped dollar. You can withdraw your wrapped dollars back as dollar bills whenever you want.

This machine also allows you to send these wrapped dollars to other people - it just subtracts from your balance and adds to the other person's.

What this guy did is transferring his wrapped dollars to an address no one controls instead of withdrawing as he should. This address was the machine's address, but it's not programmed to handle the balance in it's own account and it runs code that can't be upgraded, so any values sent there are lost.

In this example dollar = ETH, wrapped dollar = WETH, machine = the WETH smart contract.

The real problem here was thinking a ETH transfer (dollar bill deposit in the example) works the same as a WETH transfer (database transaction in the example).

I believe most contracts on the Solana network are written in Rust

You only need an internet connection the moment you're activating the eSIM for the cryptographic keys to be downloaded. From that moment forward it acts just like a regular SIM card.

Pressing ctrl-d a couple of times, seeing what will change, and typing something is most of the time easier and faster than thinking about a regex. At least that's how I feel

Isn't this related to this change on kernel 4.10? https://kernelnewbies.org/Linux_4.10#head-f6ecae920c0660b7f4...

Due to the hierarchy of dns you can ask to a root server who handles .com, then to that server who handles google.com, then to that Google server, who handles mail.google.com, and then you can connect to it. If you allow anything to be a TLD the root servers need to know about everything, which isn't really feasible

"This restriction includes the use of USOC's trademarks in hashtags such as #Rio2016 or #TeamUSA."

Say what??

I have no problem with it if they actually have a purpose, like .docx or .tar.gz

The real problem is using a public domain. OpenWRT for instance uses openwrt.lan by default.

And FCC approves it?