Rigel Kent

@tilllt please read [our note in the FAQ](https://github.com/Chocobozzz/PeerTube/blob/develop/FAQ.md#are-you-going-to-support-advertisements). TLDR': it is better to write plugins (since we have a plugin API that allows such things).

> Ideally the instance administrator would limit the classic upload for each user but eventually let users upload videos by specify an IPFS address. I guess when a user […]...

@alxlg we're not even close to writing a Desktop client. This is a non-option considered our resources. I was considering leaving the video uploaded without transcoding, thus leaving a single...

@alxlg using an IPFS address or a *.torrent file yields the same import capabilities. See #102. The only advantage of IPFS I see is that there are pinning brokers. (For...

@Openmedianetwork this has nothing to do with IPFS. Please find a related issue and detail your problem there, not in a blog post.

> Server uploads to IPFS and stores hashes of videos > > This phase has the potential of requiring double the disk space since the files will be stored on...

> This is not a proposal to force users to use IPFS, merely to give users the option. Right now they have the opportunity to use HTTP or webtorrent. This...

Since it's a auto import, we can assume videos previously imported have the same title as on YT. We could just check against titles for a first implementation.

Ah, right :/ I guess it's not a problem to add this metadata, since it's something that doesn't need to be federated (meaning we don't break things if we add...

A simpler way to implement is for clients to transcode first and then let the server decide if the video is properly transcoded. But adding workers is another level of...