[00:12:09] <MirahezeRelay>	 <notaracham, replying to jenny_on_wiki> Oh hell yeah hot pink
[00:13:22] <MirahezeRelay>	 <notaracham> https://discord.com/channels/407504499280707585/615786602454581249/1231386331662385234
[00:13:33] <MirahezeRelay>	 <notaracham> https://cdn.discordapp.com/attachments/1225560610628964423/1556459294126514296/image.png?backend=b2&ex=6ac43d2d&is=6ac2ebad&hm=a2b2fc00f95c96b2224f6004d8b7575b268ab307b298c8f9827f047b8da014c5&
[00:13:58] <MirahezeRelay>	 <notaracham> I miss that neon pink, it was such an odd choice
[00:14:23] <MirahezeRelay>	 <notaracham> Oh fun, and that was from the grogu pfp era too
[00:49:47] <MirahezeRelay>	 <crystalite13> my pfp hasnt changed since christmas
[00:49:51] <MirahezeRelay>	 <crystalite13> i used to not have this hat
[01:54:30] <MirahezeRelay>	 <justanotherdarkmodeuser, replying to jenny_on_wiki> Damn 2014 is like...12 years ago?
[04:12:16] <MirahezeRelay>	 <crystalite13> @posix_memalign i think miraheze monthly is almost ready for publishing
[04:31:23] <MirahezeRelay>	 <posix_memalign> I'll do a final pass now
[05:21:10] <MirahezeRelay>	 <ccxtwf> [1/2] apologies if this has alr been internally decided as low priority but I'd love to know T&S/Compliance's view on extensions that show real names
[05:21:10] <MirahezeRelay>	 <ccxtwf> [2/2] https://issue-tracker.miraheze.org/T16244
[05:22:53] <MirahezeRelay>	 <ccxtwf> The default disclosure text on Special:Preferences does say that the real name "will be used for giving you attribution for your work" but because some of these extensions are able to save the real names onto a page's history (looking at MyVariables and NewUserMessage), I wonder if that's worth looking into?
[05:27:39] <MirahezeRelay>	 <ccxtwf> [1/2] On the Security side I wonder if extensions being able to access `user_real_name` is a gap of some sort? I did look into Phabricator to see if discussion has been had with this but so far I'm only getting the impression that WMF is internally treating "real name" as something interchangeable with "display name". In my point of view it being called "real name" does necessitate it to be
[05:27:39] <MirahezeRelay>	 <ccxtwf> [2/2]  treated as sensitive PII, even if WMF itself does not or no longer intends to treat the field as sensitive PII.
[05:28:02] <MirahezeRelay>	 <ccxtwf> Ref https://phabricator.wikimedia.org/T154177
[05:39:56] <MirahezeRelay>	 <ccxtwf> https://phabricator.wikimedia.org/T306248
[05:43:12] <MirahezeRelay>	 <posix_memalign> I added @notaracham to the Phorge thread as well. He is probably in the best position to determine whether this needs tech attention.
[05:51:23] <MirahezeRelay>	 <posix_memalign> Also published MH Monthly. @pixldev I featured the new RfC in #minor-announcements since you said we should make an announcement about it.
[05:53:17] <MirahezeRelay>	 <posix_memalign> We also need more writers for MH Monthly. Ideally I just need to write about all the tech stuff. Wiki highlights, RfCs, and volunteer changes can be written by another editor. Right now @crystalite13 is doing lots of good work and hopefully we can distribute the workload further so that no one is tasked with doing too much of the work.
[07:32:11] <MirahezeRelay>	 <notaracham, replying to posix_memalign> Seen, will respond when time permits, juggling a lot of dayjob things at the moment
[17:59:46] <MirahezeRelay>	 <uranium_mandy, replying to posix_memalign> I can help with writing MH Monthly
[18:23:40] <MirahezeRelay>	 <posix_memalign, replying to uranium_mandy> [1/2] Awesome! It mostly involves adding new content as the month progresses (e.g. someone got a new user group -> add it to MH Monthly; the status of an RfC changed -> add it to MH Monthly). Ideally we do this as the month progresses, and then at the end of the month there won't be as much work as before since we just need to put the pieces together. Havi
[18:23:40] <MirahezeRelay>	 <posix_memalign, replying to uranium_mandy> [2/2] ng more volunteers be on the watch for new changes would be a big help.