Half-baked Piracy Solution!
#1
This is probably a stupid and impractical idea, but could Kodi nobble the streaming pirates through a universal update which disables all add-ons that don't come from the official repository? Though with the option to switch everything back on via SSH and the command line. No switch via the GUI.

It'll still be FOSS and without restrictions, but you'll just have to make a little effort to get your illegal streams. Likely enough of a bother to discourage 99% of those who are using Kodi boxes.

Thomas
Reply
#2
That would work with libreelec and OSMC, without those, Kodi is ‘just’ a media player, so there would be no way to do this, also if it were possible, someone could easily fork the project, then remove the restriction.
Server: Ubuntu Server 22TB HDD running SAMBA
Kodi: 4 Raspberry Pi 3 running Libreelec -  on the main PC - running Linux Mint
My Setup thread |
Reply
#3
(2018-03-02, 00:06)tjay260476 Wrote: That would work with libreelec and OSMC, without those, Kodi is ‘just’ a media player, so there would be no way to do this, also if it were possible, someone could easily fork the project, then remove the restriction.
 Not to mention, with the sheer number of individuals who don't even seem to know that this website is NOT the source of their Kodi build full of broken pirate addons, we can safely assume that the majority of those do not simply download Kodi from this site and then install the pirate addons on their own but instead use third party built 'all in one' solutions for their platform of choice.
Reply
#4
Not to mention that not everything from a non official repo is necessarily a piracy addon.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply
#5
I'm not sure changing the equivalent slider for unknown sources to the command line would make any difference to be honest

This type of subject comes up regularly here, and I discussed it a while ago.  It isn't going to change as the devs dont want to restrict the user to use the software as they see fit
Reply
#6
OK, what about a time machine so the devs can stop themselves from releasing Kodi for Android? How hard could that be?

I'd be happy to volunteer to be the time travelling assassin / counsellor. Would anyone care to accompany me as the quirky assistant / comic relief?
Reply
#7
If that were possible, then the likely thing would happen is the issue would migrate to the Raspberry Pi...... as its the next easiest candidate for box sellers.
Server: Ubuntu Server 22TB HDD running SAMBA
Kodi: 4 Raspberry Pi 3 running Libreelec -  on the main PC - running Linux Mint
My Setup thread |
Reply
#8
Blimey, all that leaves is destroying capitalism and creating a socialist utopia.

Would any one care to accompany me in leading the revolution? Position includes free custard.
Reply
#9
Free custard? I’m in!
Server: Ubuntu Server 22TB HDD running SAMBA
Kodi: 4 Raspberry Pi 3 running Libreelec -  on the main PC - running Linux Mint
My Setup thread |
Reply
#10
Any fish fingers?

On a more serious note, yes the team do not want to dictate how users actually use Kodi, as part of the FOSS principles that the project works under.

However what we do want is users to be making an informed decision, that if they choose the use of banned addons (wiki) then it's a conscious decision, knowing what they are, where the media comes from, who wrote (and supports) those add-ons, what the potential consequences are of their use and who is liable/included with regard to those consequences. This is where things tend to fall down, as of course all the crap peddlers of the 3rd party junk either don't give the users any choice (via pre-installed add-ons or the use of splattergun builds which hide all manner of addons and other potential nasties like cryptocoin mining scripts and who knows what else) and somehow curiously fail to state that the junk is not any part of the official Kodi release nor is something that we support or are responsible for.

If we could somehow magically wave a wand and resolve that last information part then the whole team would have a much happier outlook (and the garbage forum here wouldn't be half as regularly used as it is now).
|Banned add-ons (wiki)|Forum rules (wiki)|VPN policy (wiki)|First time user (wiki)|FAQs (wiki) Troubleshooting (wiki)|Add-ons (wiki)|Free content (wiki)|Debug Log (wiki)|

Kodi Blog Posts
Reply
#11
Fish fingers and custard? mmmmmmmmmmmmmmmm.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply
#12
Seems to go against the theme of Kodi.
I like how it is right now.
Reply
#13
(2018-03-02, 00:06)tjay260476 Wrote: someone could easily fork the project, then remove the restriction.
  
This would violate the trademark and if XBMC fights against such abuses, the fork would get its own name and by that its a perfect way to repudiate from them, so finally Kodi is not dragged through the mud anymore. And that should be the main target.

So an official database should be used, a blacklist for illegal add-on names and a DNS filter list for illegal sources. After that the forks will start in seconds and then there should be no need to update those lists anymore.
Reply

Logout Mark Read Team Forum Stats Members Help
Half-baked Piracy Solution!0