at least for the parts on finalizing the decisions, it seems like when the changes were announced, the company had already decided that they would do those things(?)
@starball there was a previous proposal which was a trigger for the strikes?
@VLAZ WRT the 900 on the MSO post? I'm not sure, coulda sworn I'd seen that, but I was also walking someone amazingly clueless through fixing their ngnix config :D
@JourneymanGeek I even tried is:q to see if 900 was maybe the count of questions. But I got ~200 results from that. Which also means answers are going to be ~1200. I tried a straight search for the domain (without url:) but got ~500 results. ¯\_(ツ)_/¯ I think we can conclude that ghosts were the problem.
> The bare minimum for significant software changes is to gather community feedback before finalizing any decisions on making those changes,
also note the paragraph above that one which is specifically about getting mod feedback on changes to mod-enforced-policy. I.e. if there was provision for getting just mod feedback on "significant software changes", I'm pretty sure makyen would have made that clear
Since SE decided to respond to everyone except me on the internal announcement, this answer is a direct and mostly unmodified copy of the questions I posted on the internal announcement [mod-only link] on 2024-08-22. A couple notes have been added after the fact to account for answers provided to...
@starball didn't you just ask if the "Unauthorized access prevention" updates followed a structured, well defined process according to what was agreed upon following the strike or it was a mess?
If that was your question then I guess Zoe reaction to what she calls "the shoe" should answer.
@ꓢPArcheon sorry, yes, (I think) I understand you now. Zoe's answer seems to imply that from the mod side, communication wasn't very clear or open, and they still went ahead without engaging
> If you say in the first act that there is a badge that can be awarded, in the second or third act it absolutely must be awarded. If it's not going to be awarded, it shouldn't be waiting there. - Anton Chekhov
@ShadowWizard sort of depends on what you mean by "manual," but the beta and graduation badges have to be triggered purposefully
I am suggesting a new badge entitled Ninja. This would be a gold badge. And in keeping with the secrecy of true Ninjas, the badge should not be mentioned anywhere except a user's profile page (and after implementation, delete this request to protect that).
What are the requirements for awardin...
Not a Robot is actually self-awarded, which is a bit ironic if you think about it
When you meet a staff member, they give you a $thingy, and the $thingy tells you to $award_process. But strictly speaking it is possible for the $award_process grantee to be someone other than the person who was given the $thingy. And at that point, who's to say whether they are actually "not a robot"?
@ShadowWizard there is logic to determine who should get the badge. I don't think there is logic to award the badge automatically
so essentially, if I remember correctly, what happens is a dev pokes the button that says "give this badge to everyone who deserves it." and that's all they need to do
but no award happens unless button pushed
is this automatic, or is this manual? we have found ourselves in strange ontological territory indeed
Goal
Use the SE API in order to get the lists of the badges for every website in the network. The /badges endpoint provide this data.
Expected result
According to the paging documentation, we can request up to 100 items:
pagesize can be any value between 0 and 100 and defaults to 30
Source: htt...
@Slate the only thing I found funny was that you found it funny. (that's not an insult by the way. I laughed genuinely in good-natured bewilderment). though I have one or two friends who would probably find the story funny.
> This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License online at http://www.gutenberg.org.
Since 2011, normal users have been prevented from voting to undelete posts that were deleted by moderators.
However, today, this answer was undeleted by votes from normal users after having been deleted by a moderator.
It appears that a bug was introduced when the logic for checking if a post was...
@Slate I greatly appreciate it. I don't like abusing chat/your presence to signal boost past the normal process but this seems like a suitably important candidate
it's ok honestly, I don't mind. sometimes a homogenized process is inappropriate. every now and again that's to be expected; it's only when it becomes a habit or a frequent requirement that the process evidently needs revising
other side of the coin, when you throw 50 things into a black box, you expect a couple to go missing
@ShadowWizard Just the normal process through status-review. I could start spam pinging CMs in the TL or if something is extreme I could report a community emergency, which is an option for mods.
It will take around 20-30 minutes to read in full unless you rush it so as to thoroughly destroy the nuances and language involved. Which I will not accept.
this offer is valid for the next zero (0) people who complete the task
The haftara or (in Ashkenazic pronunciation) haftorah (alt. haftarah, haphtara, Hebrew: הפטרה) "parting," "taking leave" (plural form: haftarot or haftoros), is a series of selections from the books of Nevi'im ("Prophets") of the Hebrew Bible (Tanakh) that is publicly read in synagogue as part of Jewish religious practice. The haftara reading follows the Torah reading on each Sabbath and on Jewish festivals and fast days. Typically, the haftara is thematically linked to the parashah (weekly Torah portion) that precedes it. The haftara is sung in a chant. (Chanting of Biblical texts is known as...