• chevron_right

      Lawsuit: Comcast Must Terminate Pirates & Block Top Torrent Sites

      news.movim.eu / TorrentFreak · Friday, 16 September, 2022 - 17:48 · 4 minutes

    throttle In 2019, a Virginia jury ordered Internet provider Cox Communications to pay a billion dollars in damages to record labels including Capitol Records, Warner Bros, and Sony Music.

    The plaintiffs alleged that by failing to terminate subscribers that had been accused of copyright infringement multiple times, Cox failed to meet its obligations under the DMCA.

    The decision is being appealed but in the meantime other ISPs face similar allegations, including AT&T and Verizon , who were sued earlier this month.

    Both of these lawsuits were filed by Voltage Pictures and several movie industry affiliates, together behind movies such as “After We Collided,” “Dallas Buyers Club,” “Room 203,” and “The Bird Catcher”. This week, the same companies filed yet another lawsuit, this time targeting the largest broadband company in the United States.

    Lawsuit Accuses Comcast of Copyright Infringement

    In general terms, the new lawsuit filed against Comcast is almost a direct copy of those filed against Verizon and AT&T. It alleges that the ISP can easily take action to prevent piracy carried out by its customers using BitTorrent networks. All it has to do is terminate their subscriptions.

    “Comcast can stop providing internet services to a customer at any time. It can stop providing internet services to customer accounts that repeatedly use its services for piracy. And Comcast doesn’t have to find these repeat offenders itself — copyright holders like Voltage already do that for Comcast, by sending copyright infringement notices. But Comcast does not take this simple step,” the lawsuit alleges.

    The filmmakers say that Comcast doesn’t terminate repeat infringers because their business is lucrative. Each customer account returns between $400 and $1,000 in additional profits and when combined, these accounts add tens of millions of dollars to Comcast’s bottom line.

    More Than 250,000 DMCA Notices Sent to Comcast

    The plaintiffs say that third parties (Comcast subscribers) are responsible for downloading torrents from sites including RARBG, 1337x, The Pirate Bay, YTS, and the less-well-known Russia-focused torrent site seleZen.

    By joining torrent swarms and sharing their movies, the plaintiffs say that Comcast subscribers reproduced, distributed, publicly displayed, and publicly performed copyright works without permission from the rightsholders.

    The plaintiffs say that evidence of this infringement was captured by Maverickeye, a company well known for its involvement in ‘copyright-trolling’ cases against single BitTorrent users. Over the past three years, the German-based company logged hundreds of thousands of infringements carried out by Comcast users, the plaintiffs say.

    The movie companies say they notified Comcast of these infringements in more than 250,000 DMCA notices.

    Failure to Terminate Repeat Infringers

    Despite receiving more than a quarter of a million copyright notices, Comcast failed to take action against its allegedly infringing customers, the lawsuit claims.

    “Comcast failed to terminate the accounts associated with these IP addresses or otherwise take any meaningful action in response to these Notices. Comcast often failed to even forward the Notices to its internet service customers or otherwise inform them about the Notice or its content,” the plaintiffs say.

    “Instead, Comcast continued to provide the internet access and services necessary for users to commit further online piracy. Comcast continued to provide access to the internet from the IP addresses that infringers used to pirate movies.”

    The complaint highlights several instances of particularly egregious conduct. One particular IP address was reported 782 times for infringement, another 626 times. Two IP addresses had 609 and 532 copyright infringements logged against their respective accounts, with several others having a minimum of 373 complaints filed against theirs.

    Comcast does have a published repeat infringer policy but the lawsuit claims that the company’s failure to terminate repeat infringers means that it no longer enjoys safe harbor from liability under the DMCA.

    “Comcast only counted the DMCA notifications regarding a customer account in each month, rather than counting total DMCA notifications. Under this policy, Comcast did not terminate an account that had a very high number of infringements over several months, but not in any one month,” the lawsuit notes.

    Several Types of Copyright Infringement

    Due to the alleged inaction of Comcast, the plaintiffs claim that the defendants are liable for contributory and vicarious copyright infringement. These claims alone could run to many millions of dollars in damages.

    Due to the plaintiffs’ Copyright Management Information (CMI) being removed or altered in movie files distributed via BitTorrent by Comcast customers, the ISP is also liable for contributory and vicarious violations under the §1202(a)(b) of the DMCA, the complaint adds.

    The plaintiffs demand actual or statutory damages and an order that compels Comcast to implement a repeat infringer policy that terminates the accounts of repeat infringers.

    In common with the plaintiffs’ lawsuits against AT&T and Verizon, the complaint demands an order that compels Comcast to block access to pirate sites listed in the USTR’s Notorious Foreign Markets report. These include YTS, The Pirate Bay, RARBG, and 1337x.

    The filmmakers’ complaint filed against Comcast at the District Court of the Eastern District of Pennsylvania is available here (pdf)

    From: TF , for the latest news on copyright battles, piracy and more.

    • chevron_right

      Verizon Must Disconnect Pirates & Block Pirate Sites, New Lawsuit Demands

      news.movim.eu / TorrentFreak · Wednesday, 7 September, 2022 - 10:19 · 3 minutes

    verizon logo Efforts to hold internet service providers in the United States accountable for the piracy activities of their subscribers are gaining momentum.

    In 2019, Cox Communications was ordered to pay a billion dollars in damages to record labels. The decision is being appealed by Cox, but it set the stage for similar lawsuits, including a new complaint reported just yesterday targeting AT&T .

    Filed in Texas by filmmaker Voltage Pictures and several affiliates, together behind movies such as “After We Collided,” “Dallas Buyers Club,” “Room 203,” and “The Bird Catcher”, the lawsuit lambasts AT&T for not doing enough to prevent subscribers from engaging in movie piracy.

    A new and broadly similar complaint filed against Verizon Communications and Cellco Partnership follows a similar template.

    Verizon Hit With Copyright Complaint

    The premise of the lawsuit is that Verizon “can easily take action against online piracy” by disconnecting customers who repeatedly use its services to download and share movies. The company doesn’t even have to find these pirates itself because the plaintiffs have provided infringement notices carrying all of the information it needs.

    The reason that Verizon hasn’t taken action, the complaint notes, is because Verizon makes between $400 and $1,000 in additional profits per ‘pirate’ account. But this isn’t permissible under law, the plaintiffs claim, because when Verizon receives knowledge of repeat infringement yet fails to disconnect the associated accounts, it can be held liable for customers’ piracy.

    Hundreds of Thousands of Infringements

    According to the plaintiffs, IP addresses allocated to Verizon/Cellco Partnership were monitored by anti-piracy tracking outfit Maverickeye downloading and sharing pirate copies of their movies. Over the past three years, “hundreds of thousands” of these infringements were logged and over 90,000 corresponding infringement notices were sent to the ISP.

    On this basis, the plaintiffs believe that Verizon/Cellco were willfully blind to these infringements because neither took meaningful action to prevent ongoing infringement by their customers. In some cases, infringement notices weren’t even forwarded to the allegedly-infringing subscribers, the plaintiffs add.

    The complaint highlights several specific IP addresses allocated to Verizon customers, for which the plaintiffs sent large volumes of copyright infringement complaints. One IP address was listed in infringement notices 800 times, another appeared 700 times, with three others being identified on 600, 500 and 400 occasions.

    In these cases and others like them, it’s alleged that Verizon had the opportunity to suspend customer accounts but failed to do so.

    Repeat Infringers and the DMCA

    When Congress passed the DMCA in 1998 (not 1988, as this lawsuit alleges), service providers were given ‘safe harbor’ protections if they adopted and reasonably implemented policies for terminating repeat infringers “in appropriate circumstances.”

    Verizon publishes its policy here but according to the complaint, the implementation of the Verizon policy places an unfair burden on rightsholders.

    The plaintiffs say that BitTorrent-style infringements must be reported via ‘Conduit Notice Forms’ but Verizon prohibits these from being filled out using automated processes. Verizon does operate the “Verizon Anti-Piracy Cooperation” program but the plaintiffs say the contract contains “onerous” terms.

    These include an agreement not to sue Verizon for copyright infringement alongside processing fees of $75 per hour for IP address lookups.

    In any event, the lawsuit claims that Verizon failed to terminate customer accounts, even when it received multiple complaints against specific accounts. As a result, it has lost its safe harbor protections under the DMCA.

    Several Types of Copyright Infringement

    Due to the alleged inaction of Verizon/Cellco Partnership, the plaintiffs claim that the defendants are liable for contributory and vicarious copyright infringement. These claims alone could run to many millions of dollars in damages.

    Due to the plaintiffs’ Copyright Management Information (CMI) being removed or altered in movie files distributed via BitTorrent by Verizon customers, the ISP is also liable for contributory and vicarious violations under 17 U.S.C.S. §1202(a)(b) , the complaint adds.

    The plaintiffs demand actual or statutory damages and an order that compels Verizon to implement a repeat infringer policy that terminates the accounts of repeat infringers.

    In common with the lawsuit the plaintiffs just filed against AT&T, the complaint demands an order that compels Verizon to block access to pirate sites listed in the USTR’s Notorious Foreign Markets report. These include YTS, The Pirate Bay, RARBG, and 1337x.

    A copy of the complaint, filed by Voltage Holdings et al. at the District Court of the Southern District of New York, can be found here (pdf)

    From: TF , for the latest news on copyright battles, piracy and more.

    • chevron_right

      One America News loses Verizon TV deal, begs for access to Comcast or Charter

      news.movim.eu / ArsTechnica · Friday, 22 July, 2022 - 16:41 · 1 minute

    One America News Network promotional item featuring a picture of four newscasters; text that says,

    Enlarge / Screenshot from One America News Network's press kit. (credit: One America News Network)

    One America News Network is about to lose its last major TV distributor. After being removed from DirecTV in early April, the right-wing network was still aired on Verizon Fios. But with a channel-carriage contract expiring at the end of July, Verizon confirmed that the sides won't reach a deal.

    "Our negotiation with OAN has been a typical, business-as-usual carriage negotiation like those that routinely happen between content distributors and content providers. These negotiations were focused on economics, as they always are, but OAN failed to agree to fair terms," Verizon said in a statement provided to Ars last night. "Since we were unable to reach an agreement, effective July 31, 2022, we will no longer have the rights to provide our customers with this programming, and it will be removed from the Fios TV lineup."

    Verizon also confirmed the July 31 removal in an update posted to its website , which notes that "sometimes broadcasters and cable networks demand unacceptable price increases" that can increase customers' monthly TV bills. We contacted OAN about its removal from Verizon last night and will update this article if we get a response.

    Read 14 remaining paragraphs | Comments

    • Sp chevron_right

      BIMI: ISP Support as of January 2022

      pubsub.slavino.sk / spam_resource · Monday, 17 January, 2022 - 13:00 · 4 minutes

    It

    It's time for your periodic BIMI adoption status update.

    A quick overview of what this is all about: BIMI is a standard being adopted by multiple internet services providers (ISPs) to allow the display of a sender's logo along side email messages, when displayed on a mobile device or in a webmail client. Some ISPs and mail clients have had a sender logo display function for a while now (one example is Gravatar ), but BIMI is an attempt to standardize and regulate this mechanism across the email ecosystem.

    Adoption by senders seems a bit slow; but the spec only went public in 2019, which isn't that long ago. Also, it suffers a bit from the "chicken and egg" problem -- it's hard to convince senders to adopt the standard if receivers haven't adopted support for the standard. But now with two of the top three B2C mailbox providers (Yahoo and Gmail) having BIMI support, I'm guessing that we'll start to see more adoption of BIMI by senders.

    BIMI.jpeg

    Here's the current status of BIMI Support at large ISPs, email hosting and webmail providers:

    1. Gmail: Yes, supports BIMI! Requires VMC. ( Find more info here .)
    2. Yahoo (ex-Verizon): Yes, supports BIMI. Does not require VMC. ( More info here .)
    3. Fastmail : Yes, supports BIMI! ( More info here .)
    4. Considering BIMI Support: Comcast and Seznam.cz. ( More info here .)
    5. Microsoft: Has no support for BIMI.

    Gmail. In July 2020, Google announced their intent to support BIMI . In July 2021, Google announced that they were rolling out BIMI support over the coming weeks . Per the BIMI spec, Google requires that senders implement a Verified Mark Certificate (VMC), available from DigiCert or Entrust (and possibly others). It sounds like obtaining this VMC will require that a sender have trademarked their logo , which could be a significant barrier for smaller or hobbyist senders.

    Yahoo (AOL/Yahoo/Verizon). Has support for BIMI. For a logo to display, the following conditions must be met: A BIMI record exists which points to a valid logo in SVG format, a DMARC policy of quarantine or reject is in place, the mailing is sent to large number of recipients (bulk mail), and they see sufficient reputation and engagement for the email address. They have a dedicated support page for BIMI and also have a contact address for questions/issues ( click here and search for "BIMI" on the page).

    Microsoft Outlook.com (Hotmail). Microsoft has not announced any support for BIMI. A competing system called "brand cards" has likely been abandoned; multiple folks have told me that they have been unable to get enough information on how to implement a "brand card." There's no opportunity here at the present time, unfortunately. If that changes, I'll post an update.

    So what should you do now? Here's what I would recommend large marketing senders do:

    1. Make sure all email you send is authenticated with both SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) authentication. (All mail -- not just bulk or newsletter mail. Your ESP , corporate email platform (or both) should be able to help you do that.)
    2. Implement DMARC, perhaps working with a vendor like dmarcian , Agari , Valimail , ProofPoint or Red Sift . (Disclaimer: I work for Kickbox , and we've got DMARC monitoring in our deliverability tool suite as well. I am a happy user of it myself!) Partnering with a vendor to provide monitoring and reporting helps you know whether or not it is safe to move on to the next step -- ensuring that you're not going to accidentally tell ISPs to block your legitimate mail.
    3. Move to a restrictive "p=reject" DMARC policy after your DMARC reporting shows that you properly authenticate all of your mail streams. Don't do this just for the future logo opportunity -- do it because it makes it harder for bad guys to send fake mail pretending to be from your email domain name.
    4. Trademark your logo and obtain a Verified Mark Certificate. Wondering what this whole VMC thing is all about? Here's a primer . Ready to obtain a VMC? You could go directly to DigiCert or Entrust, or look for help from Mailkit via their NOTAMIQ service or Red Sift.
    5. Learn how to create the BIMI logo file. You can find more information here .
    6. Understand that things are still developing. More ISPs could announce support in the future, and how they, or existing ISPs, will enforce the spec could evolve. Stay knowledgable and be flexible and be able to evolve.
    Wondering who has implemented a BIMI logo? I've put together a little BIMI logo look up tool on KBXSCORE . Plus in your favorite domain name and see what it can find. Here's a couple of logos to get you started.

    And now...you are BIMI aware! Go forth and spread that logo.

    (Disclaimer; this is not a paid post as far as consideration or compensation changing hands, but I did mention my employer above, so I'm mentioning that again here to be as transparent as I possibly can.)

    Značky: #gmail, #microsoft, #bimi, #seznam, #comcast, #Network, #brandimage, #brandavatar, #verizon, #yahoo, #fastmail

    • Sp chevron_right

      Yahoo is Yahoo again!

      pubsub.slavino.sk / spam_resource · Wednesday, 8 September, 2021 - 12:00

    we-are-yahoo.png
    Yahoo is Yahoo again ! The entity that runs the servers hosting the mailboxes for AOL and Yahoo is now called Yahoo Inc, as of September 1st, 2021. No more Verizon Media.

    You can find their updated corporate website here , and you can see that the sale of Yahoo by Verizon Media to funds managed by Apollo Global Management was completed on September 1st.

    So far, Yahoo's Postmaster blog has switched to the yahooinc domain, but the Postmaster site URL and Developer Network site URL remain unchanged. One assumes all will transition at some point soon.

    Who hosts mail for verizon.net? Yahoo. We'll see if that changes at some point in the future, but for now, they still host mail for the same consumer mailbox domains today as compared to yesterday and best practice guidance for senders remains the same .

    *** Whoops: My updating the list of past domains post to say "Yahoo" instead of "Verizon" resulted in Blogger flagging that post for spam, for some silly reason, so I've got no link to that at the moment. Thanks, Blogger. Check the website later -- I'll get the domain list reposted very soon.


    Značky: #yahoo, #verizon, #isps, #news, #Network

    • Sp chevron_right

      BIMI: ISP Support as of August 2021

      pubsub.slavino.sk / spam_resource · Friday, 20 August, 2021 - 12:00 · 3 minutes

    BIMI.jpeg

    It's been a while since I've posted a BIMI status update, and things are changing! Things are standardizing! Things are getting good. So, let's get right to it...

    BIMI, if you do not remember, is a new standard being adopted by multiple internet services providers (ISPs) to allow the display of a sender's logo along side email messages, when displayed on a mobile device or in a webmail client. Some ISPs and mail clients have had a sender logo display function for a while now (one example is Gravatar ), but BIMI attempts to standardize and regulate this process across the email ecosystem.

    Here's the current status of BIMI Support at large ISPs, email hosting and webmail providers:

    1. Verizon: Yes, supports BIMI.
    2. Gmail: Yes, supports BIMI! Requires VMC. Find more info here .
    3. Fastmail : Noted as having support ( here ) but I have no more details at this time.
    4. Considering BIMI Support: Comcast and Seznam.cz. ( More info here .)
    5. Microsoft: No support announced.

    Verizon Media (AOL/Yahoo/Verizon). Has support for BIMI. For a logo to display, the following conditions must be met: A BIMI record exists which points to a valid logo in SVG format, a DMARC policy of quarantine or reject is in place, the mailing is sent to large number of recipients (bulk mail), and they see sufficient reputation and engagement for the email address. They also have a contact address for questions/issues ( click here and search for "BIMI" on the page).

    Gmail. In July 2020, Google announced their intent to support BIMI . In July 2021, Google announced that they were rolling out BIMI support over the coming weeks . Per the BIMI spec, Google requires that senders implement a Verified Mark Certificate (VMC), available from DigiCert or Entrust (and possibly others). It sounds like obtaining this VMC will require that a sender have trademarked their logo , which could be a significant barrier for smaller or hobbyist senders.

    Microsoft Outlook.com (Hotmail). Microsoft has not announced any support for BIMI. A competing system called "brand cards" has possibly been abandoned; multiple folks have told me that they have been unable to get enough information on how to implement a "brand card." There's no opportunity here at the present time, unfortunately.

    So what should you do now? Here's what I would recommend large marketing senders do:

    1. Make sure all email you send is authenticated with both SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) authentication. (All mail -- not just bulk or newsletter mail. Your ESP , corporate email platform (or both) should be able to help you do that.)
    2. Implement DMARC, perhaps working with a vendor like Agari , Valimail , ProofPoint or Red Sift . A DMARC-savvy email security vendor can help you properly configure email authentication, configure DMARC failure monitoring, show you how to read DMARC failure reporting, and give you confidence that you're not going to break anything if you implement a restrictive DMARC policy.
    3. Move to a restrictive "p=reject" DMARC policy after your DMARC reporting shows that you properly authenticate all of your mail streams. Don't do this just for the future logo opportunity -- do it because it makes it harder for bad guys to send fake mail pretending to be from your email domain name.
    4. Trademark your logo and obtain a Verified Mark Certificate. You could go directly to DigiCert or Entrust, or look for help from Mailkit via their NOTAMIQ service or Red Sift.
    5. Understand that things are still developing. More ISPs could announce support in the future, and how they, or existing ISPs, will enforce the spec could evolve. Stay knowledgable and be flexible and able to evolve.
    And now you know as much (or maybe more) about BIMI than I do. Good luck!

    Značky: #yahoo, #seznam, #bimi, #fastmail, #verizon, #comcast, #Network, #microsoft, #gmail