[wp-meta] [Making WordPress.org] #6796: Data Erasure: Update @mentions

Making WordPress.org noreply at wordpress.org
Thu Feb 23 00:10:45 UTC 2023

#6796: Data Erasure: Update @mentions
 Reporter:  dd32                |       Owner:  (none)
     Type:  enhancement         |      Status:  new
 Priority:  normal              |   Milestone:
Component:  WordPress.org Site  |  Resolution:
 Keywords:                      |

Comment (by dd32):

 Replying to [comment:1 Otto42]:
 > Editing other people's content seems like a high risk thing to do.

 I kind of agree, and there's a reason it doesn't already happen. This is
 one reason that a lot of other `@mention` systems store the mention in a
 different format, such as the user ID and insert the username on display.

 The problem is that the current process causes a level of complaints from
 erased accounts who believe erasure should've removed content not created
 by them, but mentions them.

 I don't see something like `$content = str_ireplace( '@username',
 '@anonymized...', $content );` as a high risk operation though. If it were
 replacing `username` yes, but a direct `@username` mention of the username
 in question is much lower risk.

Ticket URL: <https://meta.trac.wordpress.org/ticket/6796#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list