occam <nob...@nowhere.nix> wrote:
> VanguardLH wrote:
>
>> Going to alt.* hierarchy for Firefox support would be a welcome change.
>> Dictator Chris Illias who has ruined the Firefox newsgroup with his
>> personal "style" of moderation (which did not follow Mozilla's
>> guidelines on moderation duties, so Chris got rid of that web page soon
>> after I pointed out he wasn't following Moz's rules) will get deposed.
>
> I'm not sure what experiences you have had with Chris, but the couple of
> times I had my posts 'removed' by him, he provided his reasons for doing
> so. I did not hold it against him, as I saw his point.
>
> You have to admit that until now, <
news.mozilla.org> NGs have been less
> prone to spurious posts and asshole interjections than, ahem.... ACF.
Yep, and also prone to very helpful replies disappearing, too. Spend
hours researching a problem for someone, dig into Firefox, do online
research, and do a write up showing how to fix the problem (or why it
cannot be fixed) along with explanation of why it is that way in
Firefox. It doesn't show up according to Chris' bias that you never
explain the failings of anomalies of Firefox. Just provide the bare
help with no explanation. That's impossible for someone, like me, that
has been in hardware and software QA for decades.
Chris refused to consider volunteers as moderators. He wants full
moderation control. They are *his* newsgroups despite they are using
Mozilla resources. Chris is just one person, and he sleeps which means
submitted but yet non-approved articles can take half a day to show up.
If you are not auto-approved (i.e., in his whitelist), acceptance of a
submission awaits his attendance. I've seen mine get delayed by 14
hours, or more. Sometimes it's just an hour (never immediate because
I'm on Chris' shitlist of obstreperous posters), but it could be over a
day, or never, so all my work to provide an educated and researched
response was wasted. Respondents doing lots of work to help but getting
reamed by Chris decide to leave. They want to help, but Chris won't let
them.
If he allowed other moderators, some would be awake when he is asleep,
and there would be averaging of bias of just what content is considered
on-topic.
Chris has a his list of cronies, and their posts always show up
immediately, so Chris employs a whitelist. If he rejects an article, he
is supposed to post the article in an alternate newsgroup along with
edited it to show his explanation of why he rejected article, according
to Moz's rules which Chris managed to eradicate. Or he can post a
synopsis article in place of the original article into the original
newsgroup with his explanation for rejection. I've never seen him do
that, but I have seen him effuse his slant on his interpretation of what
is on-topic or off-topic.
If you help a user while explaining a deficiency in Firefox that causes
the problem, fat chance it shows up since you are not only showing a
resolution but why the user has to perform the workaround. Here's what
you do: that's accepted. Here's why you have to do that: not accepted
if in any way derogatory to the product (don't expose failings).
Explaining why the fix is needed is considered off-topic by Chris. Just
help, don't analyze why it's that way. No panning of Firefox is
allowed. He says you must post that content in the general newsgroup,
but then the explanation for the resolution is disconnected from the
help you provided to someone asking why something doesn't work. How is
a discussion of defects or behaviors of Firefox not germaine to a
newsgroup named Firefox? Oh no, you must bury that into the general
newsgroup where almost no one will see it, so you get dismal response,
if any, from a general community of all Moz products instead of a
community focused on the actual product. Who goes to the Firefox
newsgroup to ask for help or to give it, and also monitor the General
newsgroup on everything and anything Mozilla? Disappearance by
dissolution.
If Chris rejects a submission (himself or via his scripts/filters), you
simply not see your submission show up. Did it get submitted? Did it
bounce through the front-end NNTP server and manage to survive the
backend e-mail setup (the newsgroups are foremost a mailing list with an
NNTP gateway tacked on)? Or was there an error in the mailing list part
of the setup which won't get returned to the poster? The NNTP frontend
accepts the submission, the NNTP session is lost, the submission (if
accepted) goes to the mailing list system, but it can error there;
however, since the NNTP session no longer exists, there is no way to
report the error from the mailing list backend to the poster. The
scheme isn't Chris' fault, but he apparently never checks the error logs
to find where articles that were approved but didn't survive the mailing
list system. Chris says to e-mail him (
cont...@ilias.ca) if you want
to inquire why your post never showed up within a few minutes, few
hours, or over a day of waiting. Uh huh, take the discussion offline,
so other users don't see the evidence of his skewed filtering.
Yes, the lack of moderation means more noise in a newsgroup resulting in
you defining filters to get the view of a newsgroup how you want to see
it. Moderation is beneficial if the moderator is a benefactor. Chris
has proven he is not so beneficiary. You are judged by your actions,
not by who you claim you are, especially after obliterating Moz's rules
you are supposed to follow as a moderator. Moz's rules? Nope. Chris'
rules despite he's driving someone else's car.
Oh, by the way, you can see that I often am very verbose in my replies.
Chris has admitted that he refuses to read long posts. He skims. If a
post is longer than he is willing to read, he won't approve it. So, he
filters based on his slow reading speed or intolerance to long posts.
Long posts are highly likely to get rejected by Chris. However, short
posts are often incomplete regarding explanation, and going terse can
often mean being too vague and of no help. My ability to read and type
very fast results in upping the chance of rejection by Chris.