Docs: Specify the string length limitation when verifying paste patterns

[asebert-caue]

Hello,
While integrating my own service with the embed tool, I noticed that there is a 450-character limitation for paste patterns.
Link to the relevant code line
I have opened an issue: GitHub Issue #135
I am not sure if this limitation is intentional or not, but I think it would be beneficial to have the ability to adjust this limit.

[neSpecc]

Regex checking is a slow operation. It was added to prevent main thread freeze when user pastes a long string.

What length will be optimal for you?

[asebert-caue]

Thank you for your response. I understand the need to lock things down to keep the application running smoothly, and I don't have a specific benchmark in mind for text length.

However, the maximum length for URLs is typically 2048 characters, although this can vary depending on the browser and server. Given this, it might be useful to allow for a higher limit than 450 characters to accommodate longer URLs. Is this length already too long?

Additionally, it would be helpful to specify this limit in the documentation so that users don't mistakenly attribute issues to a poor implementation of their regex.

What do you think?

[neSpecc]

I believe we shouldn’t add a new config property every time. Instead, it’s better to adjust the existing settings to cover most cases. I’d suggest increasing the limit from 450 to a bigger number that won’t freeze the browser.

A limit of 2000 seems excessive, in my opinion. It might work for technical web pages but not for embed-ready pages like YouTube, X, etc., which are the most common use cases for the paste pattern.