From: Hal Murray <halmurray+bufferbloat@sonic.net>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: [NNagain] Spam filtering
Date: Fri, 27 Oct 2023 14:48:40 -0700 [thread overview]
Message-ID: <20231027214840.7A4FA28C20C@107-137-68-211.lightspeed.sntcca.sbcglobal.net> (raw)
In-Reply-To: Message from Dave Taht via Nnagain <nnagain@lists.bufferbloat.net> of "Fri, 27 Oct 2023 12:37:44 -0700." <CAA93jw6bxermeacQ9MDKSjoe=YzvHa-z+FEZ9Yoh5GUSoKCX4Q@mail.gmail.com>
[Was Amtrack]
> 2) I could get mad that I figure 80% of this new email list is vanishing into
> spam boxes.
> What of the 10s of thousands of other emails that have come over the years
> not just from lists.bufferbloat.net but from people trying honestly to
> communicate?
There is/was a good discussion of all the good things that network geeks have
done.
How about discussing the things they haven't done?
Spam would be pretty high on my list. It's tangled up with (in)security -- a
lot comes from infected systems or phished accounts.
The current approach to spam is cost shifting. If you don't pay for your
abuse desk, the crap that you send or phishing sites you host..., means that
the rest of the net has to spend more on defense.
Anybody remember Spamford Wallace? He was going to setup a spam friendly ISP.
Nobody would connect to him. I wonder what would happen if a few ISPs that
host a lot of abuse had more troubles getting connected to the net. Would a
few well publicized examples be enough to spread the word?
High on my list would be dis/mis-information. The business model seems to be
to show customers things that will keep them online so you can show them more
ads. Gues what does that?
Is this also cost shifting? It's society as a whole that has to pay for the
disruption caused by bogus information.
--
These are my opinions. I hate spam.
next prev parent reply other threads:[~2023-10-27 21:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 19:37 [NNagain] An Amtrak trip through the real world yesterday Dave Taht
2023-10-27 19:58 ` Jack Haverty
2023-10-27 21:18 ` rjmcmahon
2023-10-27 21:48 ` Hal Murray [this message]
2023-10-27 23:23 ` [NNagain] Spam filtering Nathan Simington
2023-10-27 23:45 ` Dave Taht
2023-10-28 10:50 ` Frantisek Borsik
2025-04-06 1:21 ` Daniel Ezell
2025-04-06 10:23 ` Frantisek Borsik
2025-04-06 14:22 ` Tanya Weiman
2025-04-06 18:11 ` Frantisek Borsik
2023-10-28 16:55 ` rjmcmahon
2023-10-28 10:04 ` [NNagain] An Amtrak trip through the real world yesterday Frantisek Borsik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231027214840.7A4FA28C20C@107-137-68-211.lightspeed.sntcca.sbcglobal.net \
--to=halmurray+bufferbloat@sonic.net \
--cc=nnagain@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox