Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103692
MIME-Version: 1.0
References: <2df557da-eb32-4f46-944c-c0e957d03b04@gmail.com>
In-Reply-To: <2df557da-eb32-4f46-944c-c0e957d03b04@gmail.com>
Date: Mon, 7 Jan 2019 02:49:12 +0100
Message-ID: <CAJW__o1C9mQ=-P7yjZipbFLLmgN1YwdNqgi_Xgjw5i7DenQ4OA@mail.gmail.com>
To: Philippe Cloutier <chealer@gmail.com>
Cc: Internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Issue tracker - "Block user comments" abuse and alternatives
From: kalle@php.net (Kalle Sommer Nielsen)

Hi

Den man. 7. jan. 2019 kl. 01.38 skrev Philippe Cloutier <chealer@gmail.com>=
:
>
> Hi,
> I reported a bug on the issue tracker in https://bugs.php.net/bug.php?id=
=3D53255
> Hannes "bjori" Magnusson later marked the ticket as "Not a bug", insultin=
g myself (and apparently other contributors who had previously reported the=
 same issue) at the same time. Peter Kokot later confirmed the issue, which=
 is caused by an obvious concurrency bug, as can be seen in https://bugs.ph=
p.net/bug.php?id=3D66653
>
> In order to ensure this contempt is over, I meant to warn the responsible=
 by commenting in #53255. Unfortunately, that very same contributor went as=
 far as "blocking user comments" in this ticket, and the tracker considers =
me as a "user", so I cannot do that. Therefore:
> 1. Can someone with sufficient permissions unblock commenting in #53255?
> 2. While no security at all was needed  in this case, in general, soft se=
curity support minimizes the temptation to put in place "hard security". Do=
es the ITS allow hiding comments considered as useless, as Bugzilla allows,=
 instead of blocking?

I re-opened the issue. As a note, please keep issues like this to the
webmaster list as internals is purely language development.

Thank you!


--=20
regards,

Kalle Sommer Nielsen
kalle@php.net