From: Dave Taht <dave.taht@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>,
"Dave Taht via Starlink" <starlink@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: [NNagain] lists.bufferbloat.net is back up
Date: Thu, 5 Oct 2023 12:14:36 -0700 [thread overview]
Message-ID: <CAA93jw6Guss+CNNwgqvRTKYMVfHSqHW+SOLCabr=U7xPs4mhpA@mail.gmail.com> (raw)
The increase in traffic volume here triggered a spamcop alert (when I
did reach out to all my existing lists),
automatically triggered a complaint, a 3 day holding period that I
ignored since it was just the one report, which then shutdown the
server we were on, until I managed to express fully to a human to fix
it an hour ago.
Honestly... this seems a quite reasonable approach - and probably not
rapid enough in an era where a million vms can be spun up and down in
seconds.
I would like to thank those humans at linode that overrode the automation!
And also, if there is anyone more up to date on modern email standards
today (such as dmarc), and knows how to deploy, please get back to me
privately. I treasure email for multiple reasons (and things like
netiquette) - my counter example of not wanting a forum would the
short life and death of google+. Everyone retains their own copies of
all that was said, it used to be easily indexed, and various other
things left unsolved by modern tech of the moment. It can be better by
using better email clients, and rigorous netiquette... and responses
are not limited to 1k or less in size, although many might prefer our
discussions be shorter, not longer.
And for all that, I miss usenet.
--
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos
reply other threads:[~2023-10-05 19:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw6Guss+CNNwgqvRTKYMVfHSqHW+SOLCabr=U7xPs4mhpA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=nnagain@lists.bufferbloat.net \
--cc=starlink@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