Often you need to accept any separator character in a filter.[...]Separator character is anything but a letter, a digit, or one of the following: _ - . %
When looking at the available subscriptions and especially now that we have the new algorithm for the shortcuts that requires using non-alphanumeric delimiters, it could (not yet tested in terms of false-positives) make things a lot easier if there would be a separator that includes underscore, hyphen and dot. I guess % should remain except due to it's special meaning in html urls.
- Code: Select all
All of those structures are not theoretical, but pretty common all around. Also, looking at the subscriptions, you can find many examples of these "duplicates" proving that. Yet only the first and the last could be combined to ^exampleads^ currently, which limits the the real-world use to few rare situations (like ports in urls).
Therefore I'm suggestion either modifying ^ or introducing a more inclusive separator.