It's been quite a while since the last release! There've been 198 commits from 27 contributors.
A couple smaller features have since been added. Channel pages and playlists in particular have received a bit of a face-lift, with both now displaying their descriptions as expected, and playlists providing video count and published information. Channels will also now provide video descriptions in their RSS feed.
Turkish (tr), Chinese (zh-TW, in addition to zh-CN), and Japanese (jp) are all now supported languages. Thank you as always to the hard work done by translators that makes this possible.
The feed menu and default home page are both now configurable for registered and unregistered users, and is quite a bit of an improvement for users looking to reduce distractions for their daily use.
default_home are now configurable by the user, and have therefore been moved into
feed_menu: ["Popular", "Top"] default_home: Top # becomes: default_user_preferences: feed_menu: ["Popular", "Top"] default_home: Top
Several new options have also been added, including the ability to set a support email for the instance using
admin_email: EMAIL, and forcing the use of a specific connection in the case of rate-limiting using
force_resolve (see below).
Authenticated endpoints are now properly documented, as well how to generate and use API tokens. My hope is that this makes some of the more interesting endpoints more accessible for developers to use in their own applications.
API endpoints for interacting with custom playlists have also been added with documentation available here.
This is probably the feature that has been the longest in the pipe and that I'm quite pleased is now implemented. It is now possible to create custom playlists, which can be played and edited through Invidious. API endpoints have also been added (documentation here).
Overall I'm quite pleased with how smoothly it has been rolled out and with the experience so far, and I'm exctited for how it can be extended and improved in future.
It is now possible to view a list of public instances (as provided in the wiki) through an API or a pretty new interface here. It combines uptime information, statistics from each instance and basic information already provided in the wiki. I expect it should be much more user-friendly than compiling the information yourself, and is already used by Invidition to provide a list of instances for users to choose from.
The site itself is licensed under the AGPLv3 and the source is available here.
Many users have likely noticed this error message if using Invidious directly or through another service, such as FreeTube. This issue is caused by rate-limiting by Google, and is not a new issuee for projects like Invidious (notably youtube-dl) and appears to be affecting smaller, private instances as well.
There is not a permanent fix for administrators currently, however there is some information available here that may provide a temporary solution. Unfortanately, in most cases the best option is to wait for the instance to be unbanned or to move the instance to a different IP. A more informative error message is also now provided, which should help an administrator more quickly diagnose the problem.
For those interested, I would recommend following #811 for any future progress on the issue.
I'm quite late to this announcement, however I'm pleased to mention that Invidious is now a BAT verified publisher! I would recommend looking here or here for learning more about what it is and how it works. Overall I think it makes an interesting substitute for services like Liberapay, and a (hopefully) much less-intrusive alternative to direct advertising.
BAT is combined under other cryptocurrencies below. Currently there's a fairly significant delay in payout, which is the reason for the large fluctuation in crypto donations between September and October (and also the reason for the late announcement).
Currently I'm quite pleased with the current state of the project. There's plenty of things I'd still like to add, however at this point I expect the rate of most new additions will slow down a bit, with more focus on stabililty and any long-standing bugs.
Because of this, I'm planning on releasing a new version quarterly, with any necessary hotfixes being pushed as a new patch release as necessary. As always it will be possible to run Invidious directly from master if you'd still like to have the lastest version.
I'll plan on providing finances each release, with a similar monthly breakdown as below.