| Age | Commit message (Collapse) | Author |
|---|
|
"Temporary" fix, until a better and more permanent solution is found.
Closes issue 4584
|
|
Trending music was returning less than 24 videos which was getting
filtered out. Since multiple categories only appears on the default
trending page, we don't need to do that filtering for Music, Gaming or movies.
Closes issue 4596
|
|
Before this PR, the bitrate was only returned for the 'adaptiveFormats'.
They are now also returned the 'formatStreams'.
No linked issue
|
|
The new comment format is similar to the description's commandRuns.
This should fix the issues with most comments but there are still
some more changes that would need to be made like adding support for
formatting (bold, italic, underline) and channel emojis.
Fixes issue 4566
|
|
Also fixes the build on nightly as the offending code was removed.
Related to
https://github.com/iv-org/invidious/pull/4270#issuecomment-1858876952
|
|
Returns the 'isPostLiveDvr' field in the videos API when the video
is a post-live DVR (= ended livestream that hasn't been reprocessed
into VOD yet).
Example taken 10 minutes after that livestream ended:
/api/v1/videos/euqnWk-uP6M
{
...
"isPostLiveDvr": true,
...
}
Partially fixes 4421
|
|
Closes 3323
|
|
YouTube added a new format for like data in December 2023.
This PR adds support for parsing saod new format.
Related: LuanRT/YouTube.js issue 557
Closes 4419
|
|
Before this PR, Invidious assumed that fetching the DASH manifest from
YouTube will always be successful and didn't check the status code.
That meant that if YouTube gave a rate-limiting page, invidious would
return an HTTP 200 response with the 'application/dash+xml' Content-Type
header and the YouTube ratelimiting page as the body.
No associated issue
|
|
Example from an auto generated channel (Minecraft - Topic):
/api/v1/channels/UCQvWX73GQygcwXOTSf_VDVg
{
...
"tags":[
"Video game","Indie game","Xbox One","New Nintendo 3DS",
"PS3","Nintendo Switch","Wii U","Fire OS",
"Mac operating systems","Apple TV","Xbox 360",
"PlayStation Vita","PS4","Windows","Linux","Nintendo 3DS",
"iOS","Windows Phone","iPadOS","Java","Android","tvOS",
"ChromeOS"
]
...
}
Example from another channel (Mr Beast):
/api/v1/channels/UCX6OQ3DkcsbYNE6H8uQQuVA
{
...
"tags":["mrbeast6000","beast","mrbeast","Mr.Beast","mr"]
...
}
No associated issue
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Co-Authored-By: Samantaz Fox <coding@samantaz.fr>
|
|
|
|
Co-Authored-By: Samantaz Fox <coding@samantaz.fr>
|
|
Co-Authored-By: Samantaz Fox <coding@samantaz.fr>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This handler should no have been removed in 4276, as it adds the required CORS
header (Access-Control-Allow-Origin) for public acces to the API.
Thanks to iBicha for noticing this!
|
|
Note: WebVTT does allow some tags in the cue payload in some circumstances
while this PR just blindly escapes everything:
https://developer.mozilla.org/en-US/docs/Web/API/WebVTT_API#cue_payload_text_tags
|
|
This PR adds a CSS-only image carousel for community posts with more than
one image attached.
Closes issue 3522
|
|
The #contents div now takes the full width on small screens (< 1280px).
All page elements have a little more room, especially the video titles.
|
|
Closes issue 3120
|
|
Co-Authored-By: Samantaz Fox <coding@samantaz.fr>
|
|
|
|
Languages impacted: es, fa, pt
|
|
This handler should no have been removed in 4276, as it adds the required CORS
header (Access-Control-Allow-Origin) for public acces to the API.
Thanks to iBicha for noticing this!
|
|
The function names `count_users_active_6m` and `count_users_active_1m` were
swapped. As the names were swapped on both sides (declaration and use), this
had no functional impact.
No related isse was tracked.
|
|
This PR fixes an issue where the `scopes` parameter would see its wildmark
characters (*) removed during the login page redirection, after that a call
to `/authorize_token` was made while the user was not logged in.
Closes issue 4200
|
|
It seems that at some point, Youtube changed the URL parameter from `plid`
to `list` and we didn't notice. This fixes that.
Closes #3929
|
|
|
|
Multiple users have reported that the fields parameter is slowing down API
response times significantly. As most API endpoints are already optimized to
make as few requests as possible to Youtube, there is no point in limiting the
output. Furthermore, the added processing might be part of the broader memory
leak problem (See 1438).
In addition, the small increase in data output is not much of an issue compared
to the huge video proxy that lies next to this API.
No related issue tracked
|
|
This PR parses the start and end time for clips.
It also adds a new, dedicated API endpoint (`/api/v1/clips/{id}`) for
retrieving the start and end time of a clip.
Here is a sample response from that new endpoint (`video` is a video object,
as described in https://docs.invidious.io/api/common_types/#videoobject):
GET `/api/v1/clips/UgkxxPM3BRphCAPLP88YoUGuj79KXPfpNNO_?pretty=1`
Response:
```
{
"startTime": 8842.645,
"endTime": 8855.856,
"clipTitle": "✂️ Kirby is pink!",
"video": {}
}
```
Closes issue 3921
|
|
Previously, the suggestion were HTML encoded. This PR fixes that.
|
|
This adds `playlistId` and `startTimeSeconds` to /api/v1/resolveurl if these
informations were returned by Youtube's endpoint.
|
|
Some playlist author's don't have a YouTube channel, so does movies.
This caused various extractors (related videos, search) to fail.
Closes the following issues:
2530, 3349, 3766, 3812, 4133
|
|
|
|
closes #3120
|
