WorkLifeBalance

Beating macOS at gaming sounds like a punchline, that's just not impressive, macOS has only ever been an afterthought for gaming.

In which jurisdictions is this deliberate circumvention of access controls legal?

> Is there a name for this type of fatigue

Stress. (One of the smyptoms of)

Stop trying to re-invent statistics. Use a box and whisker plot of latency. You quickly get to see the mean, the quartiles, and all the outliers and you get it in a format which is familiar and easy to understand. You can even plot box and whisker plots next to each other for quick meaningful comparisons between different things.

These may well work on some (cheap?) phones, I've had phones not display properly through polarized sunglasses before.

Specifying something as password hashing as (sha256? salted sha256?) without telling it to seems like magic to me.

So to clarify, it's this password: declaration which tells the framework to hash the input?

    users
        dynamic :  . 'Users'
        password : . 'Password'

    interfaces

    root {

    }

    numerical-types

Is this defined anywhere within the project or is this framework magic? (Or "glue" if you don't like the term magic). password is not mentioned again anywhere in the documentation, I'd like to understand how the framework knows to hash the input.

Where is the definition of the password being hashed? The tutorial defines it as text:

/* 'Users': collection { 'Password': text }*/

How does the platform know to hash that? Is it looking for magic property names?

How do you take this from here to the next step?

Let's say I want to develop a multi user todo and I've followed the examples and now have some Users who log in entering a password.

Someone points out that I shouldn't be storing passwords in plain text so I want to store them hashed.

Despite there being hints in the documentation that this is possible (migrations shows the password hashed), it's not clear how to carry out this kind of change.

A walkthrough of making a change would help convey the use case much better than just templates of "this incantation produces this output".

Modern tests are delivered by computer and typically are adaptive. This means that as you answer questions correctly you get asked increasingly difficult questions until you get some wrong.

This means that you aren't limited to asking the same questions to everyone so you can have appropriate discrimination through the range.

The difference between 99th and 99.99th percentile is 1.4 standard deviations, a common IQ test ought to be able to be accurate to that. Otherwise it couldn't measure the difference between 100 and 120 IQ (0 to 1.4z) which it clearly can.

Meta doesn't imply cycling, just that the best strategy may be a mixed strategy which involves randomly picking between different pure strategies.

Instead of cycling, the meta ought to converge to a Nash equilibrium.

With the right mixed strategy, an opponent choosing a pure strategy would be at a disadvantage.

Randomising over a huge choice of pure strategies may be infeasible of course and in the real world players have to train for particular strategies which is why we see meta shifts. (Plus of course in the real world the conditions (assumptions) change due to gameplay patches.

It's a stretch to say it results in cheaters, people have been writing cheats since quakeworld.

There's a better solution: Stop collecting and keeping personal data.

I can't even read this article without using firefox reader mode to skip the cookie warning / prompt (this works for a lot of sites!).

That's a choice that techdirt make. By framing it as an unavoidable consequence of the cookie legislation or GDPR moves the focus to the wrong place.