The only one I think is reasonable is GraphQL. But that isn’t rest, and HTTP is just one of the transport layers it supports.

For anything claiming to be RESTful, it’s a crime.

The article is talking about art in promo material.

Think about it: whenever you see a piece of production art featured in a social media post or a press release or a game announcement at a big televised showcase, all you ever see is the art. You never know who made it, whether it was created by an individual or a small team (or even a studio).

(another pet peeve of mine is “rest” APIs that use 200 response codes for everything)

Yup, also some APIs use GET for everything. It’s a pain. And it means that filtering by verb only helps if you’re intimately familiar with the API. And even then, only if you keep up with changes as they happen. So really, only if you’re developing the API yourself.