Legacy Semicolon required in hash tag subscriptions

[vijayninel]

It seems that hash tag subscriptions still require a semicolon to be added at end of the word even if the preference is set to "no" in the Require Semicolon for username field. Please check if it is possible for you to remove the semicolon for hash subscriptions as well.

Thank you.

 

[Fillip H.]

It's intended to work like it does because of the challenges in correctly matching hash tags without requiring the delimiter. It's a massive performance gain to require it for usernames as well, but most people don't want to use it

We'll take it into consideration, but I can't promise anything unfortunately