we've been aware for a week or so, haven't had time for this yet. i'm subscribed to github releases but they are somehow completely bugged. while i get release notifications for other software i am somehow not getting them for blorp. since the repo was moved to the blorp org i've only gotten 2 release notifications from github for 1.9.26 and 1.10.2. i've never knowingly had this issue with other github releases.
edit: we should be getting to this in the next days, forgot to include that.
These cases are not about murder, but death sentences following due process. While it's not exactly the same, it's still calling for violence, even if it's in a more civilized and more commonly accepted way. Murder generally refers to unlawful killings.
I will take this to our team to discuss. Although I'm personally against death penalties, as I don't believe anyone can be trusted with this power as it will absolutely get abused and mistakes will be made, I think discussion surrounding death penalties in general should be allowed, provided there is due process involved. Discussion without referencing specific cases is also not easily possible. This is something that can be difficult to define, as for example Israel also claims there to be due process for the Palestinians they execute and lawfulness can often be quickly changed in favor of the acting regime.
This is definitely a comment that could have been phrased a lot better, but I don't see how this could even remotely be considered a call for violence.
i just searched through our conversations for mentions of murder, kill, israel, zion or palest, and there is nothing relevant.
you just claimed that jordan was calling for people to be murdered, so please provide references for this.
i don't remember everything we've talked about and i'm not going to read through everything again, but you clearly seem to know what you're referring to, so that should be easy to find. i doubt that this exists in the first place, and if it does, it was likely acted on already.
i'm fully aware that there are other issues you have with jordan, but since you brought up claims of calling for murder, let's focus on that.
we are not zionists. if you call for zionists to be murdered and then call us zionists that is a call to murder us, despite a lot of people claiming that it's "just a harmless political slogan". this is normalization of mass murder. we do not tolerate genocide or other murders either, which is also an accusation that a lot of people are throwing around here. accusations of zionism, mostly from dbzer0/AN users, are constantly thrown around against people that they don't deem to be radical enough.
he is an active member of the community and doesn't already moderate as many communities as e.g. TheTechnician. while I was waiting for a response from lawrence until today, another member of our team, unaware of this post, had independently looked into finding a new mod, and about half a day before i'd gotten around to it, appointed him. this resulted in a bit of an unfortunate timing, but overall I expect dohpaz to be able to take care of this community and also build up a suitable mod team, possibly with the people who posted/commented here.
fwiw, LW/PFW require local users to be at least 18, or, if higher, whatever their local laws define. for other instances this is of course nothing we can control.
I haven't heard back from them yet, I wanted to wait a week from my original comment, especially considering the easter holidays. i'll get back to it later today after work.
please follow https://lemmy.world/post/45059459 for this topic. we're currently waiting to see if we get a response from the current mod, otherwise we'll appoint one or more new mods.
we've been aware for a week or so, haven't had time for this yet. i'm subscribed to github releases but they are somehow completely bugged. while i get release notifications for other software i am somehow not getting them for blorp. since the repo was moved to the blorp org i've only gotten 2 release notifications from github for 1.9.26 and 1.10.2. i've never knowingly had this issue with other github releases.
edit: we should be getting to this in the next days, forgot to include that.