It seems like that would just complicate our signin controller logic, to say nothing of the caching implications that change would introduce. Furthermore, the endpoint is currently named appropriately (I think @commuterjoy is only mentioning namespacing so it's clear from the URL which team is responsible for the fragment). This is the profile nav component, which is to say, the fragment in the top nav that implements controls for the user's profile or a signin link if they aren't signed in. Far from helping to clarify it (and thus arguably negating the need for namespacing), overloading the signin URL would make it less clear what this fragment does.