Test PeerTube REST API with the <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/api-rest-getting-started">getting started guide</a>
Control the PeerTube player embed using the <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/api-embed-player">embed API</a>
Develop plugins and themes using the <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/contribute-plugins">getting started guide</a>
Get help on <a target="_blank" rel="noopener noreferrer" href="https://framacolibri.org/c/peertube">PeerTube forum</a> or ask new plugin/theme API in <a target="_blank" rel="noopener noreferrer" href="https://github.com/Chocobozzz/PeerTube">PeerTube issues</a>
PeerTube uses ActivityPub because this federation protocol is recommended by the W3C and is also used by other projects like the social network <a target="_blank" rel="noopener noreferrer" href="https://joinmastodon.org/">Mastodon</a>.
IPFS is a great technology, but it still seems too young for streaming large files. The PeerTube P2P system based on well established protocols like HTTP and WebRTC, and the <a target="_blank" rel="noopener noreferrer" href="https://docs.joinpeertube.org/admin-following-instances?id=instances-redundancy">redundancy system</a> are more easy for us to use and to maintain.