What I am seeing here, if I choose to think on their terms, is a small
collection of males asserting dominance by lifting their legs and demanding we
accept their peeing on a working product. If It Is Not Broke Don't Fix It. This
is the experience of a 76 year life span giving you advice. I've seen managers
pee on projects this way and destroy companies. I hated it then. I hate it now.
And you are triggering me horridly.
{+,+} I stick my tongue out in your general direction.
On 20200710 12:29:42, @lbutlr wrote:
On 10 Jul 2020, at 01:38, Olivier <olivier.nic...@cs.ait.ac.th> wrote:
Axb <axb.li...@gmail.com> writes:
the US problems won't be fixed with renaming B&W lists.
Seriously.. you have more important issues...
While thet change in names will not fix any societal issue, for a
product like SpamAssassin that relies heavily on plugins (including some
plugins that may have been developped locally, long time ago, by someone
who is not working there anymore) and that is
also embeded (like in amavis) these sort of changes may break a lot of
implementations, to the point that people will be reluctant to upgrade.
If people are so fragile that they have to hold on to terms that are extremely
offensive to some of their peers, they will get more spam. Oh noes.
And if SA is not upgraded, the user base will shrink and it may lead to
the death of SA.
If it cannot function without being offensive to many people, then so be it.
Allow/deny I think are better than welcome/block, but I don't care.
Allow/block might be better too.
