It's a good thing everyone's actions take place in a bubble and have no effect on others.

Should I be blocked from everywhere that has fired someone with the same name?

This is just a straight marketing post for Redis.

I'm guessing more than a few found out from this article directly. What a rough way to find out you were laid off.

Not to mention the environmental impact of doing so.

I'm surprised they released the feature as-is.

Is this a given? Just because something is necessary at scale doesn't mean it is a good fit for low scale use cases. I would expect the opposite is actually true.

The customer's cost isn't increased over regular online ordering, and there isn't the issue of increased packaging. The food is fresh from the local supermarket and doesn't have to be shipped, beyond at most a local delivery.

I can imagine at least some companies would stop worrying about security since they are insured if something goes wrong.

How does "search" not convey searching the internet using any search engine?

Timing attacks aren't as simple as often presented. Writers often give a set time for checking each character and ignore all other operations in order to make the issue easy to understand, but most people use this to write off the attack altogether. Surely it can't be that simple.

It isn't trivial to take advantage of timing attacks remotely, but researchers have shown that they are definitely exploitable. [1][2]

[1] https://crypto.stanford.edu/~dabo/papers/ssl-timing.pdf [2] https://www.blackhat.com/docs/us-15/materials/us-15-Morgan-W...

For example, both of these decoded headers are equivalent:

{ "alg": "HS256", "typ": "JWT" }

{ "typ": "JWT", "alg": "HS256" }

Obviously, these encode to two different values. If you reattach the wrong one, signature verification will fail.

Disclaimer: I maintain a Python JOSE library and have had to answer questions related to this on more than one occasion.