Earlier this month, several copyright holder groups sent their annual “notorious markets” submissions to the U.S. Trade Representative (USTR).

The U.S. Government uses this input for its annual review of notorious piracy markets, an overview of threats to various copyright industries.

The recommendations, including those from the RIAA, MPA, and ESA, traditionally include well-known piracy sites such as The Pirate Bay, but increasingly third-party technology providers are also being added to the mix.

For example, domain registrars and hosting services are regularly listed, and the same is true for advertising companies. Cloudflare has been frequently mentioned as well, although it’s not officially listed since the overview focuses on foreign entities.

The copyright holder groups who send these recommendations hope that the U.S. will include these companies in its final overview. That would put pressure on the sites and services as well at the countries from where they operate.

However, not everyone is pleased with this development. According to the Internet Infrastructure Coalition (I2Coalition), which counts Amazon, Cloudflare, Google, OVH, Steadfast and Tucows among its members, third-party intermediaries don’t belong in this list.

“Notorious markets should not be confused with neutral intermediaries such as Internet Infrastructure providers,” the I2Coalition writes in a letter to the USTR.

The coalition notes that some submissions, including those from the International Intellectual Property Alliance, have gone too far by suggesting copyright protection measures that would harm Internet infrastructure and therefore the Internet as a whole.

The group notes that Internet infrastructure providers, such as DNS providers, route users of the web to the right online locations. These services simply refer requests and don’t control the information at the locations where people are directed.

“The nature of these kinds of businesses is that they have limited access to content information. There are intermediaries between various segments of the Internet as a whole. They are not markets. Yet, these kinds of companies may be erroneously listed in the USTR notorious markets report,” the I2Coalition writes.

The Internet companies add that recent updates to the law have highlighted new enforcement options. However, it is not clear what must be enforced. This can become problematic when various stakeholders have different views on what the term ‘notorious market’ means.

“It is in this lack of clarity where many who submit to the notorious markets either by mistake or intentionally mischaracterize the concept of notorious markets for the purposes of identifying intellectual property infringement.”

The coalition calls on the USTR to deliver clarity as some of the current submissions vilify specific technologies, it says. Instead, the process should be limited to the ‘notorious’ sites and marketplaces themselves, not third-party intermediaries.

“We believe that the spirit and letter of the relevant IP laws are better upheld by going after true notorious markets, not throwing the baby out with the bathwater by going after Internet infrastructure providers,” the I2Coalition stresses.

The letter doesn’t mention specific companies or services the coalition believes were mistakenly called out. However, the coalition makes it clear that an effort to clear up what a ‘notorious market’ is should include a variety of stakeholders, not only those who represent the copyright industry.

A copy of the letter the Internet Infrastructure Coalition sent to the US Trade Representative is available here (pdf).

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.





Source link


In the summer of 2017, one of the most important anti-piracy initiatives of recent years was born.

After years of protecting their own content from unlicensed reproduction and distribution, 30 of the world’s most powerful media companies came together to form the Alliance for Creativity and Entertainment (ACE).

Led by the MPAA (now MPA), the companies declared a pooling of resources to tackle piracy more efficiently and on a global scale. Since then, ACE has added several new members to bolster the ranks and this week added two more, one of which is particularly notable.

“We are excited to have Comcast and Viacom join ACE – our leading global content protection organization,” says Charles Rivkin, Chairman and CEO of the Motion Picture Association.

“As the parent companies of two of our original members, they have been supporters of our efforts and numerous successes, but now as members, they will strengthen the legal and operational work we’re able to do to reduce the threat of piracy and support creators.”

Viacom is the parent company of Paramount Pictures, which in turn is a current member of both the MPA and ACE. It also owns UK-based Channel 5, which joined ACE in March 2019.

Comcast owns ACE members NBCUniversal, Sky, and Telemundo, all of which have been with the alliance from its inception. Comcast also operates telecoms giant Comcast Cable, which under the Xfinity brand is one of the largest telecoms companies in the United States.

The addition of Comcast to the Alliance for Creativity and Entertainment is intriguing. Among almost three dozen other current members, it is the first Internet service provider to commit to the global anti-piracy initiative. How that will play out on the ground is currently unclear.

Given that three of its subsidiaries are already members, the addition of Comcast seems a logical move. ACE, however, seems to be placing emphasis on Comcast’s position as a major ISP which, with imagination, could have all kinds of implications when it comes to anti-piracy enforcement.

ACE plays its cards very close to its chest and we know it only publicizes a small percentage of its actions. As previously reported, many others are kept deliberately quiet. What we know thus far though, is that ACE tends to focus on the provision and distribution of infringing content, rather than targeting end-users – customers of ISPs for example.

Nevertheless, that Comcast and by extension Xfinity are now part of the world’s largest anti-piracy coalition should give pause for thought. If nothing else it shows clear intent by an ISP to positively participate in the global fight against movie and TV show piracy, in all its forms. ACE will no doubt consider this a major achievement.

The full list of members of the ACE anti-piracy coalition now reads as follows: Amazon, AMC Networks, BBC Worldwide, Bell Canada and Bell Media, Canal+ Group, CBS Corporation, Channel 5, Comcast, Constantin Film, Discovery, Foxtel, Grupo Globo, HBO, Hulu, Lionsgate, Metro-Goldwyn-Mayer (MGM), Millennium Media, NBCUniversal, Netflix, Paramount Pictures, SF Studios, Sky, Sony Pictures Entertainment, Star India, Studio Babelsberg, STX Entertainment, Telefe, Telemundo, Televisa, Univision Communications Inc., Viacom, Village Roadshow, Walt Disney Studios Motion Pictures, and Warner Bros. Entertainment Inc.

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.





Source link


YouTube’s copyright takedown policy poses one of the biggest threats to the streaming platform’s content creators.

YouTubers who receive three copyright infringement strikes can easily lose their channel, which for some equates to their livelihood.

This looming threat also provides an opportunity for scammers. As we reported a few months ago, YouTube’s copyright takedown process was being abused to extort YouTubers, including ‘ObbyRaidz’ and ‘Kenzo.’ Both repeatedly received ‘strikes’ against their channels.

The scammer in question pretended that he was the legitimate owner of the videos uploaded by the users and requested money to retract the false claims.

“We striked you. Our request is $150 PayPal, or $75 btc. You may send the money via goods/ services if you do not think we will cancel or hold up our end of the deal,” the scammer wrote.

This abuse didn’t go unnoticed by YouTube, which tracked down the alleged offender and took action.

Last month the video streaming service sued Nebraska-resident Christopher Brady, accusing him of violating the DMCA by falsely claiming the content of other YouTubers as his own.

According to YouTube, Brady repeatedly attempted to harass and extort money from content creators through his bogus copyright infringement claims.

The company believes Brady went as far as using the address of YouTube user Cxlvxn, which is shared with a rightsholder for the purpose of filing a lawsuit, in an attempt to dispatch a large number of police officers to his home.

In the complaint, YouTube demanded a jury trial but it didn’t get that far. A few hours ago they submitted an agreed judgment and permanent injunction to the Nebraska federal court, which settles the matter without any further bloodshed.

Under the proposed injunction (pdf), Brady is prevented from filing any bogus copyright claims going forward. In addition, he separately agreed to pay $25,000 for his misconduct, offering a public apology to all the people who were hurt by his actions.

“I, Christopher L. Brady, admit that I sent dozens of notices to YouTube falsely claiming that material uploaded by YouTube users infringed my copyrights,” reads the apology, which YouTube shared with The Verge.

“I apologize to the YouTube users that I directly impacted by my actions, to the YouTube community, and to YouTube itself,” Brady adds.

The proposed judgment and injunction have yet to be signed off by the court, but this is expected to happen later this week. It’s not clear whether any of the affected users will receive compensation, but YouTube says that it’s happy with this outcome.

“This settlement highlights the very real consequences for those that misuse our copyright system. We’ll continue our work to prevent abuse of our systems,” a YouTube spokesperson said.

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.





Source link


The Freedom of Choice

One of the main tenets of both Kodi and open-source software in general is freedom of choice. By making the software freely and publicly available without charge, users are able to try the software with no financial outlay or risk. As the source code is also available for inspection, the risks of “hidden nasties” such as covert information gathering and other data mining can also be alleviated. Anyone can download, review and audit any part of the software that they wish, as well as submitting any updates, improvements and bug fixes that they may make.

This notion of user choice is also key to the operation and support offered by Team Kodi, both through GitHub and the web forum. One common question is why we don’t do more to combat piracy, especially given our zero tolerance policy towards support (or lack thereof, aside from attempts to completely remove from infected systems). The simple answer is that we believe in user choice, and that if the user makes the conscious and informed decision that they want to use Kodi for such purposes then that is up to them. Similarly, any resultant technical or legal problems which may arise are also down to them, and there’s no liability or responsibility on Team Kodi for what a user has chosen to do.

 

An Informed Choice

Key to that stance, though, is that the user has made an informed choice. This is the reason why third-party repositories are not usable by default in Kodi. The user has to make a specific action to enable their usage, complete with a warning pop-up message about the risks and liabilities involved. We take responsibility for our official repository and what we we allow into it, and content is reviewed and audited before it is included. Any fork of Kodi which seeks to override or remove this default setting would immediately be blacklisted by the team, and no support for it at all would be offered by any official Team Kodi outlet.

Similarly, this is why the team does not allow forks with pre-installed add-ons to be made without complete rebranding and disassociation from Kodi, and why no “builds” are supported. By “build”, here we use the term in the common user parlance (as can be found on many of the third-party YouTube videos and parasitic “fan” websites that we would rather did not exist) for collections of add-ons either grouped into an “all in one” installation, or even images of Kodi with such add-ons pre-installed. This obviously completely removes the user choice element, aside from the choice to install the build in the first place.

The main issues here are twofold. Firstly, whilst such builds tend to install popular piracy add-ons, they often also quietly install other code under the hood with little or no visibility to the user. This can range from scripts that try to maintain the installation (given the limited lifespan of such add-ons) to ones that aim to sabotage or remove those of rival suppliers – and, in the extreme, even to malicious malware scripts to form botnets, mine digital coinage or perform other nefarious actions behind the user’s back.

Secondly, such builds tend to be advertised on websites and in videos as being official, legal and legitimate. This is often deliberately done to confuse the naive user that they are getting something for nothing and a good deal. Of course, a moment’s thought and common sense should tell anyone that if media providers such as Sky, HBO and Disney charge people what they do for their officially-provided services, then offers of them for free cannot be above board. Similarly, sources or add-ons offering media that wouldn’t normally be available, such as movies that are still in cinema theatres, should also ring alarm bells in the head of any consumer.

 

Uncommon Sense, or Stating the Obvious?

Unfortunately in this day and age such common sense does not seem to apply to the internet. We often see this on the forum when new users request support for such installations and then apologise with “sorry, I didn’t know” or similar when we decline to assist. They completely miss the point that it was their choice and basic greed that led them there, and a moment’s thought should have given them pause. For some reason users seem to willingly accept the most obviously dodgy deals on the internet, ones that they wouldn’t touch if offered in a pub car park, car boot sale or other “real world” environment.

Our simple advice is to apply the same judgement to your Kodi installation as you would to anything else in life. If the deal you’re being offered seems too good to be true, it quite probably is and there will be a catch somewhere. The team works hard to provide the Kodi software and also to curate the official repository. Both of these can be safely used when obtained from our official site. However, beyond that, the principles of caveat emptor apply. We expect and enforce that users are responsible for their own actions and the repercussions from them.

So before using any third party repository or add-on, take a moment to consider what you know about the authors, their reputation and what they are offering. Don’t be fooled by false promises and dodgy deals – in the end the person responsible for your devices’ safety and security is you.





Source link


There was uproar in the media this past weekend after a violent video meme was reportedly shown at a pro-Trump conference.

The video, a doctored version of the famous church scene from the movie Kingsman, depicts Trump killing his critics, from both the media and politics.

The video was made by TheGeekzTeam, an entity that creates content for a website run by Carpe Donktum, a prolific pro-Trump supporter and meme-maker. During the fallout on Monday, Carpe Donktum’s Twitter account was suspended, an event which led various media outlets to connect the events of the weekend with the suspension.

A Twitter spokesperson effectively confirmed that the suspension was DMCA related, noting that it responds to “valid copyright complaints sent us by a copyright owner or their authorized representatives.”

Twitter made no mention of which content had caused the suspension but the actual DMCA notice obtained by TorrentFreak confirms it had nothing to do with the ‘Kingsman’ meme published over the weekend.

The DMCA notice, served not only against Carpe Donktum’s Twitter account but also around two dozen others, was actually filed by Universal Music Group. The offending Twitter URL is highlighted below.

The Tweet in question dates back to February 5, 2018, and remains online, along with the text “In case you missed the T-Mobile Superbowl Commercial. Here it is!” However, the embedded video has been removed, indicating that this was the source of the DMCA complaint.

Comparing uploads on Carpe Donktum’s YouTube account on the very same day we find a video entitled “T-Mobile Superbowl Commercial Fixed“, which is a doctored version of T-Mobile’s official Superbowl commercial.

It’s pretty clear why Carpe Donktum’s video was taken down. While it contains other copyrighted music throughout not contained in the original video (a lullaby rendition of Nirvana’s ‘All Apologies’ according to Shazam), it’s the last 14 seconds of the 80-second video causing the problems.

With Trump wearing a ‘Thug Life’ hat, obligatory sunglasses and sporting a huge joint in his mouth, the track ‘Ultimate’ by Denzel Curry booms from the video. This isn’t what Universal Music wanted and judging by comments made by Curry in 2017, it probably isn’t what he wanted either.

“I felt like I was part of the problem honestly. Being disillusioned and thinking, ‘nah, that’s not gonna happen, this nigga ain’t gonna be president.’ Then this nigga became president. So what the fuck just happened? I don’t get all the choices I want, but I definitely didn’t want this nigga to be my president,” Curry said.

One copyright complaint isn’t usually enough for Twitter to suspend an account but Carpe Donktum now has at least three against his. In addition to the notice sent Monday, two others are on record, one sent in April and another in June. Only the one sent by Universal Music has a listed sender, the other two have their details redacted.

Carpe Donktum’s Twitter account has now been restored but for how long remains open to question and probably dictated by future conduct.

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.





Source link


As we approach Kodi DevCon (our annual team member conference) we continue our quest for greater transparency and openness in how the project is managed. We’d like to touch on project finances: specifically where the money comes from, and where it goes.

 

Outreach is a major expense. In 2018 Team Kodi members presented at:

  • FOSDEM – @martijn, @yol and @lrusak gave talks (herehere and here)
  • Open Source Leadership Summit – @natethomas spoke (slides)
  • SCALE – @natethomas spoke, How to Destroy a Community (video, overview and slides)
  • Linaro Connect – @lrusak spoke (video)

 

Team members also attended:

 

Some attendance costs are fully covered by the conference organizers. Sometimes our team members pay their own way. Mostly Kodi funds or part-funds a trip. Your donations allow the team to play an ongoing and active part in the Open Source community; both sharing our own knowledge with others, and learning from them so we can make Kodi better.

Server infrastructure, hosting, bandwidth and CDN services, build servers, hardware items for testing, and some minor subscriptions, e.g. accounting software (as we need to file tax returns) are lesser but regular recurring costs. Some are offset by sponsors, most we fund ourselves.

Kodi DevCon is our largest expense of the year. We are a global team and the project talks mainly in text, via the forums or Slack. This creates endless opportunities for cultural, linguistic and more general misunderstanding. DevCon typically brings 20-30 team members together somewhere in a cheaper part of Europe and gives them a chance to speak face-to-face, share ideas, share some drinks and laughs – helping to defuse tensions that build up. We also get to talk about Kodi a lot (even more than normal) which spares our partners for a few days. They do get sick of hearing about it :)

The project has three sources of funding: sponsorships, public donations, and sales of Kodi branded tee-shirts and Raspberry Pi ‘flirc’ cases. There is zero advertising on our website and in our application – and this will never change (we reject many emails from advertising sales people each week). While we need to raise funds to cover our annual costs, we are not motivated by money, and nobody is paid by our foundation – we are 100% volunteers.

 

Kodi is free – and will always be an Open Source (GPL) project – because we chose to be Open Source and because it is impossible for us to change our license. We have never required contributors to submit a CLA, so they own the rights to their code, and a license change would need the permission of all contributors. Our oldest code (c.2002) cannot be attributed to a single author, and solving that would need us to rewrite an impractical volume of code. And the team simply wouldn’t allow the license change; especially @spiff our resident Viking who has been around since the original Xbox days.

 

We do like sponsors – as long as they are relevant and publicly supportive of Open Source software. Sponsoring Kodi does not bring any special treatment or influence on the team, and all sponsors are vetted by the board. Past sponsors have donated cash to our Foundation (our preferred option) or provided developers with hardware (spec. kit to write code on, not test samples) and one even bankrolled DevCon which was awesome. Current Gold sponsors provide us with free services (e.g. site hosting) which saves us a fortune. You can see their names in the footer of this page and we cannot thank them enough!

 

We are proud to announce our latest Diamond sponsor – Libre Computer, who manufacture a range of Allwinner, Amlogic and Rockchip single-board computer hardware for industrial and hobbyist use-cases (including HTPCs). We are normally shy when hardware vendors approach us with an offer of sponsorship, but Libre Computer has been funding a range of Open Source projects and Linux multimedia development that directly benefits the ecosystem around them in addition to their own products. We like their approach to FOSS, and we appreciate their support.

 

Interested in individually supporting us? – there are several ways:

  • Our Donate page has PayPal, BTC and Wire Transfer info
  • Amazon (US) will donate 0.5% of your purchases to registered non-profit organizations of any US purchases via smile.amazon.com.  We are listed as “Kodi Foundation” and here is a link to sign up: Amazon Smile

 

Thank you to everyone who contributes to Kodi and hopefully makes it possible for the team to have our developer conference in October – and if you know of a company contributing to Open Source who might be interested in becoming a Kodi sponsor, please drop us a line.

Tags: 





Source link


When they don’t use protection such as VPNs, pirates who use BitTorrent-like peer-to-peer systems are relatively easy to track down. Their IP addresses are publicly viewable meaning that one subpoena later, content companies can obtain their names and addresses from ISPs.

The situation is quite different when it comes to users of regular ‘pirate’ IPTV services. Their IP addresses and personal details are usually only known to their provider, so proving infringement is more difficult. Of course, if the IPTV provider itself is targeted by a company like DISH, it may decide to squeal to lessen the pain of its own demise.

In the summer it was revealed that NagraStar had been sending out settlement letters to people it accused of pirating DISH and Bell content using pirate IPTV services. The company reportedly asked for around $3,500 in compensation to make a potential lawsuit disappear.

Now, according to sources cited by CordCutters News, NagraStar and DISH are upping the tempo by threatening yet more IPTV users with lawsuits.

The publication says that it has received multiple reports of people who have been tracked down and provided with copies of their PayPal transactions which showed they purchased a subscription from illicit IPTV services.

Which IPTV services are involved this time around isn’t currently public knowledge but a user of RocketIPTV was previously forced to apologize on NagraStar’s website as part of a settlement.

Sorry…

None of this should come as a surprise. There are plenty of stories from users around the web indicating that NagraStar has obtained their records from a ‘pirate’ supplier, whether that was an IPTV provider or, more commonly, someone dealing in Internet Key Sharing (IKS) servers or codes.

In fact, when examining some of DISH’s ongoing lawsuits last week, TF noticed a statement from the broadcaster clearly indicating that it had obtained business records from a company called Digital TV that was helping it to sue. An excerpt from the case (pdf), filed on October 1, 2019, provides the details.

Achievement unlocked: Business Records

While this is a new case, other cases involving DISH, NagraStar, NFusion Private Server, and its resellers have been ongoing for a very long time.

One case, which dates back six years, shows that handing over information to NagraStar is part of the plan and that the company is very thorough in chasing people right down the chain.

More records obtained…

While obtaining satellite programming using IKS was once rampant and is still an issue for broadcasters, IPTV is arguably a bigger problem today. With that in mind, it shouldn’t come as a surprise that DISH and its partners are branching out to target customers of IPTV services in the same manner.

And with IPTV resellers being asked to pay around $7,500 in settlements, it shouldn’t come as a surprise when they hand over subscribers’ personal details either. After all, the skin-saving game is hardly new when people are faced with damages claims in the hundreds of thousands of dollars.

TorrentFreak was previously informed that most providers rarely care whether people supply their correct information when signing up for a service. But when PayPal addresses are involved, in most cases DISH is already too close to home.

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.





Source link


So, here we are, the third and final day of DevCon 2019. It’s likely to be a short list of topics this morning before some people head home while those who remain use the time together to write some fabulous code. So, let’s get straight to business.

 

We kicked off with kwiboo and jernej (from the LibreELEC team) talking about HDR support on Linux. This goes way beyond Kodi, as it’s kernel-level work to improve GPU support; this then ripples through the operating system before finding its way to Kodi via V4L2 and ffmpeg. We’ve been working mostly with the Intel team to complete support for their chipset, but there’s also basic work in place for Allwinner, Amlogic and Rockchip. This means that we’re well on the way to having a common implementation across all major chipsets that are likely to be running Linux. The industry-wide, concerted focus on V4L2 (driven significantly by Google/ChromeOS) also means that we can finally strip away large chunks of proprietary, vendor-specific code as all of these chipsets move to a common, standardised API model. We’ve grudgingly tolerated these for a long time, but they make maintaining and updating functionality so much more difficult when you need to consider dozens of different code paths, so we’ll be glad to see the back of them.

A couple of topics that took some time but didn’t really make it to the final sessions, so perhaps we’ll come back to them later: roles and responsibilities within the Board, the overall Kodi architecture and how it could be improved, potential for web browser support in Kodi. Just headings for the moment, so don’t get too excited.

Following this, we spent a chunk of time on introspective activities: admin rights, system and application access, social media access, password lockers, two-factor authentication, and similar. We also talked about Team matters: new members, absent friends, acknowledgements. Maybe not really interesting to the outside world, but still stuff we need to worry about if we’re to keep everything running smoothly.

And now it’s time for what a room full of developers (“a segfault of programmers”, perhaps?) with laptops does naturally. All around me, I can see screens scrolling as code compiles, the brightly-coloured syntax highlighting of IDEs, the transient flash of windows and terminal prompts as people cycle between them. The mob is talking animatedly about CODECs, rendering planes, operating systems, APIs, kernel calls. In the distance, a heated debate begins about the relative merits of Linux distros. There’s a constant murmur of noise, the combination of conversation, keyboard taps and error sounds. The mood for the rest of the day is set… let’s hope no-one breaks anything important… ¯_(ツ)_/¯

So, that’s it for this year. Thanks for listening, and I hope you’ve found these posts informative. More than that, though, thanks for continuing to support Kodi!

All the best,

Team Kodi.

Tags: 





Source link


Alongside other entertainment industry groups, the Motion Picture Association (MPA) sends a yearly overview of notorious foreign piracy markets to the US Trade Representative.

These annual submissions help to guide the U.S. Government’s position toward foreign countries when it comes to copyright enforcement.

We previously covered the submissions from the RIAA and ESA, which both listed a wide variety of pirate sites including torrent, streaming, MP3-downloaders, and ROM archives.

The MPA’s submission was published later than the others but is worth highlighting nonetheless. In recent years it has solely focused on online threats with familiar names such as The Pirate Bay, Openload, and Fmovies reappearing time and again.

This year is no different. Many of the threats the MPA highlights are identical to last year. Aside from traditional pirate sites, this includes mobile apps, unauthorized IPTV services, and hosting companies. While not a foreign company, CDN provider Cloudflare is repeatedly mentioned as well, as it has many piracy sites as customers.

“The Pirate Bay, and other notorious pirate sites, remain Cloudflare customers despite repeated notices of infringement to Cloudflare,” the MPA notes.

A complete list of all the identified notorious markets is listed below, but we will zoom in on two entities added as new entries this year.

The first one is 1XBET, a gambling company known for its advertising appearing in ‘cam’ copies of movies. The casino, whose ads appear on more than a thousand pirate sites, is well known among people who frequent these platforms. Now, it’s on the MPA’s radar as well.

“1XBET is a Russian gambling site that has started to support some of the
earliest releases of infringing theatrical camcords and infringing streams of live television broadcasts. It has become the third most active online advertiser in Russia,” the MPA informs the USTR.

The MPA’s report cites research from Mediascope which found that only Google and PepsiCo ads are more prevalent online in Russia. While that covers all publications, the movie industry group draws specific attention to the embedded ads that appear in popular pirate movie releases as well as their titles.

“Reportedly, the online casino pays to insert visual and audio advertisements into new piracy content sources incentivizing camcord and livestreaming piracy. 1XBET’s watermark with promotion codes is ‘burned’ into the video files of infringing camcord recordings. Thus, piracy is used as a vehicle to support this online gambling giant,” the MPA notes.

What’s not mentioned by the MPA is that 1XBET also sponsored several major UK football clubs and Italian football league Serie A. Responding to some earlier controversy, a 1XBET spokesperson said that it takes the piracy advertising allegations very seriously.

Another newcomer in the MPA’s list of notorious markets is Baidu Pan, the file-hosting service operated by the largest search engine in China. According to the movie industry group, it’s often used to share copyright-infringing material.

“Large quantities of infringing content are stored on Baidu Pan with
links disseminated through popular Chinese social media platforms and piracy linking sites,” the MPA writes in its submission.

The MPA points out that Baidu has a market share of over 75 percent in China, which makes it the second-largest search engine in the world. As such, it is vitally important that the company has rigorous content protection standards and that it cooperates with rightsholders, the group notes.

Baidu has made some progress in recent years when it comes to its takedown tools, but takedown rates and timeframes remain inconsistent or too long, the MPA says.

“Baidu should be encouraged to do more, including improve implementation of its takedown tools, apply rigorous filtering technology to identify infringing content, and take more effective action to suspend or terminate repeat infringers to ensure all rights holders are treated equally and infringing content and links are removed expeditiously,” the submission reads.

The MPA hopes that its recommendations will be helpful to the US Government, but whether adding 1XBET and Baidu Pan will have any effect has yet to be seen.

The MPA’s full report is available here (pdf). The USTR will use this input to make up its own list of notorious markets. This will help to identify current threats and call on foreign governments to take appropriate action.



List of all the sites and services the MPAA identified as notorious markets.

Linking / Streaming

  • B9good.com
  • CB01
  • Cda.pl
  • Cimaclub.com & cima4u.tv
  • Cinecalidad.to
  • Dytt8.net and Dy2018.com
  • Fmovies.is/.to (formerly .se)
  • “Indo 21” (Indoxxi) and many related domains
  • Movie2free.com
  • MrPiracy.site and .xyz
  • Phimmoi.net
  • Seasonvar.ru

Cyberlockers / video hosting

  • 1fichier.com
  • Baidu Pan
  • Clipwatching.com
  • Gounlimited.to
  • Netu.tv
  • Openload.co/oload.tv
  • Rapidgator.net
  • Rapidvideo.com
  • Streamango.com
  • Uploaded.net
  • Uptobox.com
  • Verystream.com
  • VK.com

Illegal IPTV

  • BestBuyIPTV.com
  • Buy-IPTV.com
  • GenIPTV
  • ThePK.tv
  • TVMucho.com

Apps

  • RenRen Shi Pin
  • ShowBox
  • Unblock Tech (unblocktech.com)

P2P sites

  • 1337x.to
  • Rarbg.to
  • Rutracker.org
  • Tamilrockers.ws
  • ThePirateBay.org
  • Torrentz2.eu
  • Zooqle.com

Hosting services

  • Fishnet Communications LLC
  • M247
  • Network Dedicated SAS
  • Private Layer

Advertising

  • 1XBET

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.





Source link


Morning, all. It’s a beautiful day here, and we’re just waiting for the last few latecomers to arrive before another day of DevCon…

 

We kicked off with Python 3, following on from yesterday’s conversation. The general consensus was to get this merged and live with any minor breakage – we need to get this done, and can’t wait for absolutely every add-on to be updated before we merge. This shouldn’t be a surprise to anyone, after all.

The conversation then quickly shifted to sarbes talking about features that would make life much easier from a Python developer’s perspective. These are really around how the core code handles items, lists and displays, and how this could be modified to improve the user experience (e.g. pagination of long lists). The obvious affect is on lists of Internet content, but it would also improve PVR/EPG display, searching, and others. Similarly, allowing add-ons to specify viewtypes or just know more about what views the user prefers would make things more consistent and usable. Other ideas included subtitle support for use within add-ons, and some kind of URI mechanism so an add-on could transfer a path from one Kodi instance to another – this would allow you to move playback from your ‘phone to the TV, for example.

Next up, jimcaroll stepped up to talk about Codegenerator, which is a core part of Kodi’s Python (and, in theory, other scripting language) API, auto-generating the C++ API code as required. The main purpose of this is to reduce code size and improve maintainability, but it could potentially scale to give a more flexible, standardised approach to supporting multiple different types of external module. Only a concept, but that would open up huge possibilities for add-ons in C#, JavaScript, Groovy and many others, bringing very different functionality, security models, and scope.

This was followed by an update on tvOS by kambala and fuzzard. Much of the Apple-specific code has been floating around for a while in various forks and branches, so this is a more concerted effort to bring it all back together, update and augment it to form a complete package for the Apple TV 4. Still a work in progress, but getting closer.

Next up, lrusak took the stage to lead a session on how platform specifics can block or delay overall development – for example, when a pull request affects all platforms but there’s some obscure issue on one particular operating system. Older versions of operating systems may come with different libraries or different development toolchains; different platforms might diverge totally or even miss out components that are business-as-usual on everything else; API calls can behave slightly differently even when they shouldn’t.

So, should we hold everything back because of one platform? Should we hold back all platforms because, say, an older but still maintained (e.g. LTS) OS release can’t support some aspect of newer functionality? Should we merge a change if it compiles on all platforms except one, effectively breaking that platform until “later”? This isn’t an easy issue: ultimately, we want to get new functions and fixes out there, and that may mean living with some dead code and platform-specific workarounds in the meantime; alternatively, we simply freeze older platforms at a previous Kodi release, and move on (as, indeed, many other application developers do). As always, though, if you’re a developer who could help here, you know where to find us…

After a break for lunch, kib and keith kicked off a conversation about Foundation responsibilities and costs – some activities are legal in nature, many of them administrative, all of them important. As a registered non-profit organisation, we’re obliged to submit certain paperwork on an annual basis to keep that status along with US tax declarations. Forget this, or get it wrong, and we face losing our status and either incurring significant taxes or else paying lawyers to re-submit and regain it – neither scenario being something we want. As such, we have an ongoing task to better document what people do and highlight the imperative tasks within that list: even as a bunch of volunteers, there’s a degree of professionalism required behind the scenes, and that means sometimes paying for help.

Time to return to more technical matters: jimcarroll once again took the floor, this time to talk about threading in Kodi. Given the history of Kodi, there was a lot of platform-specific threading mechanisms. That creates complex code, with dependencies and checks that just get in the way – so, can we collapse it down into a more platform-independent model, or, at least, a minimal set of variations? It turns out that you can slim down to two main models: POSIX and Windows, and that’s where the work has been heading. Some code will still need variations, though, although other code can be collapsed still further into newer, more standardised threading mechanisms that have been implemented on all platforms since the original code was written (e.g. as implemented in C++11).

Bringing the afternoon to a close, then, jimcarroll stayed on his feet to talk about DI – dependency injection. This is a mechanism to move away from a monolithic main() routine that directs all other application activities, and instead having a suite of dynamic dependencies between modules that are resolved at runtime. In this instance, the code can declare a constructor that has a dependency on some other component without explicitly knowing about that other component when the code is written.

 

And that’s it for Day Two. A few more topics to roll over until tomorrow, along with a hackathon while everyone is together – but, until then, that’s all for now.

Tags: 





Source link