We hereby present you the third Beta build of Kodi v18 as we are heading towards the final release. Since we are now in Beta stage our focus will be on solving bugs and possible usability problems. So far it has been proven to be quite solid to use as a daily driver for those who were brave enough to try it out. Of course you should still keep in mind it’s not a final release yet and that on any upgrade a small glitch could happen as we are still doing rework. Once you decide to give it a try it is highly recommended that you create a backup first.

Currently included

A full changelog is nearly impossible to create and in this release article we will only cover the basics. For a more extensive list you can visit our wiki page v18 (Leia) changelog which will be update along the way. From now on all v18 releases will not contain any big new features as we are focussed on bug fixing only.

Most notable fixes to mention in Beta 3:

  • Fix slow browsing in library that was a regression added in Beta 2
  • Updated button maps for controllers that changed Beta 2
  • Improved playback on Android regarding video and DTS-HD audio
  • Revert changes for smooth video on Windows that caused issues
  • Various other fixes regarding video playback

Of course there are several more changes which are listed on our github repository found here: Beta3 changes.

Make sure to also go through our news sections which contain all past announcements regarding the Leia release and some highlights of what it will contain.

Stability and usability is key

In general the whole stability has been improved quite a lot. The times you still get glitches or occasional crashes haven been reduced due to just ripping out not so well coded parts and replaced with a more structured design and standard. Not that the old code was bad however over time new insights were gained and having newer code standards just make it better. Untangling all parts or components and make them behave better next to each other has been one of the biggest efforts done so far.

Current available skins

Due to changes in how Kodi works skins need to be updated for each release. As of this moment we have the following ones have been update by their developers and are readily available from our repository.

Adnoic, Aeon Nox 5, Andromeda, Black Glass Nova, ChromaConfluence, fTV, Grid, Mimic, NebulaOmni, Rapier, Sio2, Xperience1080

More will follow at a later point in time when we approach final release.

Python 2 & 3 compatibility will be enforced

Currently, Kodi includes the Python 2.7 interpreter to run addons written in Python programming language. However, Python 3 was released almost 10 years ago and the matter of implementing the Python 3 interpreter in Kodi has been brought up on the Kodi forum several times. Now, thanks to a successful GSOC 2017 project, we have a working Python 3.6 interpreter for Kodi, and on the latest DevCon 2017 in Prague Team Kodi decided that it’s time to move on and migrate Python addon subsystem to Python 3. <--break->There are several reasons for that:

  • Python 2 End of Life is planned for 2020.

  • Python 3 is mature enough and more and more Python libraries either convert their codebase to Python 3-compatible or drop Python 2 support completely (Django is the most notable example).

  • Most current Python books, tutorials and courses are focused on Python 3.

  • Python 2 is not actively developed. It receives only security patches while Python 3 gets all the cool new features with every minor version.

However, Python 3 is not backward-compatible with the 2nd version so some transition process is required. Currently the plan is the following:

  • Kodi 19 (M*) will be released with Python 3 interpreter for running Python-based addons.

  • After the release of Kodi 18 (Leia) only addons that are compatible with both Python 2 and 3 will be accepted to the official addon repository. Also, Python 3-only addons will be accepted to the repositories for Kodi 19 (M*) and above.

  • Addon developers are highly encouraged to convert their addons to Python 2/3-compatible so that after the release of Kodi 19 (M*) we will have enough addons that work with the new version.

  • Test builds based on Kodi 18 with the Python 3 interpreter will be provided continuously so addon developers can test their addons for compatibility with Python 3. Test builds for Windows are already available for downloading from here and test builds for Ubuntu can be obtained from this PPA.

  • One the v18 version has been branched off for final release the nightlies will become Python 3 only while the release builds will still be Python 2.

Writing Python code that is compatible with both 2 and 3 versions is totally possible and the “big” Python world has been doing it for years since the release of Python 3.0. There are a number of tools and best practices developed to simplify this process. Please read this Kodi Wiki article for more information and technical details about the migration process. Also a special Wiki section has been created that will be updated with new information. You can post questions about converting your addon code to Python 3-compatible or share your experience in “Python 3 migration” subforum on the official Kodi forum.

A new main menu item

As some of you have seen a new menu item has appeared on the main menu. We will expand more on what this means in a future article.

 

The story continues

Although we don’t really have a clear future plan or clear cut goals (except making a great media center) we would welcome any developer who wants to spend time on getting Kodi better in every way. Either improving the core code to newer standards, fixing bugs or implementing a new feature we haven’t thought of. Compared to years ago the code has become better to understand and follow for newcomers to get started. Once we get something written down of certain to reach goals we will certainly share them.

A great improvement has been made on the documentation that explains how to compile and work on the core code for Kodi. We highly recommend to read the article Kodi’s GitHub codebase new face and better documentation.

 

Release time

Since we now started the Beta cycle a final release will be on the near horizon. When the final release will actually be is yet unknown as it all depends on the stability now more people will start using the v18 builds.

That’s about it for now and we’ll go back at improving this upcoming v18 release. Should you wish to give it a try a new version is readily available each day as well as nightly version. We can certainly recommend trying it out however take in mind that it’s not fully production and living room ready yet (take a backup). So far a guestimate of several tens of thousands users already use it so it can’t be that bad can it. You can get it from the download page clicking on the platform of choice and hitting the “pre release” tab. For Android and Windows we have an easy to use download add-on which you can find in our repository.

Go to the Official download page and choose the platform of choice and you will find these builds under the pre release tab.

If you do appreciate our work feel free to give a small donation so we can continue our effort. Just find the big “Donate” button at the top of the website.

May the force be with you…..





Source link


Founded in 1876, the American Chemical Society (ACS) is a leading source of chemistry-focused academic publications. Founded in 1880, Elsevier is one of the world’s largest academic publishers.

Both companies have been very active in recent times, suing various platforms (1,2) that facilitate unauthorized access to their papers.

This week, in a lawsuit filed at a U.S. federal court in Maryland, the pair accuse scientist and researcher networking site ResearchGate of committing the same offenses.

“This action arises from the massive infringement of peer-reviewed, published journal articles (‘PJAs’). Plaintiffs publish the articles in their journals and own the respective copyrights. Defendant deliberately uses infringing copies of those PJAs to drive its business,” the lawsuit reads.

Based in Germany, ResearchGate promotes itself as a professional network for scientists and researchers. The site claims 15 million members, who use the platform to “share, discover, and discuss research.” It’s mission is to make research “open to all.”

According to ACS and Elsevier, however, that openness had led to serious infringement of their rights.

“The lawsuit is not about researchers and scientists collaborating, asking and answering questions; promoting themselves, their projects, or their findings; or sharing research findings, raw data, or pre-prints of articles,” the complaint states.

“This lawsuit focuses on ResearchGate’s intentional misconduct vis-à-vis its online file-sharing / download service, where the dissemination of unauthorized copies of PJAs constitutes an enormous infringement of the copyrights owned by ACS, Elsevier and other journal publishers.”

The publishers claim that the alleged infringement taking place on ResearchGate isn’t an accident, since the platform utilizes plaintiffs’ content to grow its traffic, content, and revenues. Indeed, they claim that ResearchGate not only induces others to upload infringing works but also does so itself. As a result, ResearchGate has turned into a “focal point for massive copyright infringement.”

ACS and Elsevier claim that when users upload a copy of a PJA to ResearchGate, the company stores them on its servers where they are made available for viewing or download as a PDF file. Users are also able to share links to these works on social media platforms including Facebook, Twitter, and Reddit.

“ResearchGate consistently and successfully attempts to encourage and trick authors into uploading copies of PJAs that it knows should not be posted on the RG Website. One tactic is the combination of creating author profiles, publication pages, and journal pages, along with the ‘Request full-text’ feature,” the complaint adds.

However, in addition to user uploads, the companies claim that ResearchGate also adds content itself, using scraping techniques to acquire copyrighted works which are them uploaded to its website for viewing or download. The publishers say that ResearchGate hints at its own involvement in providing content with a statement on its website.

“Proprietary content generally appears on ResearchGate only when it has been uploaded by an author,” the statement reads. “So, if there’s already a full-text of your publication available on ResearchGate, the most likely explanation is that it has been uploaded by one of your co-authors.” (emphasis as per complaint)

Furthermore, the plaintiffs note that ResearchGate previously published a job posting in which it attempted to hire someone “with hands-on experience in building and maintaining web crawlers” to “build web crawlers to discover and index university websites.”

ACS and Elsevier state that before filing this lawsuit, they attempted to negotiate with ResearchGate to have it operate “within the law.”

Working through a trade group called the International Association of Scientific Technical and Medical Publishers, the publishers say they asked ResearchGate sign up to a voluntary scheme to regulate article sharing but the company refused. The publishers do acknowledge that some infringing works were taken down but ResearchGate has not explained why.

With large numbers of allegedly-infringing works on the site, the publishers are now suing ResearchGate for direct copyright infringement, inducement of copyright infringement, contributory copyright infringement, and vicarious copyright infringement.

In conclusion, ACS and Elsevier ask the Court to order ResearchGate to cease-and-desist all infringement of their copyrights, delete all content owned by the plaintiffs, and award statutory damages of $150,000 per infringed work.

This isn’t the only lawsuit ACS and Elsevier have filed against ResearchGate. In October 2017, the companies took action in Germany, claiming that since ResearchGate knows files are infringing, it has an obligation to remove them, even when they haven’t received a specific takedown notice.

The lawsuit 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 tandem with many other copyright industry groups, the RIAA sent its overview of “notorious markets” to the US Trade Representative (USTR) this week.

The group lists more than two dozen pirate sites, categorized by stream-ripping, MP3 download and search portals, torrent indexers, cyberlockers, and unlicensed pay-for-download sites.

The RIAA’s overview is in many regards the same as last year’s, and the full list of the sites is provided below. What is new, however, is the focus on so-called “bulletproof” hosting providers.

These hosting companies have very lenient policies and protect the identities of their customers. As such, they are often used by spammers, scammers, and also pirate sites. This isn’t by any means a new phenomenon, but the RIAA has flagged it as an emerging threat.

“[I]nfringing sites are turning more towards offshore hosting ISPs that support the sites’ infringing activities,” the RIAA informs the USTR.

“These ‘Bulletproof’ ISPs support various types of criminality through considerable leniency in the kinds of materials they permit to be uploaded and distributed via their networks.”

The problem with these companies is obvious. Ideally, copyright holders want hosting providers to shut down blatantly infringing sites, but these outfits are not responsive to warning letters or infringement notices.

The RIAA highlights two of these bulletproof hosts. The first is the Ecatel/Quasi Networks pair, which are believed to be closely related. Both companies are known to law enforcement and were targeted in a lawsuit filed by anti-piracy group BREIN last year.

“Quasi Networks is responsible for hosting various sites engaged in the transmission of pre-release works, including dbr.ee, xclusivejams, nippyspace, mp3monkey.net, gosongs, and leakth.is.

“With little recourse to remove infringements, both Ecatel and Quasi represent a significant danger to our member companies,” the RIAA adds.

The second bulletproof hosting provider is FlokiNET, which offers servers in Romania, Iceland, and Finland. The RIAA recently uncovered that the host was listed as the registrant for the pre-release leak site musicmafia.to, likely to protect a customer. The site itself disappeared soon after.

FlokiNET

On its website, the hosting provider notes that customers don’t have to share any personal details or identification, which is appealing to a certain audience.

“As a result, many different types of websites hosted on the ISP host bestiality pornography and fraudulent sites, amongst others. Other infringing sites hosted on FlokiNet include avxhome.se, djnotorioussam.com, and x1337.to.

“The operator of FlokiNET is known to the authorities and resides in Romania but, to date, no action has been taken to close the service,” the RIAA adds.

Aside from bulletproof hosting services, the RIAA signals another trend. Over the past year, it has observed a sharp rise in the number of pre-release pirate sites hosted by Nigerians. Apparently, this number has grown to more than 400, and most use the Nigerian-operated ISP speedhost247.com.

By reporting these sites and companies, the RIAA hopes to have them placed on the USTR’s final list of notorious markets. This can then be used as a political pressure tool against the countries from where they operate.

The full list of the RIAA’s “notorious” pirate sites can be found below. The full report, as submitted to the USTR, is available here (pdf).

Stream-Ripping Sites

– Flvto.biz and 2conv.com
– Mp3juices.cc
– Convert2mp3.net
– Ytmp3.cc
– Onlinevideoconverter.com
– Peggo.tv
– H2converter.com
– Y2mate.com
– Convertmp3.io

Search-and-Download Sites

– Newalbumreleases.net
– Rnbxclusive1.com
– Leakth.is

BitTorrent Indexing and Tracker Sites

– Thepiratebay.org
– Torrentz2.eu
– Rarbg.to
– 1337x.to

Cyberlockers

– Nippyspace.com
– Hitfile.net
– Suprafiles.me and cloudyfiles.me
– Dbr.ee
– Turbobit.net
– Zippyshare.com
– Rapidgator.net
– Chomikuj.pl

Unlicensed Pay-for-Download Sites

– Mp3va.com
– Mp3fiesta.com

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 response to a request from the Office of the US Trade Representative (USTR), the Entertainment Software Association has submitted a list of so-called ‘Notorious Markets’ that undermine the interactive gaming market in the United States.

The ESA represents some of the biggest names in video gaming. From Activision, EA, Nintendo, and Ubisoft, to Capcom, Microsoft, Konami, and Square Enix, the group acts as a voice for companies turning out billions of dollars worth of content. All are reportedly under multi-directional threat, from sites that facilitate direct copying to those who undermine business models and the actual gaming experience.

Linking and Hosting

According to the ESA, linking websites (those that link to content hosted on third-party cyberlocker-type sites) are a key threat.

“These sites typically generate revenue from user donations and/or online advertisements,” the ESA writes. “The following links sites are notable due to their heavy traffic, high volume of infringing video game file links that are indexed, and non-responsiveness to rights holder [takedown] notices.”

First up is a site that most gaming pirates won’t have heard of, which could prove a little counter-productive. P30Download.com is based in Iran, a country that’s rarely linked with a sympathetic attitude towards United States copyright enforcement.

According to the ESA, in August 2018 the platform made available more than 3,000 links to infringing content belonging to ESA members, of which just 2.64% were taken down. Hosted in Iran and published in Persian (not an obstacle for Google Translate), the site is most popular in its home territory and is Iran’s 25th most popular site.

Another site that’s off the radars of most casual pirates is DarkSoftware.net. According to the ESA, the platform indexed almost 4,800 new links in August and is enjoying an upsurge in traffic due to its focus on “circumventing the technical protection measures” in games consoles.

The ESA notes that DarkSoftware uses the “services of a U.S.-based content delivery network” but doesn’t mention CloudFlare by name. It doesn’t mention where the actual site or its owners are based either but publicly available information points to an address in Florida, which may or may not be legitimate.

Of course, linking sites cannot function if they have nothing to link to so it’s no surprise that file-hosting sites are high on the ESA’s list. Its main candidate is the fairly low profile Rapidu.net, which is popular in Poland and also uses Cloudflare, although the ESA again hesitates to name the platform.

1Fichier, on the other hand, is a site with a much greater following. Hosted in France, the site has a global rank of 1,093 and reportedly hosts at least 2,700 links to ESA member content. This cyberlocker-type site is reluctant to respond to takedown notices, with just 0.59% of content removed following complaint, the ESA notes.

ESA Members

ROMs

Given the recent furore surrounding classic gaming ROMs (1,2,3,4), it’s perhaps no surprise that ROMUniverse.com appears in the ESA’s submission to the USTR. Claiming a catalog of 60,000 ROMS serving 375,000 members, the ESA says the site has enjoyed “significant traffic increases” recently due to offering downloads for the latest video games consoles.

Interestingly, given the fact that the USTR’s report focuses on overseas sites, the ESA notes that ROMUniverse is hosted in the United States at Frontier Communications. Similar US-based hosting is provided by GoDaddy for ISOsLand.net, another platform on the ESA’s list.

Torrent Sites

Few submissions to the USTR would be complete without a complaint about The Pirate Bay, and this entry from the ESA is no different.

“Despite some recent downtime, this site continues to be a major source of infringing copies of ESA member company video games,” the ESA notes. “Over 2,200 infringing URLs were found on the site in August 2018. It currently operates with the assistance of the U.S.-based CDN referenced above,” the trade groups adds, without directly naming CloudFlare.

While The Pirate Bay is certainly the highest-profile torrent site, the ESA appears to have bigger problems with a site called PeerTorrents. In August, the group found 8,100 infringing downloads available via the site, which the ESA notes is similar in appearance to LimeTorrents.cc. The site also uses CloudFlare.

Private gaming servers

In this section of its report, the ESA highlights threats to “free-to-play” games that generate revenue from micro-transactions, advertising, and subscriptions. Unauthorized third-party ‘private’ servers allow users to play such games, bypassing the original revenue model and stopping publishers from monetizing their content.

“Establishing and maintaining unauthorized game servers often involves multiple acts of copyright infringement as well as the circumvention of technological protection measures,” the ESA notes, citing Warmane.com and Firestorm-servers.com (World of Warcraft) as culprits.

Cheats and other digital goods

Over the past year, lawsuits against those who maintain and distribute game cheating tools have been frequently reported (1,2,3) so similar complaints in the ESA’s filing are not unexpected.

Established in 2000, Unknowncheats.me heads the ESA’s list, offering up to 10,000 cheats for around 100 gaming titles while generating advertising revenue from its 2.4 million users. Fellow cheat site MPGH.net is said to offer “several hundred thousand” cheats to more than four million users while Iwantcheats.net and Artificialaiming.net service around 720,000 users between them.

Several other platforms are listed in the report as locations to purchase in-game items, CD keys, skins, accounts, and even CD keys, with others offering online subscriptions sourced in cheaper regions of the world and sold in the US.

“We would like to underscore our appreciation to the U.S. officials who drive and administer the out-of-cycle review of notorious markets,” the ESA says in its summing up.

“The resulting Notorious Markets List provides important insights that allow national and local policymakers, as well as law enforcement officials, to evaluate and fairly demand accountability from those marketplaces and the services that support them,” the trade group concludes.

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


Earlier this year, FairPlay Canada proposed to institute a national pirate site blocking scheme.

The coalition of copyright holders and major players in the telco industry, including Bell and Rogers, submitted its plan to the Canadian telecoms regulator CRTC, which subsequently asked the public for input.

This consultation triggered a wave of responses. Many ISPs and rightsholder groups were in favor, but there was also a big wave of opposition from academics, activists, and members of the public.

After a careful review, the CRTC today decided to deny FairPlay Canada’s pirate site blocking application. In its decision, the regulator explains that it lacks the jurisdiction to implement the proposed measures.

“The Commission determines that it does not have the jurisdiction under the Telecommunications Act to implement the FairPlay Coalition’s proposed website blocking regime to address copyright piracy and, consequently, it will not consider the merits of implementing the regime,” CRTC writes.

The FairPlay coalition argued that piracy brings serious harm to the Canadian entertainment industry. While the CRTC doesn’t deny this, it stresses that the Telecommunications Act is not meant to implement such copyright remedies.

“The Commission acknowledges that there is evidence that copyright piracy results in harm to the Canadian broadcasting system and to the economy in general,” CRTC writes.

“However, there are other avenues to examine the means of minimizing or addressing the impact of copyright piracy, including the ongoing parliamentary review of the Copyright Act and the expert panel review of the Telecommunications Act and the Broadcasting Act.”

This means that the controversial site blocking proposal is off the table for now. It’s certainly possible, however, that a revised version will be brought up again in the future.

Digital rights group OpenMedia, a fierce opponent of the plan, is happy with the outcome. Executive Director Laura Tribe describes it as a big win for the open Internet and a true demonstration of democracy in action.

“Today the CRTC protected the open Internet, in an important victory,” Tribe notes, adding that “all eyes will now turn to the Copyright Act Review, to see the final act of this play.”

At the time of writing the FairPlay Canada coalition itself has yet to comment on the decision through their official channels.

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


One more day, with enough content to warrant a separate blog post – partly because people are still here for the most part, partly because of new stuff that’s been added to the agenda as we’ve gone along, and partly because of the topics that, despite our best efforts, managed to escape from previous days.

We began the day with a broad retrospective of the past year: for each person, what went well in the past twelve months, what could have been improved. As you might expect, we covered far too many topics to cover here, spanning as they did nearly every aspect of people, process and technology. However, it was a useful conversation that gave time to both be proud of the positive while reflecting on where we still need to focus more effort. We’ll work through and digest everything that was said and perhaps come back to it as a separate, future post, as the conversation will help shape where we go next.

Next up, lrusak took us through his experiences and presentation at both FOSDEM (Brussels) and Linaro Connect (Vancouver) this year. His talk was mainly aimed at shifting from vendor-specific or closed code (kernel and blob dependencies) to more universal, open source methods, specifically around windowing and rendering on embedded Linux (SoC) platforms such as Allwinner, Broadcom and Qualcomm. As well as simplifying our core code and removing the need for maintenance and use of platform-specific patches, this also has the potential to deliver performance advantages and broader platform coverage. Overall, there are some real benefits once we can tap into specific libraries via standardised kernel calls rather than depend on userspace code that’s in turn reliant on monolithic, all-purpose blobs that may include a whole load of code that simply isn’t needed for Kodi.

We discussed Kodi “remixes” – forks, feature branches, JeOS distributions, and similar variations – and how they link back to our trademark policy and support overheads: what’s allowed, what can we tolerate, what can we manage, how does it appear to our users. This is an area full of opinion and interpretation, rapidly wandering into genuine legal implications. While this is something we really don’t want to have to worry about, it’s something we must keep aware of, as historical experience has demonstrated. As such, we’ll be revisiting aspects of our practices to ensure that we protect Kodi while, at the same time, embracing the broader community where we can see that there’s positive intent and genuine common benefit.

lrusak then returned to the stage to give an update on LibreELEC. That team continues to streamline everything, reducing the maintenance overhead, slimming down the underlying OS overhead, and aligning the user experience more and more closely with core Kodi. He discussed some potential architectural changes that flow out of this goal: future platform support, what libraries could be removed and why (no longer supported or just not needed), what could perhaps be moved upstream so that it becomes part of Kodi and thus not some separate facet of LibreELEC.

And that’s it for day three. Thanks to everyone for their participation, and thanks to the entire community for making Kodi what it is.

One final comment as we close: we really need to offer very many thanks to Roza Zdravkova, who’s been invaluable as our local eyes throughout this DevCon. From helping with transport to pointing out where to go and what to do, she was fundamental to the event’s success. So, “thank you” from the team!

So… that’s it for DevCon 2018. Time to turn to a bit of hacking and development before all going our separate ways once more.

Tags: 





Source link


The North American Free Trade Agreement (NAFTA) between the United States, Canada, and Mexico was negotiated more than 25 years ago.

Over the past quarter-century trade has changed drastically, especially online, and to accommodate these changes the three countries have been working hard to modernize the international deal.

A few weeks ago the US and Mexico reached consensus on many key issues and last night Canada came along, resulting in a new version of NAFTA. Titled the United States-Mexico-Canada Agreement (USMCA), the deal covers a wide variety of trade issues including various copyright related subjects.

“USMCA will give our workers, farmers, ranchers and businesses a high-standard trade agreement that will result in freer markets, fairer trade and robust economic growth in our region,” US Trade Representative Robert Lighthizer and Canadian Foreign Affairs Minister Chrystia Freeland said in a joint statement.

One key change for Canada is that the country’s current copyright term will be extended by 20 years. At the moment copyrighted works are protected for the term of the author’s life, plus 50 years. This will be extended to life plus 70 years, at a minimum.

The Canadian Government has previously shown reluctance to make this change but gave in eventually.

Life +70 years

Another controversial subject that was widely debated by experts and stakeholders are ‘safe harbors.’ In the US, Internet services are shielded from copyright infringement liability under the safe harbor provisions of the DMCA, but in Mexico and Canada, that’s not the case.

The new USMCA includes a safe harbor section. This means that Internet services will be shielded from direct liability for copyright-infringing users. However, this protection doesn’t come without obligations.

The agreement specifies that ISPs should have legal incentives to work with ISPs to ensure that copyright infringements are properly dealt with.

This framework shall include “legal incentives for Internet Service Providers to cooperate with copyright owners to deter the unauthorized storage and transmission of copyrighted materials or, in the alternative, to take other action to deter the unauthorized storage and transmission of copyrighted materials,” the agreement reads.

ISPs that want to apply for safe harbor protection also have to take down pirated content and implement a repeat infringer policy, which the US already has. This means that ISPs will have to disconnect persistent pirates.

This is achieved by “adopting and reasonably implementing a policy that provides for termination in appropriate circumstances of the accounts of repeat infringers,” as the agreement prescribes.

Repeat infringer

The current text is quite vague and doesn’t define what the “appropriate circumstances” are to terminate accounts. This was also the case in the US, but after a series of lawsuits, ISPs have recently tightened their termination policies.

Crucially, the takedown and repeat infringer termination policies don’t apply to Canada. There is an annex to the agreement stating that when a country applies to various other conditions at the time of signing (including a notice and notice scheme), these do not apply.

It is clear, however, that the safe harbors will provide protection for ISPs against copyright claims. And with regard to the EU’s filtering plan, it’s worth noting that the agreement specifically states that “monitoring” or “affirmatively seeking facts indicating infringing activity” is not required.

At the time of writing the agreement has only been available for a few hours, but it’s expected that further analysis from experts will provide more context during the days to come.

While there is a final agreement, lawmakers in the three countries have yet to sign off on the new text, which isn’t a done deal yet. This means that, for now, the current NAFTA agreement remains in place.

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


Good morning/afternoon/evening/night (delete as appropriate – we’re a global community). The world has turned once more, the sun has crawled into the sky, and we’re back in the room.

Nate began the day with an update on the Foundation’s financial status: income, expenditure, bank balance, sponsorships and revenue sources. The good news is that we’re financially stable, but the bad is that we’re never going to be rich. Damn this volunteering thing, it’s almost like everyone does this for free. Oh, wait…

Next up, garbear took to the stage to talk about the upcoming (and long-anticipated!) RetroPlayer. This is already available in the 18.x “Leia” builds, so you can try it now if you like. As well as a demo to the team, the presentation covered how we’re addressing controller topology (including hubbing and mapping), user interface options, configuration, potential for user profiles, binary add-on repository structure, and some potential future features.

Martijn next took us through our current user statistics. Because we do no user tracking, it’s always been difficult to get any real numbers, so we’re reliant on partial data: Play Store active user counts, Microsoft app store figures, what we see hitting our repos for e.g. scraper or other add-on downloads. We probably have c. 80 million downloads and c. 30 million recently-active users across all platforms and versions – including some active installations on every release since 13.x “Gotham”. This presentation also led into a conversation about release management, specifically, the intended schedule for the upcoming 18.x “Leia” release plus very early timing plans for 19.x “M*”.

The next presentation was by kib, giving us an update on all things related to the Kodi infrastructure – build servers, download servers, web hosting, caching. He took us through upgrades to the Windows build system, wiki software upgrade, https implementation, the Kodi paste site, LXD containerisation, OS reinstallation and upgrades, changes to mirror up/down detection, CloudFlare, and more.

Finally, a1rwulf rounded out the day by talking about the Kodi databases: the basic architecture, current limitations, and potential changes that we need to consider as new features are introduced.

A shortened day today, with a couple of topics kicked into Sunday for a variety of reasons. Watch this space for an update on those, as we’ll add them in due course, either as an update to this post or as a separate one, depending on content.

Tags: 





Source link


With millions of visitors per week, Torrent9 is a force to be reckoned with.

The site is most popular in French-speaking countries, which hasn’t gone unnoticed to local copyright holders.

Last year, the Paris Court of First Instance ordered French ISPs to block the site. However, Torrent9 was quick to take countermeasures and moved to a new domain name.

Quite recently, it was operating from Torrent9.blue. This went fine until the site’s owner started to notice that Google traffic had tanked. The torrent site used to get roughly 20% of its visitors through the search engine, but that suddenly dropped to less than 5%.

As it turned out, the French anti-piracy outfit SACEM had sent takedown requests for hundreds of thousands of URLs in the span of a few days. Google then removed these from the search engine, adding a downranking punishment on top.

SACEM’s ‘carpet-bomb’ of takedown requests was clearly targeted and massive in scope. In one week in August, the group asked Google to remove over 350,000 torrent9.blue URLs. For comparison, The Pirate Bay usually gets a tenth of that, from all copyright holders combined.

Torrent9.blue takedowns

While we were taking a closer look at the notices in question, we spotted another peculiarity.

It almost looks like the French anti-piracy group submitted each and every URL they could find, regardless of whether it actually points to works from their music industry members.

Some URLs do indeed point to music, but there are also plenty of others, targeting movies, TV-shows, games, and software. In some cases, the torrents are not even infringing, such as the open source copy of Ubuntu listed below.

Pirated Ubuntu?

Google appears to have removed nearly all URLs including the ones that don’t point directly to copyright infringing content of SACEM members.

The removals were probably automated, but they certainly warrant a closer look. There is no question that Torrent9 offers links to pirated content, but should such broad takedown requests be permitted?

This endeavor left Torrent9 no other choice than to move to another new domain. At the time of writing the torrent site is operating from Torrent9.ph, but this could easily change again in the near future, as SACEM has already started to target the new domain with another carpet-bombing of ‘dubious’ DMCA takedown notices.

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


<blinks in the light>

What, a year already? Yup, twelve months have passed, we’re all a year older, the world is still mad, and we’re once again sitting in an overly-warm, windowless, anonymous conference room, discussing everyone’s favourite media software while wondering where the coffee is. Welcome to DevCon 2018, coming to you this year from Sofia/Со́фия, the capital city of the beautiful Balkan nation of Bulgaria.

So: Team Kodi Assemble!

We hit the ground running this morning. Mixed in with initial logistics, introductions, and the annual battle with AV and hotel wifi, keith led a conversation about github, and how we could perhaps better use it to track code and project issues. We currently use trac for bugs, which presents more than a few challenges to both casual users and the team; we could also potentially use github for bug reporting/allocation instead, and also use the associated project tracking to also keep better notes of e.g. press conversations, Foundation issues, and similar.

We continued into a conversation about conferences – which are most appropriate, how do we best cover them, what and where, how do we get most benefit. More later on this year’s conference experiences.

Martijn then talked about the move from Python 2 to Python 3: approach, milestones, timeline. Python 2 is EOL in 2020, so this is becoming a more urgent task. The intention is to combine this into the normal Kodi rolling release schedule, so expect a significant focus on Python 3 readiness and enforcement as we move past 18 (Leia) and on to 19 (M). If you’re an addon developer, specifically, then it’s time to pay attention to this as “later” is rapidly becoming “now” – everyone has had ten years to think about this, after all!

The big challenge is how we encourage developers to migrate while not inconveniencing or irritating users. This is a significant change, and some things are likely to break. Blog post here.

We next moved to conduct and standards – not because we believe there are specific problems, but more because it’s generally good practice to have some expectations regarding behaviour of team members and contributors: if you follow the news, you won’t have missed some of the headlines around what can happen when people go beyond constructive disagreement and move into personal attacks, particularly when social media or public discourse is involved. As such, we’re putting in place some clearer ground rules and management policies around our own behaviour, just as we have done around the standards we expect from our forum contributors.

The conversation then moved on to engagement and communication – how we keep people informed, updated, involved. Kodi is a big project, with very many moving parts, and nearly as many ways to interact. That’s not just about the code, but it’s Foundation stuff, user support, strategy, wiki, external conversations, release management: keeping on top of all of these is undoubtedly a challenge. This is very much an internal Team conversation, but one that we’ll continue to progress, as even orientation to the project can potentially be a barrier to new contributors.

Moving on, Martijn led a conversation around issue tracking – trac vs github. While we currently use an internal trac system, and it has some genuine benefits, it’s neither the most usable nor maintanable of systems. By contrast, hosting and managing the issues on (public) github means they’re more closely linked with code and commits, so we’d get some significant advantages there that should more than offset what we’d be missing. If we do make this change, which is likely, it won’t happen overnight, as we’ve much to decide: what to do with old (and maybe no-longer-valid) bug reports, what labelling/tagging structure we’d need, what systems we’d need to have in place to ensure that we receive “complete” reports going forward, and so on. More to come.

Related to this – because github is, in general, a more public platform than trac – we had a conversation about embracing this as a benefit and how we become more open. Again, Kodi is a hugely-complex project and is very daunting to a potential contributor: where to start? Who to talk to? How to get help? Who are all these people, anyway?? So, many thoughts: github conversations, GSoC experiences, public discussion channels, updated build/”getting started” documentation, code documentation/architecture. If you’re a potential developer and feel like you don’t know where to begin, please, contact a member of the team to help us address any concerns you have. We can always use some more help, particularly on the features and multiple platform support that everyone values so much.

Returning to a topic introduced earlier in the day, garbear, Razze and yol took the floor to report back on their attendance at VDD (Video Dev Days) earlier this month (also attended by Martijn and RomanVM). This was also touched on in a previous blog post. Sessions included AV1 CODEC development, including the dav1d decoder and rav1e encoder;  the x265 HEVC encoder; VLC 4.0 plans and features; a series of short “lightning talks” on various AV-related topics; and, of course, many networking opportunities across a common community of interest (website hosting and load balancing, request handling/download management, breakouts on FFMpeg, programming languages…). Useful bridges built with like-minded people, which is ultimately good for the whole open source multimedia landscape.

As the day started to draw to a close, mohit-0212, one of our 2018 GSoC students, gave a presentation on his project around episode intro/outro detection. The goal of this project is to improve the user experience by editing out the endless theme tunes and credits you get, particularly when binge-watching a box set. This involves searching for common scene transition points across multiple episodes of a series, and using hashing algorithms on the video stream to work out when the likely sections begin and end. In the first implementation, then, the detection is run and then the user is presented with a “skip” button as a the section begins. Fully-automated skipping would perhaps be a later addition, but more work is needed yet on the code, detection of “edge cases”, and UI, and similar.

Finally, natethomas and the other Foundation board members spent some time talking about the board responsibilities: who, what, how, why. The XBMC Foundation has a legal status, and thus there are ongoing administrative, legal and financial activities around our overall direction as a project, non-profit status, trademarks, incorporation status, revenues from sponsorship and donations, approval of expenditure, taxes, PR/press, GSoC admin, Foundation membership and bylaws, internal policies, and any formal legal communications as required.

And that’s it for day one. Time to head out into the fading evening light before reconvening in the morning.

Tags: 





Source link