> All those links that you mentioned in the Github api responses are named and you as a client can use them, where the actual url can change. I think that's a

> All those links that you mentioned in the Github api responses are named and you as a client can use them, where the actual url can change. I think that's a good idea, just like REST and HATEOAS are both ideas trying to solve problems. I'm just skeptical that it'd work in practice. It seems vanishingly unlikely that consumers will use it correctly enough that changing the URLs in that mechanism wouldn't result in making the breakage even more mysterious. When I say "it only makes sense if you've got a browser on the other end," the issue is you need a client approaching the complexity of a browser to do all the redirection and such that makes this level of flexibility for the API implementer to work. I believe something like that is possible, but this isn't the way.