But generic type syntax is a feature exclusive to Typescript while typeof is a JavaScript thing. You’d never get Pie[Pie[T]] as a result from a typeof check. (Please excuse the square brackets; seems like the markdown parser here isn’t quite right and it keeps messing up the angle brackets)

Also, it’s typeof foo not typeof(foo) in js

factoid actualy just statistical error. average palestinian eats 0 pieces of bread per day. Breads Georg, who lives in cave & eats over 190,000 each hour, is an outlier adn should not have been counted

What is this from?

Libre

There are some cases where any must be used instead of unknown but they usually involve generic constraints and seem more like a bug than intended behavior

No no, 10 base 512 lines of code

I don’t think that’s as Indian-specific as you think

Someone’s trying to smash a stack

It makes sense if you just think of everything as a function.

JSX can exist without React; it’s essentially just an alternative syntax for function calls.

(That is, annoyingly, handicapped in the Typescript checker)

Chrome will show :D when you have over a hundred tabs. Firefox shows ∞

I know this from extensive experience

JABBERLOOP

Not really relaxing but good

There have been a couple attempts at platform agnostic playlist services… none of them seem to be up anymore.

That said, link it. I think people without accounts can at least see the list?

This happens all the time. I feel like a big reason people don’t like meetings is that they tend to involve a lot of bikeshedding.

Ah yes. Drinking beers is a great way to… hide alcoholism.

Well yes. But that’s not why they’re trying to impeach him.

It’s millions of dollars

Okay, so generally the way it works is you have some app (e.g. Google Authenticator, 1password, Aegis, Bit warden – anything that supports TOTP). When you enable 2FA for a site, it’ll give you a QR code. You scan that with your app and then the app gives you a six digit code that changes every 30 seconds.

The QR code is really just an easy way to get a long string of characters into your app, though, and if the QR code doesn’t work there should be an option to see the raw code and manually enter it.

You enter that code in once to confirm that you have actually set up the 2FA. Then it will show you a list of recovery codes. It’ll only show you these once; it doesn’t store them anywhere. You need to note them down in whatever way suits you best (I print mine; you could also just write them down). You cannot see these again. The best you can do, if you still have access to your account, is generate new ones (probably by disabling and re-enabling 2FA)

Now, whenever you login, you’ll be asked for your authenticator code (much like an SMS). You just open whatever app you used and enter in whatever code it’s currently showing (remember it’s time based).

If your authenticator app gets messed up somehow, you can recover it using your recovery codes.

Print off your recovery codes and keep them safe. If you want to be extra, hammer them into metal plates like the crypto weirdos do.