search

iBicha / playlet

The unofficial, privacy driven, YouTube client for Roku
GNU Affero General Public License v3.0
327 stars 12 forks source link

Support for Piped? #75

Open FireMasterK opened 1 year ago

FireMasterK commented 1 year ago

Hi there,

Author of Piped here! :wave:

I came across this project, and thought it's really nice to see a privacy-friendly YouTube on Roku!

I was wondering if it would be out of scope to add support for Piped's API?

Just like Invidious, Piped is another alternative privacy-friendly frontend for YouTube.

We also support unauthenticated subscriptions, a feature to have subscriptions without an account on Piped, a feature that Invidious doesn't have to improve privacy further.

Unfortunately, I have no prior knowledge of BrightScript nor own a Roku. But I'd be willing to learn enough to be able to add support for Piped for those who want to use playjet with Piped.

Let me know your thoughts! Thanks!

iBicha commented 1 year ago

Piped API support looks like a great addition to Playlet! In fact I was not aware that there are two different teams (TeamPiped and TeamNewPipe) I had testing NewLeaf on my radar, but I was not aware of Piped API.

I personally think it's a good idea for Playlet to support multiple APIs. Sometimes the feature parity is not perfect, and sometimes breakage that happens because of Youtube changes does not affect everyone (since extractors are similar but not exactly the same) so having options that makes sure non-tech savy users are not affected is a plus as well.

Similar to Invidious, I see that there are publicly hosted instances of Piped, which is great for people to try it out (or people who do not know how to host) this makes it even better.

But looking at https://docs.piped.video/docs/api-documentation/, it seems to be that the API docs are not complete? I'll take a deeper look at it, but for now I'll add this to the roadmap!

Thanks for your suggestion

FireMasterK commented 1 year ago

I'm actually a member of both TeamPiped and TeamNewPipe. In Piped, we use NewPipeExtractor in the backend which is also used by the NewPipe application.

We currently lack documentation on the API, and the current documentation is going to be replaced by a new OpenAPI specification when its fully complete. Haven't really gotten time to work on that, but will prioritize it going further. In the meanwhile, I think this could be of some help :)

We have an API to see all the available instances at https://piped-instances.kavin.rocks/

iBicha commented 1 year ago

That's a good idea, open api specs can really keep docs up to date if they are the source of truth Might work on adding BrightScript to https://github.com/OpenAPITools/openapi-generator, that way the integration can be simpler