→ECP: Reply Tag: Reply |
|||
Line 90: | Line 90: | ||
::::::::I just do not think a matter like that is best decided by just twelve editors, nor do I feel it is within ArbCom's purview to make such a decision unilaterally. Whatever the right outcome is here, the resolution of that question and a change this drastic should have been put before the community. If because of the scale of the implications and kniock-on effects if nothing else. So this is a worrisome precedent to me. ''[[User:Snow Rise|<b style="color:#19a0fd;">S</b><b style="color:#66c0fd">n</b><b style="color:#99d5fe;">o</b><b style="color:#b2dffe;">w</b><b style="color:#B27EB2;">Rise</b>]][[User talk:Snow Rise|<sup><b style="color:#d4143a"> let's rap</b></sup>]]'' 01:04, 24 November 2023 (UTC) |
::::::::I just do not think a matter like that is best decided by just twelve editors, nor do I feel it is within ArbCom's purview to make such a decision unilaterally. Whatever the right outcome is here, the resolution of that question and a change this drastic should have been put before the community. If because of the scale of the implications and kniock-on effects if nothing else. So this is a worrisome precedent to me. ''[[User:Snow Rise|<b style="color:#19a0fd;">S</b><b style="color:#66c0fd">n</b><b style="color:#99d5fe;">o</b><b style="color:#b2dffe;">w</b><b style="color:#B27EB2;">Rise</b>]][[User talk:Snow Rise|<sup><b style="color:#d4143a"> let's rap</b></sup>]]'' 01:04, 24 November 2023 (UTC) |
||
:::::::::I personally think there are better hills to die on; we as a community have already basically accepted that the Israeli-Palestinian conflict topic area cannot be effectively administered with our normal procedures, and we have already ceded to ArbCom basically limitless authority to manage that topic area so that the administrators we do have that are willing to step in to keep things somewhat in line with our behavioral policies are not overwhelmed with so much low-level crap that they are unable to deal with the more complicated problems. I understand the frustration, at the time they were discussing this at ARCA there was one user with like 300 edits who I saw being completely constructive and I wanted them to be able to continue being so (and this was a user that I feel comfortable placing firmly on the "pro-Israel" side of the spectrum). But there is still so. much. bullshit that happens in these articles everyday. I have literally zero doubt that on basically every RFC, move request, or AFD that what we now know to be {{u|AndresHerutJaim}}, as {{u|יניב הורון}} (Yaniv) was just a sock of his, is mass emailing at least a dozen accounts to get them to vote. I have zero doubt that he is doing the same for various editing disputes across a range of pages. 30/500 isnt an insurmountable barrier, otherwise we wouldnt still be getting NoCal100 and Icewhiz socks regularly, but it does at least quiet some of the noise down. As far as ''to the pretty steep price of removing all productive non-EC perspectives'', I really think that is overestimating that price. Most of the commentary is not all that productive. Yes, some of it is, and the rules still allow for edit requests for anybody that wants to make a constructive comment. But most of it is bare voting and forumming. <small style="border: 1px solid;padding:1px 3px;white-space:nowrap">'''[[User talk:Nableezy|<span style="color:#C11B17">nableezy</span>]]''' - 18:43, 24 November 2023 (UTC)</small> |
|||
== GA nom of the Israeli occupation of the West Bank article == |
== GA nom of the Israeli occupation of the West Bank article == |
Revision as of 18:43, 24 November 2023
Deletion of content based on a reliable source
Can you show me where it was said that Arutz Sheva a garbage source? You also removed content from Maariv, which is one of the most-read newspapers in Israel and a reliable source. Why did you remove it? Eladkarmel (talk) 16:58, 31 October 2023 (UTC)
- Per BLP, this hearsay needs stronger sourcing. As far as Arutz Sheva, see here or here or for example the NYT describing it as "a news organization that represents the view of Israeli settlers in the West Bank". Im sure I can find more, but its reliable for the views of settlers and thats it. nableezy - 17:05, 31 October 2023 (UTC)
- Huh? Agree with you on the need for good sourcing for BLP. But bias is not indicative of reliability, as you've rightly argued many times elsewhere. Neither RSN reflects a consensus view that AS/INN or Maariv are unreliable. The NYT does not say AS only reliable for "the view of settlers." RS also say that Al-Jazeera represents the view of Qatar. But we wouldn't say that AJ is only good for the views of Qatar and that's it. Longhornsg (talk) 22:17, 31 October 2023 (UTC)
- Arutz Sheva has a long history of being a settler mouthpiece, and for any material related to Qatar I would not be using al Jazeera either. But see for example: such as the establishment of the radio station Arutz Sheva, which represents the settlers, Arutz Sheva, the settlers radio station or Arutz Sheva, a settler source. It is a garbage source, and there are countless other Israeli sources of much higher quality that we can, and do, use. nableezy - 22:29, 31 October 2023 (UTC)
- Popping back in, though I love talk page debates, as no arguments provided here resonate with me and sound like WP:DONTLIKE. Sure, Arutz Sheva is biased. But bias != unreliable, and excluding a source that is quoted extensively by other RS solely for its perceived biased (but that produces similar journalism as other RS in this area) would be a violation of NPOV, just as excluding Al-Jazeera Arabic or Al-Arabiya, etc, would be. And there's no consensus that AS is "garbage" (despite umpteen threads at RSP). Longhornsg (talk) 08:06, 9 November 2023 (UTC)
- Arutz Sheva isnt extensively quoted by anybody, so the rest of the comment does not follow. nableezy - 10:08, 9 November 2023 (UTC)
- If Obama, a Muslim who is not known to have ever apostasized, is elected, then 'Israel is screwed'. That is just one of hundreds of articles one could link to to document the moronic, hysterical, extremist quality of its input.Nishidani (talk) 16:16, 9 November 2023 (UTC)
- I'm not denying the site posts some looney-bin op-eds. So does the Guardian, Counterpunch, Washington Report, and a whole host of other outlets you would likely deem RM. Again, that has no bearing on its reliability for facts. Longhornsg (talk) 22:12, 9 November 2023 (UTC)
- Compare how Arutz Sheva covered the material under discussion here and how a more respectable outlet did: A7: The Palestinian activist and terrorist supporter Ahed Tamimi called for the murder of the settlers in Judea and Samaria. In a post she uploaded today (Tuesday) to her Instagram account, Tamimi wrote ... vs Haaretz: Palestinian activist Ahed Tamimi was arrested overnight into Monday by the Israeli army after allegedly threatening to kill Jewish settlers. Reuters: Israeli troops on Monday arrested a Palestinian activist, regarded in the occupied West Bank as a hero since she was a teenager, on suspicion of inciting violence, but her mother denied the claim and said it was based on a fake Instagram post. So we have A7 making a statement of fact that Tamimi did such a thing, before she was even charged, we have Haaretz saying she is alleged to have done these things, and we have Reuters saying she is alleged to have done this things and the allegation has been denied by her family. You think A7 is reliable for facts that Tamimi did these things that all the responsible outlets are saying she is merely alleged to have done, and more than that most of them include the denial? Where A7 simply says, without any substantiation whatsoever, that Tamimi is a. a terrorist supporter, and b. wrote in Hebrew a Nazi inspired threat, and c. that this is a fact so clear we shouldnt even include a denial? Well if you feel that way thats nice for you, I do not. And I will continue to remove bullshit sources like A7 where I see them, and I dont need a consensus that it is generally unreliable to do that. I dont need that consensus for Stormfront either. nableezy - 22:23, 9 November 2023 (UTC)
- I'm not denying the site posts some looney-bin op-eds. So does the Guardian, Counterpunch, Washington Report, and a whole host of other outlets you would likely deem RM. Again, that has no bearing on its reliability for facts. Longhornsg (talk) 22:12, 9 November 2023 (UTC)
- If Obama, a Muslim who is not known to have ever apostasized, is elected, then 'Israel is screwed'. That is just one of hundreds of articles one could link to to document the moronic, hysterical, extremist quality of its input.Nishidani (talk) 16:16, 9 November 2023 (UTC)
- Arutz Sheva isnt extensively quoted by anybody, so the rest of the comment does not follow. nableezy - 10:08, 9 November 2023 (UTC)
- Popping back in, though I love talk page debates, as no arguments provided here resonate with me and sound like WP:DONTLIKE. Sure, Arutz Sheva is biased. But bias != unreliable, and excluding a source that is quoted extensively by other RS solely for its perceived biased (but that produces similar journalism as other RS in this area) would be a violation of NPOV, just as excluding Al-Jazeera Arabic or Al-Arabiya, etc, would be. And there's no consensus that AS is "garbage" (despite umpteen threads at RSP). Longhornsg (talk) 08:06, 9 November 2023 (UTC)
- Arutz Sheva has a long history of being a settler mouthpiece, and for any material related to Qatar I would not be using al Jazeera either. But see for example: such as the establishment of the radio station Arutz Sheva, which represents the settlers, Arutz Sheva, the settlers radio station or Arutz Sheva, a settler source. It is a garbage source, and there are countless other Israeli sources of much higher quality that we can, and do, use. nableezy - 22:29, 31 October 2023 (UTC)
- Huh? Agree with you on the need for good sourcing for BLP. But bias is not indicative of reliability, as you've rightly argued many times elsewhere. Neither RSN reflects a consensus view that AS/INN or Maariv are unreliable. The NYT does not say AS only reliable for "the view of settlers." RS also say that Al-Jazeera represents the view of Qatar. But we wouldn't say that AJ is only good for the views of Qatar and that's it. Longhornsg (talk) 22:17, 31 October 2023 (UTC)
- "Most read" ≠ good; The Sun/Daily Mail are the most read in the UK, and crap. Iskandar323 (talk) 19:12, 31 October 2023 (UTC)
- Arutz Sheva hosts a writer driven out of mainstream Italian newspapers because he plagiarized stuff. It hosted articles by people arguing for conspiracy theories about Obama. It is happy with ethnic cleansing. It cannot be used for facts, but, rarely, for settlers' opinions. That is obvious. We don't use The Electronic Intifada by consensus, and the same should go for a partisan rag of dubious worth, like Arutz Sheva on the other side of the line.Nishidani (talk) 22:25, 31 October 2023 (UTC)
Saying Sorry!
I just saw your reply and I have to say sorry. I reverted to remove vandalism and made my way through all the edits that were made in between to manually reinstated as per RV. I reinstated your edits here [1] and here [2] but may have missed one.
Just wanted to say apologise and happy editing! Jo Jc JoTalk💬Edits📝 15:08, 10 November 2023 (UTC)
- Oh no worries, I didnt even notice. nableezy - 15:19, 10 November 2023 (UTC)
Dovidroth
Hi there, I recently came across your post on Dovidroth's behavior in regards to their topic ban and for what it's worth, Dovidroth still engages in such behaviors (1, 2), particularly socks of AndresHerutJaim/Yaniv Horon. There are likely a few more discreet examples where Dovidroth would "repackage" their edits instead of outright re-reverting but I am unfortunately a bit too busy to sift through all their edits at the moment. John Yunshire (talk) 02:22, 11 November 2023 (UTC)
A barnstar for your efforts
![]() |
The Current Events Barnstar | |
For your efforts contributing to the page 2023 Israel–Hamas war. Awarded by Cdjp1 (talk) 16:04, 11 November 2023 (UTC) |
- Thank you very much very kind of you. nableezy - 03:44, 16 November 2023 (UTC)
Addition of the info on helicopter
Hello! Have you seen this edit and it's comment right before you have added the info again? Could you please clarify why you have done it? Please also see this and this. Do you mind to remove what you have added? Thank you! With regards, Oleg Y. (talk) 18:24, 19 November 2023 (UTC)
- yeah, no, Im not removing Haaretz reporting on Israeli investigations because PolitiFact discusses some other video that has nothing to do with what Haaretz reported. I dont know what NewsRu is, and based on my quick perusal of sources it doesnt come close to Haaretz in terms of reliability. Beyond that, Haaretz doesnt report this as an Israeli police investigation, but Israeli security services, which would include the Shin Bet and be outside of a police official's ability to respond to. nableezy - 19:15, 19 November 2023 (UTC)
- You can find what is NEWSru here: NEWSru. And it was not the only source. Here is another one. With regards, Oleg Y. (talk) 19:47, 19 November 2023 (UTC)
- Ill include the Times of Israel on the police denial, thanks for the source. That doesnt justify the removal of the Haaretz article however. nableezy - 19:47, 19 November 2023 (UTC)
- You can find what is NEWSru here: NEWSru. And it was not the only source. Here is another one. With regards, Oleg Y. (talk) 19:47, 19 November 2023 (UTC)
ECP
You should just revert IPs engaging in content discussion, drop them a quick explainer on ECP, and report them if they continue to take part in discussions establishing consensus on article content.
Your effort is wasted because their thoughts on the content wom't be considered when it comes to deciding on how the article reads. ScottishFinnishRadish (talk) 02:29, 20 November 2023 (UTC)
- Ok, will do, thank you. nableezy - 02:30, 20 November 2023 (UTC)
- ScottishFinnishRadish, I saw Nableezy's comments on the talk page in question on this matter and came here to inquire about where they were getting the assertion that "Non-extended users cannot contribute to consensus discussion on ARBPIA articles". I've reviewed ARBPIA4 and I see no reference to such a sanction--and indeed, I would have expected there to have been an absolute furor of argument if ArbCom had tried to create such a rule whole-cloth, limiting WP:ANYONECANEDIT in such a way without a strong community mandate for such.
- And I've just reviewed ECP as well to make sure I am up to date on any changes there, and I see no evidence of such a rule expressed there either. Rather ECP says only that extended confirmed protection can be applied to CTOP articles, and that if it is, non-extended confirmed users can use edit requests to propose changes (because of course they can). But it doesn't say anything about their contributions to consensus discussions being limited to requesting changes, nor does it imply anything remotely similar. As far as I know, there is no community consensus limiting contributions of non-ec editors to discussions on talk pages for articles under any type of page protection, CTOP or no. I think you might both be labouring under a misconception here, but I suppose it's possible I've missed some sort of recent development somewhere. If so, can you point me to where this consensus is codified? SnowRise let's rap 08:39, 23 November 2023 (UTC)
- Snow Rise, Wikipedia:Arbitration Committee/Noticeboard#Arbitration motion regarding the extended confirmed restriction and WP:ECR explain this.
Non-extended-confirmed editors may use the "Talk:" namespace only to make edit requests related to articles within the topic area, provided they are not disruptive.
- The original text was amended a couple weeks ago to make it explicit. ScottishFinnishRadish (talk) 09:34, 23 November 2023 (UTC)
- Thanks for that, ScottishFinnishRadish; I appreciate your cluing me in to where this change occurred. I have to say (and hopefully Nableezy will forgive my getting on the soapbox on their talk page), but I have serious misgivings about ArbCom promulgating that particular rule by themselves. Less because of the result (I suppose there are arguments either way) and more because they chose to abrogate such a core and founding community priority so broadly on their own onus, with the input of just a few members of the community. I'm beginning to wonder if any permutation of ArbCom these days sees any practical limits to their prerogative to legislate policy unilaterally. Something like this really should only have been done with major consultation of the community: from the looks of it, there was no parallel discussion at WP:VP or even a listing on WP:CD? SnowRise let's rap 16:50, 23 November 2023 (UTC)
- There was discussion at WP:ARCA to clarify the original decision. ScottishFinnishRadish (talk) 16:52, 23 November 2023 (UTC)
- Yeah, I see that, but in my opinion the involvement of less than a dozen editors is insufficient consultation of the community for a change so broad and impactful. This really should have been floated before the community in a more visible way, either by way of a satellite discussion or at least a CD posting. SnowRise let's rap 18:29, 23 November 2023 (UTC)
- I didnt really support the further restricting of non-ec editors as there were some that definitely were constructive, but it was getting drowned out. Despite the usual take from the media on a "few bad apples", the phrase actually ends with "spoils the bunch" (at least thats how I was taught it as a kid in the late 1900s). nableezy - 17:00, 23 November 2023 (UTC)
- Yeah, I'm of two minds on the underlying matter. On the one hand, I definitely feel that there's a risk of baby out with the bathwater here, to use another old idiom. Content editing restrictions are one thing, but restricting even consensus discussion, and specifically on contentious topics, to only established editors feels like a bridge too far to me. There's more than a whiff of "we, the regulars, should have exclusive input" elitism in this, as well as an element of WP:CREEP towards the goal of a vocal minority on the project to eventually restrict all editing to registered users. On the other hand, I also understand the perspective that the corps of veteran editors is spread increasingly thin across acrimonious areas, fighting disruption from SPAs and other bad actors. I imagine a true community discussion on this matter would have brought a variety of perspectives and that it might have been a very close run thing, however the community came down.
- There was discussion at WP:ARCA to clarify the original decision. ScottishFinnishRadish (talk) 16:52, 23 November 2023 (UTC)
- Thanks for that, ScottishFinnishRadish; I appreciate your cluing me in to where this change occurred. I have to say (and hopefully Nableezy will forgive my getting on the soapbox on their talk page), but I have serious misgivings about ArbCom promulgating that particular rule by themselves. Less because of the result (I suppose there are arguments either way) and more because they chose to abrogate such a core and founding community priority so broadly on their own onus, with the input of just a few members of the community. I'm beginning to wonder if any permutation of ArbCom these days sees any practical limits to their prerogative to legislate policy unilaterally. Something like this really should only have been done with major consultation of the community: from the looks of it, there was no parallel discussion at WP:VP or even a listing on WP:CD? SnowRise let's rap 16:50, 23 November 2023 (UTC)
- Snow Rise, Wikipedia:Arbitration Committee/Noticeboard#Arbitration motion regarding the extended confirmed restriction and WP:ECR explain this.
- But it's the fact that this discussion was so insular and the change promoted in such a cavalier fashion without respect for how this impacts longstanding community principles that really worries me--much more so than any outcome on the motion, frankly. I feel like ArbCom is hitting a critical mass in presumption of authority the last couple of years, and something's gotta give. Or perhaps it's better said that I think it would better serve the overall health of the community if something does give.
- Mind you, I've traditionally been a supporter of a broad remit for that body, but I think we're hitting a tipping point of needing to claw back their power to promote broad changes to the project without consultation and approval of the community, in light of some power-grabby decisions in recent years--or more specifically, the laissez-faire approach to what is essentially unilateral policy making. The Committee was never meant to have this kind of power to shape such project-defining rules under their own initiative, as I see it. I think many more presumptive acts like this and a big, big conversation is coming. SnowRise let's rap 18:29, 23 November 2023 (UTC)
- Well things like RFCs and move requests were already restricted. The mood isn’t restricting it to the regulars, it’s more a. You need to have some basic understanding of our policies to meaningfully participate and most the influx of new editors did not have that, and b. There’s still a shit ton of socking and canvassing going on. nableezy - 19:46, 23 November 2023 (UTC)
- That's the point I was going to make. There are a tremendous amount of socks being blocked, and a lot of the other editing was still disruptive. When you're dealing with what might be the most fraught topic on Wikipedia dealing with extra bullshit has a lot of drawbacks, from opportunity cost to higher likelihood of snapping at a good faith editor because you're reaching your wit's end.
- Sometimes you have to go with the least bad option. ScottishFinnishRadish (talk) 19:59, 23 November 2023 (UTC)
- Yeah, I'm very sympathetic to that view. Now mind you, if this had been put more properly before the community rather than having been implemented through Arbitrator fiat, I think I may have just narrowly come down on the other side of the cost-benefit analysis. Afterall, we already have substantial procedural and technical tools for dealing with these sorts of disruption, and closers are already entitled to discount IP/new user perspectives where appropriate (as when a large number of IPs show up with suspiciously uniform views). I honestly don't know that we get all that much that improves the situation from this model, relative to the pretty steep price of removing all productive non-EC perspectives.
- But at the end of the day it's a close issue for me, I can endorse elements of both perspectives, and both seem basically like reasonable outlooks. Again, the fundamental issue I have here is not the result, but how this decision was arrived at. This is the first time in the history of the project that all non-EC editors have been de facto banned from even participating in the dialogue around particular (and frankly, massively broad) encyclopedic topics. The first such rule that automatically lumps all constructive editors in this category in together as persona non grata for these topics, by default, rather than just those who have demonstrated disruption. That is a major, major threshold and cultural change away from a core project commitment that still enjoys broad community support.
- Well things like RFCs and move requests were already restricted. The mood isn’t restricting it to the regulars, it’s more a. You need to have some basic understanding of our policies to meaningfully participate and most the influx of new editors did not have that, and b. There’s still a shit ton of socking and canvassing going on. nableezy - 19:46, 23 November 2023 (UTC)
- Mind you, I've traditionally been a supporter of a broad remit for that body, but I think we're hitting a tipping point of needing to claw back their power to promote broad changes to the project without consultation and approval of the community, in light of some power-grabby decisions in recent years--or more specifically, the laissez-faire approach to what is essentially unilateral policy making. The Committee was never meant to have this kind of power to shape such project-defining rules under their own initiative, as I see it. I think many more presumptive acts like this and a big, big conversation is coming. SnowRise let's rap 18:29, 23 November 2023 (UTC)
- I just do not think a matter like that is best decided by just twelve editors, nor do I feel it is within ArbCom's purview to make such a decision unilaterally. Whatever the right outcome is here, the resolution of that question and a change this drastic should have been put before the community. If because of the scale of the implications and kniock-on effects if nothing else. So this is a worrisome precedent to me. SnowRise let's rap 01:04, 24 November 2023 (UTC)
- I personally think there are better hills to die on; we as a community have already basically accepted that the Israeli-Palestinian conflict topic area cannot be effectively administered with our normal procedures, and we have already ceded to ArbCom basically limitless authority to manage that topic area so that the administrators we do have that are willing to step in to keep things somewhat in line with our behavioral policies are not overwhelmed with so much low-level crap that they are unable to deal with the more complicated problems. I understand the frustration, at the time they were discussing this at ARCA there was one user with like 300 edits who I saw being completely constructive and I wanted them to be able to continue being so (and this was a user that I feel comfortable placing firmly on the "pro-Israel" side of the spectrum). But there is still so. much. bullshit that happens in these articles everyday. I have literally zero doubt that on basically every RFC, move request, or AFD that what we now know to be AndresHerutJaim, as יניב הורון (Yaniv) was just a sock of his, is mass emailing at least a dozen accounts to get them to vote. I have zero doubt that he is doing the same for various editing disputes across a range of pages. 30/500 isnt an insurmountable barrier, otherwise we wouldnt still be getting NoCal100 and Icewhiz socks regularly, but it does at least quiet some of the noise down. As far as to the pretty steep price of removing all productive non-EC perspectives, I really think that is overestimating that price. Most of the commentary is not all that productive. Yes, some of it is, and the rules still allow for edit requests for anybody that wants to make a constructive comment. But most of it is bare voting and forumming. nableezy - 18:43, 24 November 2023 (UTC)
- I just do not think a matter like that is best decided by just twelve editors, nor do I feel it is within ArbCom's purview to make such a decision unilaterally. Whatever the right outcome is here, the resolution of that question and a change this drastic should have been put before the community. If because of the scale of the implications and kniock-on effects if nothing else. So this is a worrisome precedent to me. SnowRise let's rap 01:04, 24 November 2023 (UTC)
GA nom of the Israeli occupation of the West Bank article
G'day Nableezy, I hope you are well. Just had a quick look at the subject article wondering about assessing it, and beyond the few currently uncited passages, I cannot see this article getting to a stable enough state for a successful GAN while the current levels of fighting and activity in the West Bank is ongoing (and it will be needing updating as it progresses), and I think at over 18,000 words it is too long and would benefit from splitting. There are also a few single sentence paragraphs. Some widget I have installed is telling me the Abdullah, Daud source is generally unreliable, and there appear to be dozens of sources in the Sources section that are not used for citations in the article itself (for example, Algazy, Bishara, Mearsheimer, Slater and Halper, and many more). The latter gives the impression there are more sources used in the article than there are. I have a great deal of respect for the work that yourself and others have done on what is an important article, but just don't think it is going to be able to be positively assessed against the GA criteria until things settle down a bit over there and it is updated and the points mentioned here are addressed. Just my two cents, take it or leave it. Cheers, Peacemaker67 (click to talk to me) 06:46, 22 November 2023 (UTC)
- A bunch of material has been condensed over time, so some of the sources that were in the article aren't used. I'll go through and prune that section, or re-add them as sources. I can replace the MEMO cite, no worries. I dont think the article itself is really getting that much editing so as not to be stable, but if you want to table the review thats fine with me. Obviously Ive had other priorities for my editing time as well. Thank you for the feedback, Ill try to get to it as soon as I can. nableezy - 16:58, 23 November 2023 (UTC)