Does magic (me / self) use resource identifiers that go against the principles of REST?

Question

I saw URIs that support magic identifiers for an authenticated user, as shown below:

GET /user/me - list my profile
GET /user/me/photos - list my photos

where the ones below use the actual user id

GET /user/742924
GET /user/742924/photos

The problem that I see is that the same resource identifier points to a different resource depending on the authenticated user.

Is this against any REST principles?

Answer 1

/me , , REST. , , , :

5.2.1.1

REST - . , , : , (, " -" ), , (, ) .., , , , . , , . [...]

/me , , , .

Answer 2

, , , :

REST : . , , , , -, , . REST , , , , . , , , , .

, - .

Answer 3

.

, , , URI. " " "user 742924", .

It can be even worse than “current user”, “last registered user”, “user with a name starting with A”, “oldest user”, etc. All of these can be different resources, even if they can point to the same "user".