#41 Playlists are recreated when they already exist

After tests, this is a Peertube bug, see to bug report in the first post about that.

A workaround exist, but need to edit manually the server component of Peertube.

For the moment, no solution, but we may have to modify prismedia once the Peertube bug is solved, perhaps to add some option to the API.

According to the last answer of the Peertube bug by Rigelk: https://github.com/Chocobozzz/PeerTube/issues/2138#issuecomment-569037287

There is now a search function in the API that we could use instead of retrieving the list as we currently do. (retrieving the list still returns 14 last playlists)

I reopen to take time to work on it!

As notified by @Zykino, the function we currently use accept parameters to iterage on pagination, eg adding count=1&start=16

As it also returns the total number of playlist, we may use it to find the correct playlist if needed, but be careful as it may have lot of playlist :-/

According to the documentation the max count allowed by peertube is 100

If you try more than 100 (eg: 101), it returns an error:

{'errors': {'count': {'value': '101', 'msg': 'Should have a number count (max: 100)', 'param': 'count', 'location': 'query'}}}
2020-11-11 09:57:03,671 - Prismedia - ERROR: Peertube: 'data'

But, if we have less than 100 and pass count=100, it works.

So we may mitigate the bug by requesting 100 directly. Problem will occurs when a user have more than 100 playlists ^^"

For this case, we have to rewrite the get_playlist function to use pagination, according to the total of playlists returned by the API.