Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

Oct. 24, 2015 (Jon Ericson)

A while back I circulated an idea internally to let everyone see display name changes. The complication is that we don't know why people change their display names and sometimes they might have very good reasons to conceal their identity. Obviously it's still be possible to connect accounts to old accounts if you dig into comment replies and such. But it seems like a user has a reasonable expectation that old display names will remain private if they haven't posted anything with them.

Giving this information to moderators is not a problem since they are bound by the moderator agreementmoderator agreement. Making the information easily accessible is probably not a problem when it's possible to find the old display name on the site associated with the user. But figuring that out is complicated and error-prone. Our developers told me that it would be easier to block people from changing their display names instead of my scheme. So while I love the utility of this proposal, I don't think we can make it happen.


The ability to see all of a user's past display names/aliases.

Reference this popular feature request (and many others).

This is already available for moderators and partially available from the API (needs to be in SEDE too). Plus Jeff did sort of promise it for everybody, long ago (and several redesigns ago):

We do have this information, and we can expose it. But the user page is quite busy already and needs a redesign, so I am not sure exactly when we will get to that.

Oct. 24, 2015 (Jon Ericson)

A while back I circulated an idea internally to let everyone see display name changes. The complication is that we don't know why people change their display names and sometimes they might have very good reasons to conceal their identity. Obviously it's still be possible to connect accounts to old accounts if you dig into comment replies and such. But it seems like a user has a reasonable expectation that old display names will remain private if they haven't posted anything with them.

Giving this information to moderators is not a problem since they are bound by the moderator agreement. Making the information easily accessible is probably not a problem when it's possible to find the old display name on the site associated with the user. But figuring that out is complicated and error-prone. Our developers told me that it would be easier to block people from changing their display names instead of my scheme. So while I love the utility of this proposal, I don't think we can make it happen.


The ability to see all of a user's past display names/aliases.

Reference this popular feature request (and many others).

This is already available for moderators and partially available from the API (needs to be in SEDE too). Plus Jeff did sort of promise it for everybody, long ago (and several redesigns ago):

We do have this information, and we can expose it. But the user page is quite busy already and needs a redesign, so I am not sure exactly when we will get to that.

Oct. 24, 2015 (Jon Ericson)

A while back I circulated an idea internally to let everyone see display name changes. The complication is that we don't know why people change their display names and sometimes they might have very good reasons to conceal their identity. Obviously it's still be possible to connect accounts to old accounts if you dig into comment replies and such. But it seems like a user has a reasonable expectation that old display names will remain private if they haven't posted anything with them.

Giving this information to moderators is not a problem since they are bound by the moderator agreement. Making the information easily accessible is probably not a problem when it's possible to find the old display name on the site associated with the user. But figuring that out is complicated and error-prone. Our developers told me that it would be easier to block people from changing their display names instead of my scheme. So while I love the utility of this proposal, I don't think we can make it happen.


The ability to see all of a user's past display names/aliases.

Reference this popular feature request (and many others).

This is already available for moderators and partially available from the API (needs to be in SEDE too). Plus Jeff did sort of promise it for everybody, long ago (and several redesigns ago):

We do have this information, and we can expose it. But the user page is quite busy already and needs a redesign, so I am not sure exactly when we will get to that.

replaced http://stackapps.com/ with https://stackapps.com/
Source Link

Oct. 24, 2015 (Jon Ericson)

A while back I circulated an idea internally to let everyone see display name changes. The complication is that we don't know why people change their display names and sometimes they might have very good reasons to conceal their identity. Obviously it's still be possible to connect accounts to old accounts if you dig into comment replies and such. But it seems like a user has a reasonable expectation that old display names will remain private if they haven't posted anything with them.

Giving this information to moderators is not a problem since they are bound by the moderator agreement. Making the information easily accessible is probably not a problem when it's possible to find the old display name on the site associated with the user. But figuring that out is complicated and error-prone. Our developers told me that it would be easier to block people from changing their display names instead of my scheme. So while I love the utility of this proposal, I don't think we can make it happen.


The ability to see all of a user's past display names/aliases.

Reference this popular feature request (and many others).

This is already available for moderators and partially available from the APIpartially available from the API (needs to be in SEDE too). Plus Jeff did sort of promise it for everybody, long ago (and several redesigns ago):

We do have this information, and we can expose it. But the user page is quite busy already and needs a redesign, so I am not sure exactly when we will get to that.

Oct. 24, 2015 (Jon Ericson)

A while back I circulated an idea internally to let everyone see display name changes. The complication is that we don't know why people change their display names and sometimes they might have very good reasons to conceal their identity. Obviously it's still be possible to connect accounts to old accounts if you dig into comment replies and such. But it seems like a user has a reasonable expectation that old display names will remain private if they haven't posted anything with them.

Giving this information to moderators is not a problem since they are bound by the moderator agreement. Making the information easily accessible is probably not a problem when it's possible to find the old display name on the site associated with the user. But figuring that out is complicated and error-prone. Our developers told me that it would be easier to block people from changing their display names instead of my scheme. So while I love the utility of this proposal, I don't think we can make it happen.


The ability to see all of a user's past display names/aliases.

Reference this popular feature request (and many others).

This is already available for moderators and partially available from the API (needs to be in SEDE too). Plus Jeff did sort of promise it for everybody, long ago (and several redesigns ago):

We do have this information, and we can expose it. But the user page is quite busy already and needs a redesign, so I am not sure exactly when we will get to that.

Oct. 24, 2015 (Jon Ericson)

A while back I circulated an idea internally to let everyone see display name changes. The complication is that we don't know why people change their display names and sometimes they might have very good reasons to conceal their identity. Obviously it's still be possible to connect accounts to old accounts if you dig into comment replies and such. But it seems like a user has a reasonable expectation that old display names will remain private if they haven't posted anything with them.

Giving this information to moderators is not a problem since they are bound by the moderator agreement. Making the information easily accessible is probably not a problem when it's possible to find the old display name on the site associated with the user. But figuring that out is complicated and error-prone. Our developers told me that it would be easier to block people from changing their display names instead of my scheme. So while I love the utility of this proposal, I don't think we can make it happen.


The ability to see all of a user's past display names/aliases.

Reference this popular feature request (and many others).

This is already available for moderators and partially available from the API (needs to be in SEDE too). Plus Jeff did sort of promise it for everybody, long ago (and several redesigns ago):

We do have this information, and we can expose it. But the user page is quite busy already and needs a redesign, so I am not sure exactly when we will get to that.

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

Oct. 24, 2015 (Jon Ericson)

A while back I circulated an idea internally to let everyone see display name changes. The complication is that we don't know why people change their display names and sometimes they might have very good reasons to conceal their identity. Obviously it's still be possible to connect accounts to old accounts if you dig into comment replies and such. But it seems like a user has a reasonable expectation that old display names will remain private if they haven't posted anything with them.

Giving this information to moderators is not a problem since they are bound by the moderator agreement. Making the information easily accessible is probably not a problem when it's possible to find the old display name on the site associated with the user. But figuring that out is complicated and error-prone. Our developers told me that it would be easier to block people from changing their display names instead of my scheme. So while I love the utility of this proposal, I don't think we can make it happen.


The ability to see all of a user's past display names/aliases.

Reference this popular feature requestthis popular feature request (and many others).

This is already available for moderatorsalready available for moderators and partially available from the API (needs to be in SEDE too). Plus Jeff did sort of promise it for everybody, long ago (and several redesigns ago)Jeff did sort of promise it for everybody, long ago (and several redesigns ago):

We do have this information, and we can expose it. But the user page is quite busy already and needs a redesign, so I am not sure exactly when we will get to that.

Oct. 24, 2015 (Jon Ericson)

A while back I circulated an idea internally to let everyone see display name changes. The complication is that we don't know why people change their display names and sometimes they might have very good reasons to conceal their identity. Obviously it's still be possible to connect accounts to old accounts if you dig into comment replies and such. But it seems like a user has a reasonable expectation that old display names will remain private if they haven't posted anything with them.

Giving this information to moderators is not a problem since they are bound by the moderator agreement. Making the information easily accessible is probably not a problem when it's possible to find the old display name on the site associated with the user. But figuring that out is complicated and error-prone. Our developers told me that it would be easier to block people from changing their display names instead of my scheme. So while I love the utility of this proposal, I don't think we can make it happen.


The ability to see all of a user's past display names/aliases.

Reference this popular feature request (and many others).

This is already available for moderators and partially available from the API (needs to be in SEDE too). Plus Jeff did sort of promise it for everybody, long ago (and several redesigns ago):

We do have this information, and we can expose it. But the user page is quite busy already and needs a redesign, so I am not sure exactly when we will get to that.

Oct. 24, 2015 (Jon Ericson)

A while back I circulated an idea internally to let everyone see display name changes. The complication is that we don't know why people change their display names and sometimes they might have very good reasons to conceal their identity. Obviously it's still be possible to connect accounts to old accounts if you dig into comment replies and such. But it seems like a user has a reasonable expectation that old display names will remain private if they haven't posted anything with them.

Giving this information to moderators is not a problem since they are bound by the moderator agreement. Making the information easily accessible is probably not a problem when it's possible to find the old display name on the site associated with the user. But figuring that out is complicated and error-prone. Our developers told me that it would be easier to block people from changing their display names instead of my scheme. So while I love the utility of this proposal, I don't think we can make it happen.


The ability to see all of a user's past display names/aliases.

Reference this popular feature request (and many others).

This is already available for moderators and partially available from the API (needs to be in SEDE too). Plus Jeff did sort of promise it for everybody, long ago (and several redesigns ago):

We do have this information, and we can expose it. But the user page is quite busy already and needs a redesign, so I am not sure exactly when we will get to that.

added 16 characters in body
Source Link
wythagoras
  • 9.3k
  • 33
  • 68
Loading
Thank you for the suggestion. I really wish I could make it happen.
Source Link
Jon Ericson
  • 79.6k
  • 34
  • 244
  • 343
Loading
Source Link
Awesome Poodles
  • 20.6k
  • 5
  • 46
  • 91
Loading