[Feature Request]: Support for youtu.be url format with timestamp

[ArthurKun21]

Guidelines

• I have searched the issue tracker for open and closed issues that are similar to the feature request I want to file, without success.
• I have searched the documentation for information that matches the description of the feature request I want to file, without success.
• This issue contains only one feature request.
• I have read and agree to follow the rules.

Problem Description

Navigating to this URL does not load in freetube due to having timestamp https://youtu.be/OT_iyvOy0Tk&t=90

Proposed Solution

Add support for it

Alternatives Considered

None

Issue Labels

improvement to existing feature

Additional Information

It was actually different video, but I was surprised to see this type of URL for youtube. Thought it was broken but it loaded up in the website using browser

[efb4f5ff-1298-471a-8973-3d47447115dc]

We do support https://youtu.be/OT_iyvOy0Tk?t=90 though
Where did you get this url from?

[absidue]

As mentioned by @efb4f5ff-1298-471a-8973-3d47447115dc we do support youtu.be URLs with timestamps they just need to follow the WHATWG URL specification that JavaScript uses (query parameters start at the ? not the & character). In your example the path is /OT_iyvOy0Tk&t=90 so FreeTube looks at it and says it's not a video ID, so falls back to treating it as a channel URL. YouTube's youtu.be rediretor either follows a different URL specification or has some extra tolerance built in for broken URLs.

I'll improve our parsing so it can at least extract the video ID from the start of the path in cases like these, but it will still ignore the timestamp.

[ArthurKun21]

Where did you get this url from?

someone shared a different youtube video with this url format. Others have viewed it normally but when I loaded it up with freetube it errors like in the picture above due to having timestamp. Removing the timestamp will load it just fine in freetube, the problem was it was shared with timestamp

just need to follow the WHATWG URL specification that JavaScript uses (query parameters start at the ? not the & character)

honestly, was confused the same when I saw this url format

I'll improve our parsing so it can at least extract the video ID from the start of the path in cases like these, but it will still ignore the timestamp.

https://youtu.be/OT_iyvOy0Tk <- works fine

https://youtu.be/OT_iyvOy0Tk&t=90 <- was not working, hence the feature request for video with timestamp

[absidue]

With timestamps is already supported for valid URLs, so you need to replace the & with a ?. As mentioned above I'll make our parsing a bit more flexible so it only checks that the start of the path is a video ID and extracts that, so it will be treated as if the broken part weren't there. Adding workarounds to fully handle broken URLs is a non-goal though.