Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122496
Content-Type: multipart/alternative;
 boundary="------------tyPpKdEShFd6207ynFcYAsjG"
Message-ID: <fc91a239-43db-4d08-9695-6d90f334d838@daniil.it>
Date: Mon, 26 Feb 2024 12:53:25 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] is this thing on?
To: internals@lists.php.net
References: <112488a9-aaa6-4d85-9056-a4581a3cda21@app.fastmail.com>
 <17d50791-190d-4f74-9478-030a84ae9545@app.fastmail.com>
Content-Language: en-US
In-Reply-To: <17d50791-190d-4f74-9478-030a84ae9545@app.fastmail.com>
From: daniil@daniil.it (Daniil Gentili)

This is a multi-part message in MIME format.
--------------tyPpKdEShFd6207ynFcYAsjG
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

> This has also come up in the past regarding moving from e-mail to $currently_fashionable_technology - having some barrier to entry is actually quite useful, since we want people to put some effort into their contributions beyond "me too" or "I had this crazy idea in the pub".

IMO sending an email is not a gigantic barrier to entry, as can be seen 
by the often low (technical and overall) quality of the replies to many 
of the threads on this list.

Personally, I do not think that gatekeeping (!) and spam-prevention are 
a good reason to keep using a broken and outdated system like mailing 
lists in 2024.

Large projects like PHP will still inevitably attract attention, 
regardless of whether github or mailing lists are used; I personally 
dislike mailing lists not because they are difficult to use, but because 
they are simply broken: every time I had to deal with any mailing list, 
including this one, I had both incoming and outgoing deliverability 
issues related either to DKIM/DMARC, or some other issue caused by 
modern anti-spam measures that mailing lists do not account for.

I really don't think that a modern discussion system can afford to 
randomly loose messages: mailing lists should not be used in 2024.

Regards,

Daniil Gentili.


--------------tyPpKdEShFd6207ynFcYAsjG
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <span style="white-space: pre-wrap">
</span><span style="white-space: pre-wrap">
</span>
    <blockquote type="cite"
      cite="mid:17d50791-190d-4f74-9478-030a84ae9545@app.fastmail.com">
      <pre class="moz-quote-pre" wrap="">This has also come up in the past regarding moving from e-mail to $currently_fashionable_technology - having some barrier to entry is actually quite useful, since we want people to put some effort into their contributions beyond "me too" or "I had this crazy idea in the pub".
</pre>
    </blockquote>
    <p>IMO sending an email is not a gigantic barrier to entry, as can
      be seen by the often low (technical and overall) quality of the
      replies to many of the threads on this list.</p>
    <p>Personally, I do not think that gatekeeping (!) and
      spam-prevention are a good reason to keep using a broken and
      outdated system like mailing lists in 2024.</p>
    <p>Large projects like PHP will still inevitably attract attention,
      regardless of whether github or mailing lists are used; I
      personally dislike mailing lists not because they are difficult to
      use, but because they are simply broken: every time I had to deal
      with any mailing list, including this one, I had both incoming and
      outgoing deliverability issues related either to DKIM/DMARC, or
      some other issue caused by modern anti-spam measures that mailing
      lists do not account for.</p>
    <p>I really don't think that a modern discussion system can afford
      to randomly loose messages: mailing lists should not be used in
      2024.<br>
    </p>
    <p>Regards, <br>
    </p>
    <p>Daniil Gentili.<br>
    </p>
    <p><br>
    </p>
  </body>
</html>

--------------tyPpKdEShFd6207ynFcYAsjG--