EDIT: And the corollary of above is that most people when saying REST actually mean HTTP with correct method use.
If not, then is there a good source on what you mean by REST and HATEOAS?
REST is defined by four interface constraints: identification of resources; manipulation of resources through representations; self-descriptive messages; and, hypermedia as the engine of application state.
What does "REST" mean to you?
I don't think service developers take HATEOAS super-seriously. From what I've seen, returning resources with a URI rather than an identifier is about all many services do to be HATEOAS-ish. Clients are coupled to the server, but that's often okay.
It would be hard not to make that client behave like a browser from the user's point of view.
And if you go with HAL or JSON-LD, you have to use a specific clients for those formats, so not universal anyway.
I tend to agree with "HATEOAS is for Humans"[1], HATEOAS makes sense when interacting with HTML.
[1]: https://intercoolerjs.org/2016/05/08/hatoeas-is-for-humans.h...
To me, like most people, REST means an http-based API where we use GET, POST, PUT, DELETE etc. to interact with resources. This in full understanding that under a literal interpretation of the enlightened one's (Roy Fielding's) utterances, REST mandates HATEOAS, meaning that there are only a few true REST APIs to be seen in the wild.
I also usually use the term RESTful, this seems to be a somewhat widely accepted middleground.
Sort of like how youtube is filled with videos about "damascus steel" which is nothing more than steel of random, irrelevant composition with certain visual pattern akin to actual damascus steel. But again, good luck finding a video about the real deal.
Same can be said about ASMR, and many other misappropriated terms people throw around for clickbait.
Rant over.