9

Alright, so - there have obviously been past questions about updating one's username, e.g. Changing user name does not update @lerts / cites?, Change all @username references in comments when a user changes their name?, and notes about making name changes public for clarity, e.g. Make the "past names" list public info for 30 days after changing your name.

The two relevant points from questions/comments like these can basically (as far as I can tell) be summarized as follows:

Editing past mentions/alerts for old usernames is probably due to the technical difficulty of doing so and its vague pointlessness.

Here I am to make a counterpoint/request that hopefully will not bring down too much wrath upon my head: this sucks for trans users who update their username.

I was pretty active pre-name change, and scattered around the network are tons and tons of references to what is now my deadname. Comments, chat messages, references in answers themselves, and I'm sure other places. I understand that making updates everywhere across all users any time anyone changes their username is...probably unnecessary. However.

I would like to propose that some sort of pipeline/process be implemented so that users could request that their deadname be removed from the site as best as possible. Obviously this might not be able to reach every single mention - ones in answers, for instance - but I'd like it to not be insanely easy to figure out my deadname from looking around. Edit: I completely agree that a fully reliable/completely generalized version is impossible; I'm just looking for a tool that provides at least some assistance.

Please note that I'm not asking the entire network be scoured for every single mention - I'm asking for a semi-automated process, if possible, that can be implemented upon a specific user's request that gets maybe a majority of these old mentions, and potentially some sort of policy where it's allowed to edit old answers/etc to update names.


EDIT: Have been told in the comments that comments are purely text and don't retain references to userID. If this is the case, this is an even more difficult feature request than I thought. However, I'm not going to retract it, and instead ask if there are any possibilities here. I think the underlying problem I've pointed out is major enough that this request is worth retaining, though it seems it will be more difficult/by necessity take a different form than I originally thought.

EDITED again to remove second sub-request as I misread the answer in the related question. Apologies.


Finally, just a general plea: I'm still kind of tired of Mother Meta due to everything that went down in late 2019. Please, please don't ask me 'why this is a big deal,' 'whether this is really important,' refer to me by my old username, try to figure out my old username [completely understandable if you've already run into it], or try to make this into some big 'censorship/positive commands' argument. Please. This paragraph is not intended to incite, just a beg for the overall question to be answered so I don't have to go into the weeds. Thanks.

19
  • 10
    There's no uniqueness to display names. Many other people might be using your deadname and might get caught in the crossfire. And if the process is automated in any way what happens if someone with a more common name wants that removed. Sep 11 at 18:55
  • 1
    @RobertLongson but display names are associated with user ID, right? Or am I misunderstanding what I've read through? Sep 11 at 18:59
  • 3
    Nope, in comments they are just text. Sep 11 at 18:59
  • @RobertLongson ah, okay. I've updated the question to address this - while this will then be much harder than I thought, I still think it's an important issue worth asking. Thank you for your clarification! Sep 11 at 19:03
  • 4
    Worth noting that this does work differently on Teams than everywhere else. If we were to swap to the Teams pinging system, this might be easier to implement.
    – Mithical
    Sep 11 at 19:04
  • 1
    For chat, I guess your best bet is having your messages anonymized. This post gives more details on that.
    – Tinkeringbell Mod
    Sep 11 at 19:08
  • 14
    I explained a bit more thoroughly that it's just not possible. Our developers already thought through this very thoroughly when implementing GDPR and came to the conclusion that comment mentions would just not be covered by those requests. If they decided that even GDPR didn't warrant writing scripts for it, pretty much no reason will even change that decision.
    – animuson StaffMod
    Sep 11 at 19:08
  • ^ I was just writing that up ;) --- It is not technically possible, the software was not designed in the first place to allow a later request to implement this feature: meta.stackexchange.com/a/252030/282094 meta.stackexchange.com/a/366683/282094
    – Rob
    Sep 11 at 19:16
  • 2
    Am I misunderstanding Shog's answer to his own request about making past names public for 30 days? It looks like that's not the case so I'm confused about what you are asking for. Mods can see past names but I don't think regular users can.
    – Catija StaffMod
    Sep 11 at 19:19
  • @Catija I apologize, I did misread that particular section - particularly since the second answer gave an alternate solution to view that info, but it looks like that link is dead. Edited to update. Sep 11 at 19:24
  • 1
    Maybe you can rescope the request a little? Last time I checked, the API exposes a reply_to_user field on comments that could at least be matched with a leading @ mention (unless I am missing the point of the field) uniquely, thus allowing for at least some mentions to be updated. Sep 11 at 22:18
  • 1
    @OlegValter ah makes sense, thank you! Maybe write that up as an answer? Sep 11 at 22:33
  • 1
    @AudenYoung probably :) I need to take a peek at the API again first - but it seems like it is possible. And not at all costly even if made from the outside. Surely it can be done from on the inside (unless I am missing a caveat). Sep 11 at 22:37
  • 1
    @ymb1 thank you so much!! I didn't realize that needed to be updated as well. I've updated :) Sep 11 at 22:51
  • 2
    @AudenYoung upon reading animuson's answer on the thread they linked, they actually answered exactly what I mentioned in my comment above and to a great detail too, so I think my answer here would unnecessarily duplicate things - but it does seem like your request would be possible to grant at least in part Sep 11 at 23:15
13

As mentioned this is really difficult to do as comment mentions are simply part of the comment text. A fully reliable version is impossible, the best we might potentially be able to do is a tool that catches most well-formed and unambiguous mentions. I'm writing down an idea here on how that might work, but I suspect that I'm likely to miss a few issues here:

  1. List all comments that generated an inbox notification for the target user

  2. Extract the @notification out of the comment. Ignore if multiple @notifications are present in the comment (those are not valid anyway, so I'm not sure if they could be present in this list)

  3. Apply the same algorithm that creates the User suggestions while typing an @notification to check how many users this particular @notification would notify

  4. If that is exactly one user which is the target user, replace this @notification with the new name

This will fail for comments with multiple @ characters and for cases where the @notifications are ambiguous. The first case should be rather rare, and the second one is simply not safe to change.

The bigger issue are not the false negatives above, but false positives. The only kind I can think of are cases where the other involved users changed names, so the @notification appears unambiguous today, but wasn't back when it was posted and some users had a different name. This is potentially fixable, but expensive as user names would have to be queried at the date of each comment.

I think the biggest issue is anything that could lead to collateral damage, changing comments that are not actually directed at the target user. The tool must be safe to use as reviewing the changes would mean an unreasonable amount of effort. This tool will also be expensive to run, but that might be acceptable as it will be rarely used.

2
  • 2
    This is an interesting proposal that does seem to address the issues people are discussing - thank you! Interested to see if there are any issues with it. I completely agree that a fully reliable/completely generalized version is impossible; I'm just looking for a tool that provides at least some assistance. Sep 11 at 20:06
  • 1
    "List all comments that generated an inbox notification for the target user". The system already does this. It's the responses tab in your profile, visible to yourself and moderators. (Changing your name may mess this up though.) I understand the complications but I don't see why this couldn't be the starting point for an effective semi-automated system.
    – Laurel
    Nov 23 at 14:25

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .