32

One nice quality-of-life feature on Stack Exchange is the ability to direct users to their own network profile using /current. However, there are a few places where support for /current doesn't seem to have been implemented.

Supports /current

Uses different URL format

Does not support /current

Notes

1Tabs on user and network profile pages are also supported.

3Also works with "mine" but searching user:current will have no effect on search results.

Improve this question
8
  • 3
    Fyi https://stackexchange.com/filters/favorite-tags will already redirect you to your own filters. The user ID isn't needed.
    – animuson StaffMod
    Commented Jul 24, 2017 at 16:41
  • @animuson Thank you for the clarification. I had assumed the user ID was necessary, since the final resolved URL includes the ID.
    – Stevoisiak
    Commented Jul 24, 2017 at 16:44
  • 1
    As well, your Data Explorer example is not something that can ever be supported. Data Explorer runs on open source software and does not have access to the account system for the rest of the network, and accounts there are not in any way attached to the rest of your network profile. Looking up the account ID there is simply not possible and never will be.
    – animuson StaffMod
    Commented Aug 3, 2017 at 16:32
  • 1
    I've removed the filtered questions link completely. It actually does not take a UserId in the URL at all. The Id it inserts into the URL is actually the Id of the filter it selects by default, not your UserId or AccountId. So it doesn't make sense for current to be used there at all. As mentioned before, just using the bare URL works fine for this case.
    – animuson StaffMod
    Commented Sep 6, 2021 at 16:35
  • It also doesn't work for chat, or any of the chat profile tabs
    – caird coinheringaahing
    Commented Sep 6, 2021 at 16:55
  • I note, however, that as this question is currently written, it is not a feature-request. As written, this is just calling attention to the fact that /current is inconsistently implemented and listing the URLs where it is and isn't supported. It doesn't actually ask for any feature change or explain what is actually wanted to be changed regarding any specific URLs.
    – Makyen
    Commented Sep 6, 2021 at 19:37
  • @Makyen My original intent was to see more consistent support for /current. However, now that the three job pages are scheduled for removal, my most straightforward examples no longer apply, so I'm unsure where it leaves my post.
    – Stevoisiak
    Commented Sep 6, 2021 at 21:00
  • 1
    Stevoisiak, I'm not saying the question isn't useful (it is useful, IMO), or that more consistent use of current wouldn't be beneficial. For me, it's just not clear what, if any, action is wanted here, particularly with the bounty from @αλεχολυτ. As a list of where /current (or similar) is function, this question is helpful, IMO. But I couldn't say what action/change is desired which would get this to status-completed as a feature-request or bug, nor what action is really desired from bringing more attention to it with a bounty.
    – Makyen
    Commented Sep 6, 2021 at 21:48

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .