Newpipe: IDEA support decentral video platforms

Created on 29 May 2018  路  6Comments  路  Source: TeamNewPipe/NewPipe

I see some mutual long-term benefit opportunity by providing some support or
easy integration possibilities to these platform (since those users could need a nice client too):

these all are different, so for sure, there must be some thoughts,
which platform architecture can be supported, etc...

enhancement multiservice peertube

Most helpful comment

  • For PeerTube support see #1349 and TeamNewPipe/NewPipeExtractor#79
  • For DTube support see #1137

Before we can add them to the frontend, someone needs to add support for the services in the extractor. @theScrabi Is writing a documentation to make it easier for other developers to add a new service.
The overall plan was to add more services by version 2.0. Nevertheless, if someone is interested to implement this, we'd appreciate it :)

@theScrabi We once discussed guidelines for new services and how to handle service requests. Maybe we should open one ticket for all requests and with the inclusion criteria and a link to the documentation in the description. Otherwise we'll just get a bunch of duplicates.

All 6 comments

  • For PeerTube support see #1349 and TeamNewPipe/NewPipeExtractor#79
  • For DTube support see #1137

Before we can add them to the frontend, someone needs to add support for the services in the extractor. @theScrabi Is writing a documentation to make it easier for other developers to add a new service.
The overall plan was to add more services by version 2.0. Nevertheless, if someone is interested to implement this, we'd appreciate it :)

@theScrabi We once discussed guidelines for new services and how to handle service requests. Maybe we should open one ticket for all requests and with the inclusion criteria and a link to the documentation in the description. Otherwise we'll just get a bunch of duplicates.

@theScrabi We once discussed guidelines for new services and how to handle service requests. Maybe we should open one ticket for all requests and with the inclusion criteria and a link to the documentation in the description. Otherwise we'll just get a bunch of duplicates.

Yes you are right. We can put a link to the inclusion criteria in the contribution note. Maybe also in the FAQ what do you thing?

However as you said these guidelines are not final.

We can put a link to the inclusion criteria in the contribution note.

That sounds like a good idea.

I once made a draft for our website which included some information about multi service support.
For now, I think it is enough to leave a short note in the FAQ, but once we have proper support for at least three services, I am going to put some (better designed) information on the main page.

There is no P2P or Decentralized App in the Normal-Browser-Web

The thing is none of these plattforms are p2p decentralized. The most of them are simply peer2gateway2peer decentralized and/or self hosted. So these Projects have not realy something to do p2p decentralisation.

And DTube is the worst, they use steemit and steemit simply claim that they got a blockchain. Which could be true but also could not be true. They simply hide everything behind a none normed RCP API and a Asksteemit api that is maybe a better gateway for the client frontend.

For Storage DTube using IPFS which is the only way to do p2p storage. But they seem to only host relevant data, which is defined by the ipfs node provider. And if you do not run a IPFS gateway localy on you pc you access IPFS via a gateway from the internet. So even this ends up in users think they using p2p and decentralized systems and they basically do not use a decentralized or p2p system.

Also HTTP is design by centralized Companys like Google and Facebook. And they got special interessed in not have decentralized web, because it is their buisness.

Strict HTTP Security Headers basically destory every possibility of get the web p2p and decentralized. Because every Application that is decentralized or p2p needs a now to send rules to the next client that they need to follow caused by they browser restrictions. This can help against injecting scripts, but in the most cases fails and break a lot of old web apps.

Also HTTP and the Browsers where never designed to be used as p2p or decentralized sandbox. It is simply impossible to do this in Browsers.

Even DNS is a Centralized System. The most servers are hosted by Companys. The most of them also get rules to ban domains for a couple of reasons.

Also RSA is Centralized, why?, because we need pre installed public keys on our systems to not got in the problem that STARTTLS have. Without this we would need handshakes, that can someone simple view and abuse.

So any question about decentralized and p2p applications in the web ? :D

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

cool-student picture cool-student  路  3Comments

PanderMusubi picture PanderMusubi  路  3Comments

danialbehzadi picture danialbehzadi  路  3Comments

Aevann picture Aevann  路  3Comments

cavemandaveman picture cavemandaveman  路  3Comments