[00:07:51] PROBLEM - procs on server.testwiki.wiki is CRITICAL: PROCS CRITICAL: 427 processes [00:10:52] RECOVERY - procs on server.testwiki.wiki is OK: PROCS OK: 170 processes [09:10:03] [discord] Hey @amosisreborn , Thank you updating and issuing the newsletter - I wasn't active around here this month [09:11:40] [discord] I would help around this month 🙂 [09:12:13] [discord] is there a point when the newsletter has zero updates [09:12:24] [discord] at first I liked the idea but there's just, so little going on [09:12:30] [discord] maybe quarterly would be better [09:12:57] [discord] https://cdn.discordapp.com/attachments/1120379200893890762/1301836367373795378/Screenshot_209.png?ex=6725ed18&is=67249b98&hm=ede588571f084d24c2b35ba95e9eadf219ccc1aee871d0915acf1afc434af556& [09:13:23] [discord] Well it has sufficient updates - to deserve a newsletter of its own [09:13:27] [discord] I was looking at another one, but I'll comment about that one [09:13:40] [discord] let me pull it up [09:14:02] [discord] besides the fact things are slow enough you can pretty much glean it from a cursory recent changes scan, even easier with a minor filter [09:14:18] [discord] Well in that case, I agree that if there is little to no activity, then it's not useful to publish one [09:14:57] [discord] Yeah but the newsletter helps everyone to take a glance and look what changes were made in a short time [09:15:07] [discord] so xaloria: removed, readded across three categories, basically nothing to note then [09:16:10] [discord] consequentially this is what happened [09:16:10] [discord] https://cdn.discordapp.com/attachments/1120379200893890762/1301837176224481311/image.png?ex=6725edd9&is=67249c59&hm=0c30ce52e7bf1224d9798f32616c0371946a32551477f8b7ca303ddde5a137f5& [09:16:22] [discord] I'm using a source inspected image to illustrate [09:17:01] [discord] I would assert that the first two, being as routine as giving someone autopatrolled since the whole function is testing, are kinda... meeeh. so really the only 'news' is suppressor and interface administrator. Interesting, but does it mean much? [09:17:36] [discord] especially when the *only* new thing that's happened is kiteretsu as suppressor [09:18:32] [discord] even a note of discussions like the centralauth discussion may give a bit more meat to read, and would probably be relevant to include if we're looking for a meaningful way to expand those [09:19:11] [discord] well it helps when users aren't around here (like I was this month) much - so it helps to note who have joined the community over a past month [09:19:14] [discord] perhaps a summary of the weirder affairs like xaloria, where you don't get an actual idea of what was going on based on the changes list. It's pretty but it is not explanatory. that is a missed opportunity [09:19:30] [discord] only one person 'joined' based on that though, the rest are new-olds [09:19:38] [discord] Yeah that was missing - Maybe someone forgot to add it [09:19:49] [discord] that's an good suggestion [09:19:59] [discord] I will include it in this month's letter [09:20:52] [discord] what would probably make more sense is for the permissions changes to summarize - instead of xaloria being in several categories and it not being terribly clear what happened, perhaps only the outcome is reflected [09:21:51] [discord] the consequence is that xaloria has no rights, therefore the removal is what is relevant - if more information to clarify is needed (which it is now anyway), that is why a blurb would be useful [09:22:52] [discord] september's issue did have more going on for it I'll grant [09:23:27] [discord] could you provide something as draft , so I could know what you want? [09:23:37] [discord] could you provide something as draft of the newsletter , so I could know what you want? (edited) [09:24:04] [discord] honestly most of the previous ones are just enough that I rest my case [09:24:17] [discord] I suppose I took the latest sparse issue as being the rule and not the exception [09:25:14] [discord] but a full example of what I mean isn't needed - it just means that it would be worth thinking how to make changes in a short amount of time make sense, maybe that needs a community discussion if others agree [09:26:04] [discord] in xaloria's case it was not clear where xaloria stands, his rights were added and removed so where was he? it might make sense if an issue just reflects that ultimately, xaloria's rights are removed. Or if it includes both, a brief explanation. [09:26:32] [discord] This one is short but well rounded, https://testwiki.wiki/wiki/Test_Wiki:Administrators'_newsletter/2024/6 [09:26:46] [discord] hmm maybe a " * " sign near his name and then a detailed explanation at the end? [09:27:04] [discord] I guess it would be a section called "permissions news" or, there you go, a * and that section elaborates a bit. [09:28:32] [discord] I feel the system is slightly overengineered for testwiki, but a very good thing to consider for say, wikioasis where those changes can be more consequential to how the farm is run, especially if the idea is a community run farm [09:29:43] [discord] maybe I can create a newsletter for them too 👀 [09:30:17] [discord] that would be a good habit to start early [09:30:36] [discord] maybe run it through people first though [09:31:37] [discord] yeah I will [15:50:21] [discord] @Suppressors : Can the suppression tool on this test page be used for testing? As described on this page? https://testwiki.wiki/wiki/Suppression_test [15:54:52] [discord] @drummingman : 🧐 [16:01:31] [discord] @itsboyhappy Indeed. 🙂 [16:04:25] [discord] @drummingman : [16:04:25] [discord] Many thanks, so can I add the suppressor to your account for testing on this page? [16:06:32] [discord] Only to your own account with the clear notice that it is for testing purposes. [16:07:02] [discord] Ok.. 🙂 [16:07:51] [discord] and then undo it afterward as well. [16:11:14] [discord] Sure! I'll do that after testing it. 😊 [21:42:56] [discord] Discontinued.