The LibreELEC 9.0 Alpha cycle has continued and releases for Amlogic and Slice hardware have been added additionally to the test cycle. We official support now Khadas VIM (AML S905X) and the LePotato (AML S905X) too. Since the 8.90.006 release we support a wide range of Rockchip devices. There are no plans to release LibreELEC 9.0 images for NXP/iMX6 hardware as support was removed from Kodi some months ago. Support will be reinstated in a future LibreELEC, we wrote an dedicated article about the future of LibreELEC.

Alpha releases are important to the team because we cannot test every scenario and sometimes sidestep issues without realising. The project needs a body of regular testers to go find the problems we miss. Testing will be particularly important for LibreELEC 9.0 as Kodi v18 includes substantial internal changes to VideoPlayer and introduces new retro-gaming capabilities.

** ROCKCHIP **

We added several Rockchip devices at this release. Please consider it as alpha quality and not yet as perfect. All kind of flavors of HDR, 4k and audio are supported already. These images are rather new and it is likely that you hit an problem sooner or later. Please report them at our issue tracker or at the dedicated Rockchip forum that they could get fixed. Within the LE9 release cycle we are likely not able to finish the Rockchip devices to reach an perfect stable state – they stay in alpha status as long it is needed.

TEST NOTES

Our current focus is the OS core and we are more interested in hardware and driver bugs than Kodi problems. Please report the issues you find by starting a thread in the forums or use our bug tracker. Raspberry Pi users are reminded that dtoverlay=lirc-rpi has now been deprecated. Please read the infrared remotes wiki page  before updating.

** CAUTION **

Alpha builds exist for hands-on testing not a hands-off experience. If you run Alpha builds you must be willing to report issues and engage the LibreELEC and Kodi developers in hunting bugs. If you have no idea what a debug log is or “wife acceptance factor” is critical, these builds are not for you. If you want to run Alpha builds please make a backup and store it somewhere off-box first. Your failure to make a backup is not our problem.

Updates since v8.90.005 ALPHA:

– updated to Kodi 18 Beta 3
– Kernel updated to 4.18.11 for Generic, RPi and Slice
– added Rockchip RK3328, RK3399 and RK3288 Devices
– a lot more updates and fixes, have a look at the full changelog

LibreELEC 9.0 Alpha 006 (Kodi 18 Beta 3)

To update an existing installation from within the Kodi GUI select manual update in the LibreELEC settings add-on and then check for updates; select the LibreELEC 9.0 channel and then the 8.90.006 release. To create new install media please use our simple USB/SD Creator App. The following .img.gz files can also be used to create install media or update the old fashioned way:

RPi 2/3 LibreELEC-RPi2.arm-8.90.006.img.gz (info)

RPi 0/1 LibreELEC-RPi.arm-8.90.006.img.gz (info)

Generic LibreELEC-Generic.x86_64-8.90.006.img.gz (info)

Odroid_C2 LibreELEC-Odroid_C2.arm-8.90.006.img.gz (info)

KVIM LibreELEC-KVIM.arm-8.90.006.img.gz (info)

LePotato LibreELEC-LePotato.arm-8.90.006.img.gz (info)

Slice LibreELEC-Slice.arm-8.90.006.img.gz (info)

Slice3 LibreELEC-Slice3.arm-8.90.006.img.gz (info)

WeTek_Core LibreELEC-WeTek_Core.arm-8.90.006.img.gz (info)

WeTek_Hub LibreELEC-WeTek_Hub.arm-8.90.006.img.gz (info)

WeTek_Play LibreELEC-WeTek_Play.arm-8.90.006.img.gz (info)

WeTek_Play_2 LibreELEC-WeTek_Play_2.arm-8.90.006.img.gz (info)


RK3328

Firefly ROC-RK3328-CC LibreELEC-RK3328.arm-8.90.006-roc-cc.img.gz (info)

Generic Rockchip Box LibreELEC-RK3328.arm-8.90.006-box.img.gz (info)

PINE64 ROCK64 / Popcorn Hour Transformer LibreELEC-RK3328.arm-8.90.006-rock64.img.gz (info)

Popcorn Hour RockBox LibreELEC-RK3328.arm-8.90.006-rockbox.img.gz (info)

MVR9 LibreELEC-RK3328.arm-8.90.006-box-trn9.img.gz (info)

Z28 LibreELEC-RK3328.arm-8.90.006-box-z28.img.gz (info)

RK3399

96rocks ROCK960 LibreELEC-RK3399.arm-8.90.006-rock960.img.gz (info)

PINE64 RockPro64 LibreELEC-RK3399.arm-8.90.006-rockpro64.img.gz (info)

Rockchip Sapphire Board LibreELEC-RK3399.arm-8.90.006-sapphire.img.gz (info)


RK3288

ASUS Tinker Board LibreELEC-TinkerBoard.arm-8.90.006-rk3288.img.gz (info)

mqmaker MiQi LibreELEC-MiQi.arm-8.90.006-rk3288.img.gz (info)



Source link


With file-sharers manually acquiring increasingly large libraries of content, several years ago it became clear that software to automate the process would prove popular with the masses.

One such tool was Sick Beard, a PVR-like piece of software that was able to utilize Usenet providers, indexers, and TheTVDB to identify airing dates for TV shows and automatically download whenever they became available online. It would then add the content to a user’s library ready for viewing.

Like many successful open projects, Sick Beard later found itself ‘forked’, with developers breathing life into SickRage, a GNU General Public Licensed tool that took Sick Beard’s dreams and ran with them. With improved Usenet and torrent support plus a whole raft of new features, SickRage gained an impressive following.

SickRage in action

Unfortunately, however, SickRage began to suffer problems common to many projects where not every developer is an agreement on every point of action. This led to fragmentation, with devs moving to work on other similar projects. One of those who departed was a dev known as Echel0n, who started up his own SickRage variant operating from SickRage.ca.

In July 2017, things appeared to boil over when Echel0n (later self-identified as ‘Justin Tabish’) filed a DMCA complaint with Github, claiming copyright over the SickRage code.

“SiCKRAGE and the original code has not been provided or its use authorized, this is a violation of my copyright. I have a good faith belief the distribution of SiCKRAGE includes content of which the distribution is not authorized by the copyright owner, it’s [sic] agent, or the law,” the complaint reads.

Just days later, SickRage fought back, filing a counter-notice with Github. Perhaps unsurprisingly given the various contributors to long-standing open projects, the counter-notice points out a number of issues with the original DMCA notice.

Disputing all of its claims, the counter-notice states that the original SickRage copyright holder (@midgetspy) endorsed adding his name to the license and adding the counter-notice filer’s name “underneath his as credit for later contributions as per convention.” It also states that ‘Echel0n’ has no standing to make a complaint.

“As such, all other claims are disputed for this DMCA. We are in compliance with all applicable law to the best of our knowledge. Very little if any code is shared among these forks, however if complainant would like a prior credit added that would be amenable,” the notice adds.

With that, Gihub reinstated the project and for some time it appeared that an uneasy peace had broken out. It now transpires, however, that Echel0n (Tabish) was just getting warmed up.

As the image below shows, in September the developer registered the trademark ‘SickRage’ in the US with the United States Trademark and Patents Office (USPTO).

SickRage trademark filing

Armed with this piece of paper, Justin Tabish fired off a complaint to developer Dustyn Gibson (aka ‘miigotu‘) of the SickRage project, warning him to cease and desist using the SickRage trademark, even though it doesn’t appear to have been awarded yet.

Cease and Desist

Tabish also wrote to Github, demanding that the site transfer ownership of the SickRage repository to him.

“I’d like to report a case of trademark infringement and am requesting transfer of ownership for the following organization to my control so that I can remedy the situation, the organization is https://github.com/sickrage and is owned/controlled by username Miigotu, user’s profile is located at https://github.com/miigotu,” he told the company.

“This repo also has a website located at https://sickrage.github.io. This user/repo is a ex-team member of mine that I let go awhile back, they and others decided to open a repo on you’re servers under the exact same name of my company and project causing confusion and misleading members, as you can see in the title of the repo they have placed ‘The new home of the SickRage community’ which leads others to think there was some sort of change of ownership.”

Describing the effort as a “hostile takeover” attempt, ‘miigotu’ posted a note to the official Github account promising to fight every inch of the way.

“I will have to fight this again, he is claiming his ‘company’ owns a trademark to the name SickRage. This is a joke and I will fight it tooth and nail,” miigotu writes.

“Just another attempt by the drug addict to try and claim he owns the work that we all did on this project. He abandoned the project and we made it what it is. Then he popped up 2 years later and removed the entire team. If I have to take him to court, that will happen.”

There’s now a pretty huge argument taking place on Github as to who is right and wrong, and who is infringing on various rights. It’s a minefield of opinions that’s best read directly to be understood. Needless to say, it’s very messy indeed.

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


Since its official launch in 2013, the PlayStation 4 (PS4) remained piracy-free for a long time, but last year things started to shift.

Following the release of a new jailbreak version a few months ago, things took a turn for the worse for Sony. This allowed the masses to tinker with their PS4 consoles which only increased the piracy troubles.

While it will be hard for Sony to put the genie back in the bottle, the Japanese company has decided to take a stand. In a new case filed at a federal court in California, Sony details its complaint against a local resident who allegedly offered for sale jailbroken PS4s filled with pirated games.

According to Sony, defendant Eric Scales was using the handle “Blackcloak13” to sell the jailbroken PS4s preloaded with over 60 pirated games on eBay.

“Defendant is an individual who has marketed, sold, and distributed ‘jailbroken’ PS4 consoles that: (a) contain ‘pirated’ (unauthorized) copies of PS4-compatible video games, and (b) were produced and designed for purposes of, and/or were marketed by Defendant for use in, circumventing technological protection measures,” the complaint reads.

One eBay listing

Sony ordered two devices online and found that they were indeed ‘as advertised.’ The PS4s were modified to run an unnamed exploit which effectively circumvents the technological protection measures that normally prevent people from playing pirated games.

“The exploit enables the PS4 console sold by Defendant to play the 60+ unauthorized copies of video games that are contained on its hard drive,” Sony writes.

In addition to the eBay shop, the man is also accused of running a separate website (now offline) where he advertised his services and products. The website stated that he’s been jailbreaking and modding consoles since 2006, and encouraged people to “stop buying games.”

“On Defendant’s website, where he uses the traditional ‘pirate’ symbol of a skull and crossbones shown below, Defendant states that purchasing his services or products will enable the purchaser to ‘be able to Download and copy any game’ and to ‘STOP BUYING GAMES’,” Sony notes.

STOP BUYING GAMES

With its lawsuit, Sony hopes to obtain an injunction ordering the defendant to stop any infringing activity and to destroy all jailbroken or “modded” PS4 consoles, hard drives, and games.

In addition, the game company requests damages for copyright infringement and for violating the DMCA by circumventing the PS4’s technological protection measures.

To our knowledge, this is the first jailbroken PS4 lawsuit, and it’s likely that Sony wants to set a clear example. With several first-party PS4 games being mentioned in the lawsuit, the potential damages run to hundreds of thousands of dollars.

A copy of the full complaint, obtained by TorrentFreak, 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


Well over six years have passed since Megaupload was shut down and it’s still unclear how the criminal proceedings will unfold.

Aside from Andrus Nomm’s plea deal, progress in the criminal proceedings has been slow.

Kim Dotcom and his former colleagues are currently fighting a legal battle in New Zealand to prevent their extradition to the US, for which the final decision has yet to be issued.

While all parties await the outcome, the criminal case in the United States remains pending. The same goes for the civil cases launched by the MPAA and RIAA in 2014, more than four years ago.

Since the civil cases may influence the criminal proceedings, Megaupload’s legal team previously managed to put these cases on hold, and last week they requested another extension.

This is not the first time that such a request had been made. There have been several extensions already, which caused some issues.

There were previously concerns that the long delays could result in the destruction of evidence, as some of Megaupload’s hard drives were starting to fail. However, after the parties agreed on a solution to back-up and restore the files, this is no longer an issue.

“With the preservation order in place, and there being no other objection, Defendant Megaupload hereby moves the Court to enter the attached proposed order, continuing the stay in this case for an additional six months,” Megaupload’s legal team informed the court this week.

Without any objections from the MPAA and RIAA, U.S. District Court Judge Liam O’Grady swiftly granted Megaupload’s request to stay both lawsuits until April next year.

And so that wait continues…

Order to stay

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


Four years ago, Singapore became the latest in a long line of countries to use copyright law to block access to ‘pirate’ sites. The amendments were passed during the summer of 2014 and took effect in December the same year.

After a break of almost two years, a request by the MPA(A) rendered Solarmovie.ph inaccessible in 2016. Several major ISPs were ordered by the High Court to block the streaming platform, the first such action in the country.

In April this year the MPA(A) chalked up another victory when its application to have 53 sites operating across 154 domains – including those operated by variants of The Pirate Bay and KickassTorrents – was granted by the High Court. ISPs including Singtel, StarHub, M1, MyRepublic and ViewQwest blocked the sites shortly after.

The blocking process in Singapore appears to be thorough. The High Court must be satisfied that sites targeted are “flagrantly infringing”, i.e with a primary purpose of breaching copyright and generally showing a lack of respect for copyright law. Site operators are also able to defend themselves although thus far, none have done so.

With plenty of experience of sites around the world taking evasive counter-measures to avoid blocking, the injunction in Singapore allowed copyright holders to return to Court to request an amended order to block new domains and/or IP addresses. However, this model has proven cumbersome in the past so it’s no surprise the MPA(A) has now persuaded the Court to adopt a more streamlined approach.

After highlighting that several of the blocked sites changed their domains to avoid blocking, the High Court has now handed down a “dynamic injunction” which will allow the Hollywood studios to block any new methods deployed by the 53 sites covered by the earlier injunction.

“Without a continuing obligation to block additional domain names, URLs and/or IP addresses upon being informed of such sites, it is unlikely that there would be effective disabling of access to the 53 (infringing websites),” said Justice Lee Seiu Kin, as quoted by TodayOnline.

Under the terms of the new order, companies including Disney, Paramount Pictures and Twentieth Century Fox, will be able to liaise with ISPs M1, MyRepublic, Singtel, StarHub and ViewQwest to have additional domains and IP addresses blocked, if they facilitate access to the previously blocked sites.

According to Justice Lee, the new injunction “provides a practical means of ensuring the continued effectiveness of the original injunction since it provides an expedited process for the blocking of additional (piracy websites).”

The Judge added that ISPs will only have to block the new resources if they are satisfied there is enough evidence to do so but according to TodayOnline, this was highlighted as potentially problematic by local lawyers.

“It is questionable if this is a good enough safeguard when the most expeditious way for an Internet service provider to respond, upon receipt of a request to block an additional domain name, would simply be to comply with the request, rather than to incur the time and cost of disputing the matter with the copyright owner,” said representatives from the Bird & Bird law firm.

Nevertheless, the judgment was welcomed by Neil Gane, general manager of the Asia Video Industry Association’s Coalition Against Piracy.

“There is no one silver bullet to deterring online piracy,” Gane said. “What is required is a holistic solution to include enforcement; disabling access to egregious piracy websites through effective site blocking; cooperation with technology platforms and other intermediaries; and consumer outreach.”

According to a report published by the Motion Picture Association Canada earlier this year, at least 42 countries are now obligated to block infringing sites. In Europe alone, 1,800 sites and 5,300 domains have been rendered inaccessible, with Portugal, Italy, the UK, and Denmark leading the way.

In Canada this week, site-blocking efforts suffered a setback when local telecoms regulator CRTC denied FairPlay Canada’s application for a broad pirate site blocking scheme. CRTC cited a lack of jurisdiction under the Telecommunications Act.

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


When CD copying was all the rage in the late 1990s, many countries started to levy a tax on blank media.

This meant that consumers had to pay an extra fee on every recordable disc, because these can be used to duplicate copyrighted content.

In some countries, this model has expanded to other media, such as hard disks, MP3 players and phones. In Canada, however, this didn’t happen. Despite several attempts in the past, there is no private copying levy on smartphones, tablets or hard disks.

During recent copyright reform discussions, the matter was brought to the forefront once again. But there’s also another copyright compensation issue, one that’s potentially even more controversial.

A proposal from the Screen Composers Guild of Canada (SCGC), put forward during last week’s Government hearings, suggests to simply add a levy on Internet use above 15 gigabytes per month.

The music composers argue that this is warranted because composers miss out on public performance royalties. One of the reasons for this is that online streaming services are not paying as much as terrestrial broadcasters.

The composers SCGC represents are not the big music stars. They are the people who write music for TV-shows and other broadcasts. Increasingly these are also shown on streaming services where the compensation is, apparently, much lower.

“With regard to YouTube, which is owned by the advertising company Alphabet-Google, minuscule revenue distribution is being reported by our members. Royalties from the large streaming services, like Amazon and Netflix, are 50 to 95% lower when compared to those from terrestrial broadcasters,” SCGC writes (pdf).

“Statistics like this indicate that our veteran members will soon have to seek employment elsewhere and young screen-composers will have little hope of sustaining a livelihood,” the guild adds, sounding the alarm bell.

SCGC’s solution to this problem is to make every Canadian pay an extra fee when they use over 15 gigabytes of data per month. This money would then be used to compensate composers and fix the so-called ‘value gap’.

As a result, all Internet users who go over the cap will have to pay more. Even those who don’t watch any of the programs where the music is used.

However, SCGC doesn’t see the problem and believes that 15 gigabytes are enough. People who want to avoid paying can still use email and share photos, they argue. Those who go over the cap are likely streaming not properly compensated videos.

“An ISP subscription levy that would provide a minimum or provide a basic 15 gigabytes of data per Canadian household a month that would be unlevied. Lots of room for households to be able to do Internet transactions, business, share photos, download a few things, emails, no problem,” SCGC notes.

“[W]hen you’re downloading and consuming over 15 gigabytes of data a month, you’re likely streaming Spotify. You’re likely streaming YouTube. You’re likely streaming Netflix. So we think because the FANG companies will not give us access to the numbers that they have, we have to apply a broad-based levy. They’re forcing us to.”

The last comment is telling. The composers guild believes that a levy is the only option because Netflix, YouTube, and others are not paying their fair share.

That sounds like a licensing or rights issue between these services and the authors. Dragging millions of Canadians into this dispute seems questionable, especially when many people have absolutely nothing to do with it.

According to Canadian law professor Michael Geist, who highlighted the issue, it would also result in an unfair double-payment.

“[T]he SCGC proposal would represent double-payment by consumers, who would pay to access the content on services such as Spotify and Netflix and pay for the transmission of the same content with the ill-advised copyright tax on broadband data,” Geist writes.

It’s doubtful that there will be broad support for the proposal among the public. However, proposing to add a levy or tax on Internet use certainly gets people’s attention, which might have been part of the plan.

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


At the start of this year pirate streaming site 123movies was one of the largest pirate streaming sites on the web.

The site received millions of visitors per day which prompted none other than the MPAA to label it “the most popular illegal site in the world.”

For Hollywood, the blatantly infringing activity was a thorn in their side, so behind the scenes the movie studios did all they could to take the site offline, helped by US authorities.

In 2017, the US Ambassador to Vietnam called on the local Government to criminally prosecute the site’s operators on their alleged home turf. In addition, the site was also on the radar of the office of the US Trade Representative, which featured 123movies in its latest Notorious Markets report.

March this year, the MPAA sent its own people to Vietnam to expedite the issue. The movie industry group teamed up with the local Office of the Police Investigation Agency, hoping that this would lead to the downfall of the streaming site.

A few days later, 123movies shut down.

“Now it’s time to say goodbye. Thank you for being our friends and thanks for staying with us that long,” the 123movies team wrote, asking users to “respect” filmmakers by paying for movies and TV-shows instead of pirating them.

There was never an official explanation for this radical decision but it wasn’t hard to figure out that the ground had become too hot for the operators. Movie industry pressure was mounting and Vietnam also appeared to get more strict on copyright enforcement issues.

While 123movies never elaborated on its reason to shut down, the MPAA has now provided some more insight. In its latest list of “notorious markets” sent to the US Government this week, the group links it to a criminal investigation.

“An important development in 2018 was the shuttering of a ring of piracy services that had operated under the names 123movies, 123movieshub, gostream, and gomovies following the launch of a criminal investigation in Vietnam and significant industry engagement,” MPAA writes.

MPAA on 123movies’ demise.

TorrentFreak asked the MPAA whether this investigation resulted in any arrests, charges, or if it’s still ongoing. We are yet to receive a response.

It’s clear though, that the mounting pressure resulted in 123movies being shut down. This is arguably one of the major anti-piracy successes of the year so far, but the problem isn’t over yet.

Following the demise of 123movies, several clones and copies stepped up to take its place. However, the MPAA says that it has these on its radar as well.

“Since its closure, many copycat sites have emerged. This ring of piracy services had been blocked in at least eight countries prior to its shut down and efforts are underway to shut down the copycats as well,” the MPAA notes.

This is not a veiled threat, it appears. Last month, the biggest clone 123movieshub.sc suddenly went offline as well, as the site’s domain was deactivated by the domain name registry. As expected, other 123movies clones were quick to take over the top spot.

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


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