cross-posted from: https://sopuli.xyz/post/44631447
For the record, @Lalla@slrpnk.net entered my thread to spout some finger-wagging threadcrap:
“Could we at least not use her deadname? I get that the article is old, but please don’t.”
I actually agree with using the proper new names of people in the present to address them in the present. But it’s stupid and disrespectful to drag someone’s new name through their history before they changed their identity. I believe my response to the threadcrap was quite civil. This is what ~~@CurlyWurlies4All@slrpnk.net~~ was surreptitiously censored:
“We are talking about Manning’s history. It is proper to use the name of the time of the events. People don’t create new identities for the hell of it. New identities are generally created for a new life going forward, to be disconnected from a past life.
Europe recognises the right to be forgotten which is enshrined in GDPR art.17. Guatamala respects people’s wishes to establish a new identity to the extent of allowing name changes with no public record in a closed-door session with a judge.
Tying someone’s new name to their prior history is disrespectful. Some may want their legacy to follow them despite a name change and we might guess Manning is proud of their accomplishment, but it’s not for you to decide what people with new identities carry forward from their past.
Please respect people’s privacy. I know Manning’s privacy is toast anyway, but it’s still off to be part of the intrusion and then to ask others to also drag new identities through their prior history.
You also advocate historic inaccuracy. Exxon (a dead name) discovered climate change. Not ExxonMobil. You cause confusion by insisting on refencing new identities in past events. If you say ExxonMobil discovered climate change in the 1960s, you falsely imply that ExxonMobil existed at that time. But in fact the merger (and thus new identity) came after that.
The modlog vaguely states “breaks rules” without citing a specific rule. This was coupled with the cowardess of not DMing me about the action.
The power abuse occurs alongside the decision to allow the rule-breaking threadcrap I defended from to persist. The mod doubles down on their oppression this way. The privacy-disrespecting finger-wag carries on in a community that inherently values privacy.
UPDATE: it was not the mod
Due to a defect in the Lemmy server software, it looked as if the moderator of enshitification did the censorship. But in fact it was the admin of an outside host (sopuli) who did the censorship, which yielded a modlog on slrpnk.net.
Okay well fair warning that line of thinking on gendering people's past is not welcome on here for future reference, so if it comes up in another thread you are expected to gender people correctly when speaking in past-tense
I am not going to keep track of your esoteric personal preferences. If you non-transparently keep this rule concealed, the consequences are on you.
Please put your bizarre new rule in the sidebar so people who accurately discuss past events do not get broad-sided by unexpected interventionalism. The norm is that people use the present gender for present tense chatter, which needs no explicit rule. But this zealous idea of inserting someone’s new identity into their past (prior to the current identity) at the risk of disrepecting their privacy really calls for some explicit wording. Feel free to name the rule of this niche scenario after me, if you want.
UPDATE
I see the new rule in the sidebar. I agree with it. It does not cover this corner case of the context of historic accounts.