CraftThatBlock

I don't think speakly badly of is the same thing as "framing" though

It's pretty simple, don't say Cloudflare are nazis are you will be allowed on their platform. They have been very vocal about being neutral in almost every case.

This is most likely a win-win senario for both parties.

Netflix can be more stable, and can save on bandwidth in their own DCs.

ISP can save a lot of egress bandwidth by having Netflix inside their infrastructure.

I would be surprised if any of the parties payed. It's a great strategy to have the ISPs on board with this

Many indie developers do use these platforms instead of writing their own engines. From scratch is usually the exceptions

I agree, I could've been clearer. I meant as a third for of authentication overall, with an additional password

This is strictly an upgrade from the old button though, as this is a single form of physical security vs zero. If used with a password, the key is only secure in computers with the password, AND it has to be you pressing.

Fingerprint are not very secure, but as this is meant to be only for physical access with the password, it's much better than before.

You can spoof it in the inspector, under application/sensors I think

Yes, it's like the libc of WASM. https://wasmer.io is a runtime with WASI support

Git being "distributed" version control is meant as distributed because it doesn't require a central checkout server, and GitHub is simply a distribution (not checkout) server

The astronauts finished all the experiments ahead of schedule, even with the "strike". It seems like taking a break (accidental or not) increased their productivity afterwards

We have cruise ships with thousands of people sailing right now, and the system seems to be working fine.

It's typically not immediately after it's fixed, but usally about a week or so, to let the majority update.

The vendor can also usually request an extension, as per the Project Zero guidelines, of I believe 1 month if they confirm to be actively working on a patch.

The goal of responsible disclosure is to help the vendor and their users' be more secure, so having a policy that is balence between the two is important to let the vendor fix it, and to not let the users be possibly hacked

A normal process goes like this:

- Researcher finds bug

- Researcher discloses to vendor

- Vendor fixes (or not)

- Researcher discloses bug publically once vendor has fixed, or after X time (whichever is first)

This is roughly how Project Zero goes, and it's a good mix between giving the vendor the opportinity to fix it and deploy the update before it gets exploited.

It's very naive to assume that bugs can be fixed before others can exploit them. Bugs take time to fix, and the process takes time, especially when dealing with large enterprises.

Would also like to add that the video in the article (https://www.youtube.com/watch?v=Qn_4F3foB3Q) is really well made and to the point

Anti-cleverness is what makes Go great. Go code is simple, and it is easy to read/understand. It's a feature of the language

A keyboard is actually a good place to learn some hardware stuff. You can (relatively) easily build a keyboard from scratch and program the chip (excluding USB, which is another can of worms). They are lots of tutorials and documentation online to get you started on it

I think it might be. We had some at my workplace as a celebration and most of us disliked it, however one (of Chinese decent I believe) told us he had it in his childhood and loved it.

Are you sure? The date/time was live for me.

Edit: Looked at the network requests, it's not images. It's returning config files with the information to emulate it. https://download.lenovo.com/bsco/schemas/ThinkPad%20X1%20Car...

I would argue that this definitely depends at which company. The most important position is where the most important component is, and if that's web/front-end, well that'll be the most important position.

If it's callback driven, is it a Promise mistake or a callback mistake? I don't think it would apply here

Are these "common" mistakes? With basic understanding of Promises, these mistakes shouldn't happen. Also I believe #1 is wrong when using async/await.

In the past months, I feel like I see a new useful feature every week. When Microsoft acquired them I was a little scared, but I've been extremely impressed with GitHub since. Microsoft is playing the long game and I think it will pay off immensely for them.

Overlays are quite common on non-TAS speedruns too, it seemed they were real-time

I agree, One UI would definitely win for "most improved" of the skins. Even stock (Pixels) is really great now.

I feel like Android's overall quality in the past couple of years has dramatically improved. Any modern half decent phone will be quite snappy nowadays, and the software has been polished up a lot.

At a past company, we used https://brainbrowser.cbrain.mcgill.ca, which may come in help to you.

That is for in kernel drivers, as stated. It something breaks in kernel, it just won't compile with the kernel, but user space drivers have great ABI compatibility as stated in the link you provided.

Not an expert though, might be wrong but the text makes it pretty clear

Ah yes you are totally right. My bad!

1Password's Android app definitely has the password generator, it's the little gear next to the password field.

In other news, water is wet. More at 11