|
|
|
|
|
|
by grey-area
4860 days ago
|
|
|
In the same way that different people viewing: http://facebook.com/ see a different resource? For a web app like FB I don't think this avoidable. All data served is dependent on who you are when you are logged in. For another example of how to handle this better, see twitter: twitter.com - the user's feed, content differs for each user twitter.com/username - the user's public url, for sharing, a proper URI which everyone can use twitter.com/settings/profile - the user's private profile, content differs for each user I agree they shouldn't need that redirection with no id supplied and I suspect it's just a legacy of the original way of showing profiles (profile.php?id=n), they could just redirect it to root instead (shows the same as profile.php it seems) to avoid leaking state. |
|
|