From: "Douglas Goncz A.A.S. M.E.T. 1990" <DGoncz@replikon.net>
To: nnagain@lists.bufferbloat.net
Subject: Re: [NNagain] Scope of "Network Neutrality"? (Jack Haverty
Date: Thu, 14 Mar 2024 12:08:07 -0400 [thread overview]
Message-ID: <CAOnAEVYcJhSmuwqtxFvMc=Q7+cY3KhXYxBisNeuBso9Pj5CvZg@mail.gmail.com> (raw)
In-Reply-To: <mailman.7.1710432001.14886.nnagain@lists.bufferbloat.net>
[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]
Hi there Jack
I don't know if isps are in general allowed to refuse to send an email or
refuse to allow a user to receive an email but I know that if I mail an MP3
using Gmail the chances are that Google meaning alphabet will refuse to
transmit it based on
If I remember correctly
The digital millennium copyright act as currently amended
And in general
The principal that I shouldn't share a copy of a CD I own even track by
track with someone else
However
I am pretty sure and this is a separate issue
That if I use an editor
And I've never tried
To put two MP3s together to make my own creation
Analogous to a well recognized principle that making your own CD mix is
fine and you can share copies of that as long as it's not all the tracks
from one album or CD and it represents some kind of authorship where you
pick and choose music that meets your whatever needs or style or whatever
That probably would sell through but I don't have any hard data
I have had emails can that means canceled
Based solely on violation of digital millennium copyright act
And I note here there is no means for an appeal
So as far as net neutrality
An ISP who is not part of the backbone
Might be a good thing to have
An email from a secondary provider
Might be a good thing to have
Your mileage may vary
And that's just an opinion there about the backbone and the providers
[-- Attachment #2: Type: text/html, Size: 2493 bytes --]
parent reply other threads:[~2024-03-14 16:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.7.1710432001.14886.nnagain@lists.bufferbloat.net>]
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='CAOnAEVYcJhSmuwqtxFvMc=Q7+cY3KhXYxBisNeuBso9Pj5CvZg@mail.gmail.com' \
--to=dgoncz@replikon.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