You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This doesn't let me to share the video from youtube app to a friend using the bot in a simple way.
Proposal
Let's parse links using (probably not) rfc-compliant pattern like:
/https?:\/\/[^\s\/]+(\/\S*)?/g
In search of the perfect URL validation regex
Maybe we should validate host in the link not to be local-addresses like localhost, 127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 and so on.
The text was updated successfully, but these errors were encountered:
PROger4ever
changed the title
Search for links throughout the whole message
Search for links throughout whole message
Sep 23, 2024
Thank you for taking the time to share your valuable suggestions with us. We will carefully review your input and assess the feasibility of incorporating these ideas into our project. From the first look of this, it appears that this change may impact the bot's current YouTube search functionality. One possible solution could be to limit YouTube searches to instances where the /search command is specifically invoked. We would appreciate your thoughts on this approach and any other ideas you may have.
Please allow us some time to thoroughly evaluate your suggestions. We will get back to you as soon as we have a clear understanding of how to proceed.
Problem
When you share youtube-video from mobile app to telegram, it has name in the beginning like:
But ytdlbot searches for link in message begininng:
ytdlbot/ytdlbot/ytdl_bot.py
Line 593 in dd3e42f
This doesn't let me to share the video from youtube app to a friend using the bot in a simple way.
Proposal
Let's parse links using (probably not) rfc-compliant pattern like:
In search of the perfect URL validation regex
Maybe we should validate host in the link not to be local-addresses like
localhost
,127.0.0.0/8
,10.0.0.0/8
,172.16.0.0/12
,192.168.0.0/16
and so on.The text was updated successfully, but these errors were encountered: