| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
GitHub instead of showing all issues
|
|
|
|
|
|
|
|
Co-Authored-By: Samantaz Fox <coding@samantaz.fr>
|
|
|
|
Co-Authored-By: Samantaz Fox <coding@samantaz.fr>
|
|
Co-Authored-By: Samantaz Fox <coding@samantaz.fr>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fix/popular-disabled-error
|
|
|
|
This reverts commit 1363fb809436464de57b90113864ff50867a9dae.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The current Content Security Policy does not allow to embed videos
inside local HTML files which are viewed in the browser via the file
protocol. This commit adds the file protocol to the allowed frame
ancestors, so that the embedded videos load correctly in local HTML
files.
This behaviour is consistent which how the official YouTube website
allows to embed videos from itself.
Signed-off-by: Tomasz Wilczyński <twilczynski@naver.com>
|
|
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
|
|
|
|
similar to what's done in #3793, this is causing an assert on my instance
|
|
|
