The sidebar menu has been completely reworked, thanks to the UX design work we did with Marie Cécile Paccard. It is now way easyier to interact with you profile or to distinguish pages displaying what's in your Library from what's on your instance federation bubble.
The work in progress on the PeerTube experience is going well: several interviews have been conducted, and our designer will soon be sending us summaries with her recommendations. In addition, we are planning to work together on the menus organization, but don't be impatient! This is an in-depth work and the results may only be visible in a few months 😉.
There is also a new plugin that allows to silence or block a list of predefined instances: our thanks to those who have started to create, publish and share their blocking lists, we hope that this kind of initiatives will multiply!
There is still a lot to tell about this v3, and people who contributed to make it happen. That's a good thing, because we will talk about it in January, for the v3 release post.
This <a href="https://framagit.org/framasoft/peertube/search-index" target="_blank">index engine code</a> is under FLOSS license so that anyone can host their own index engine and set their own eligibility rules. As an example, if you want to set up a search interface that only allows you to search for videos hosted on instances dedicated to video games, you will just have to create a list including all instances URLs you have selected and put it online. So that the index engine can refer to it and return you the appropriate results.
This <a target="_blank" href="https://framagit.org/framasoft/peertube/official-plugins/-/tree/master/peertube-plugin-video-annotation">annotation PeerTube plugin</a> allows you to display information in the player at a given time of a video. To do so, once the plugin is installed on the instance, you just have to go on the uploaded video information page, open the <i>Plugin settings</i> tab and then add your annotations and their time code. The placement of the annotations is in the player top right corner by default, but you can choose other locations. The annotations format must respect specific rules:
This index engine has common features with the PeerTube search engine (API). So, you could use this global search system in two different ways: by creating a dedicated web interface for it or by integrating it on a PeerTube instance search. We will give you more details on this feature on mid-July when we will publish the 2.3 release.
This list isn't exhaustive and it's possible that we may include other developments, depending on feedback from <a href="https://github.com/Chocobozzz/PeerTube/labels/Component%3A%20Moderation%20%3Agodmode%3A" target="_blank">the community</a>.
This new release includes many other improvements. You can see the complete list (in English) on <a href="https://github.com/Chocobozzz/PeerTube/blob/develop/CHANGELOG.md" target="_blank">https://github.com/Chocobozzz/PeerTube/blob/develop/CHANGELOG.md</a>.
This new release includes many other improvements. You can see the complete list on <a target="_blank" href="https://github.com/Chocobozzz/PeerTube/blob/develop/CHANGELOG.md">https://github.com/Chocobozzz/PeerTube/blob/develop/CHANGELOG.md</a>.
This new video report window now includes a checklist of possible reasons for the report and offers you a free writing field to specify your report if necessary.
This v2 adds <strong>HTML support (on top of text mode) in emails</strong> sent by PeerTube, making them less austere and avoiding bugs where links would get shortened.
This v3.1 also changes the way transcoding tasks are managed. Before, and for each instance, transcoding occured chronologically as users were uploading videos. Thus when a video maker was uploading several videos in a row, he prevented video transcoding from other users of the instance. Therefore we have <strong>modified the priority management system for these transcoding jobs</strong> so that when a user upload several files at the same time, the transcoding of some of his videos is de-prioritized (they are on standby) if another user upload a file. In other words, administrators can give an higher priority to optimize jobs and can decrease priority of transcoding jobs depending on the amount of videos uploaded by the user in the last 7 days. This prevents one single user from blocking other people's contents' uplaods: it's more fair. Besides, administrators can now see the progress of video transcoding in the list of on-going jobs on their instance.
Thus, it is now possible to authenticate users via an external server (OpenID or SAMLv2 compatible) or via an LDAP directory. This work was made possible thanks to funding from the <em>"Direction du Numérique pour l'Éducation du Ministère de l'Éducation et de la Jeunesse" (France)</em>.