-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Peertube #147
Comments
Good point, thank @jibe-b |
I will! |
Rather that trying to curate URLs, using the embed library allows to decouple your implementation from the evolving PeerTube platform, so I'd advise you first try that. |
The main challenge for this is that we can't detect that a video is from Peertube just by looking at its URL. There can also be many Peertube links for the same video, which doesn't work well with our current data model. That being said, I'd love to see this happen one day. |
Hello, You can detect a peertube instance using the nodeinfo endpoint: Then, the origin video URL can be found using the REST API: https://peertube2.cpy.re/api/v1/videos/d6210593-dbb8-49a0-b4a8-72f03fc550eb ( |
Nice, thank you @Chocobozzz! |
User story
PeerTube is a decentralized videos platform. Having CaptainFacts supporting PeerTube instances would be a plus.
Best solution for this problem
The code of PeerTube is free and open source which should ease the path until the support.
The challenge is that a video does not necessarily have one unique URL. It may be replicated in more than one instance. Hence a need to curate URLs of a unique video.
This feature is not urgent ;)
The text was updated successfully, but these errors were encountered: