[13:08:42] Niharika: did the reject applicants for GSoC/Outreach receive a suitable encouraging message telling them that we value further work from them during the year etc.? [13:10:30] Nemo_bis: The usual stock reply: https://www.mediawiki.org/wiki/Outreach_programs/Messages_to_candidates#Candidate_declined I added a few lines asking them to reach out to me if they want to hear feedback on where they went wrong and how they could improve their proposal for the future rounds. A couple of people did. [13:11:15] Ok, good. [14:22:54] Would it be possible to use OAuth simply to validate that my bot is communicating with a Wikimedia user? It wouldn't perform any edits with his/her account. [14:25:26] Phabricator uses OAuth to confirm that a user owns a particular account [14:25:33] So I imagine so [14:25:53] Yeah, I think various people already do this [14:26:04] I mean you'd need a web interface to your bot to allow it [14:26:13] But it should be possible [14:26:19] Why do you ask, Magog_the_Ogre? [14:27:20] To be blunt, because Magnus is an unreliable pain in the ass and refusing to support TUSC, despite claiming that he would. [14:28:26] I'm trying to figure out the best way to create a TUSC v2 [14:29:14] I see. [14:29:37] background for my annoyance: https://commons.wikimedia.org/wiki/User_talk:Magog_the_Ogre#Problem_with_Creation_of_a_TUSC_Account [14:29:59] AFAICS Magnus' tools no longer use TUSC, do they [14:30:27] No, they don't [14:30:35] but he claimed he wouldn't stop supporting it [14:31:02] That sounds like a bad promise to make. [14:31:59] People should just use OAuth directly [14:32:15] that's all well and great [14:32:17] there's no need for another thing that can fail these days [14:32:27] but we have old tools which use TUSC and would port poorly to OAuth [14:33:04] glad you guys are so progressive but I've dealt with many problems related to his tools, and he almost always just ignores them [14:33:19] I'm pretty sick of dealing with Magnus and would like to cut the cord ASAP [14:34:18] If you feel like maintaining a bc tusc no one is keeping you from that [14:34:38] what? [14:34:59] "If you feel like creating and maintaining a backwards-compatible TUSC, no one is keeping you from that"? [14:35:28] I'm trying to figure out if that's doable with OAuth, but I don't think it is. [14:35:36] Why not? [14:36:31] how would the downstream tool verify that the user is who they said they are? [14:36:32] It just seems that Magnus is not going to commit to it, so I don't think there's a point in pushing there [14:36:32] I guess it's open source, so that's probably the starting point here [14:37:06] I hope it's open source, if it's running on tools :) [14:37:08] They'd need to trust your TUSC for that, obviously [14:37:40] OK, I made the mental connection [15:51:55] Staff are not removed from access to shell after they resign. Is it supposed to be like that? [15:52:28] Some staff are removed from access [15:52:30] Some aren't [15:52:39] It depends on whether they want to stay as a volunteer or not [15:53:05] ah, alright [15:53:15] I imagine some people are simply missed when they leave [15:55:14] Anyone in particular you noticed, Glaisher? [15:55:58] several [15:57:30] I attempted to clarify everyone's affiliation where I could here: https://meta.wikimedia.org/wiki/System_administrators#List [15:58:31] I saw that :) [16:01:59] Glaisher, anyone there you think should be marked as a volunteer now instead? [16:17:49] Krenair: yeah Reedy and Eloquence, perhaps? [16:20:01] I have no idea what Reedy's official status is. [16:22:21] I don't think I should comment on Erik's yet. [16:33:50] Krenair: Why can you merge security tickets, but I can't? [16:34:23] ... you can't [16:34:24] ? [16:34:41] I tried to merge them via the UI at least twice and it didn't work [16:34:47] what did it say? [16:34:50] so I assumed it's disabled for security tasks [16:34:57] nothing, it just returned w/o doing anything [16:35:05] weird [16:35:18] Worksforme, sorry