Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Regression: Pinned hashtag feature does not work anymore with multiple hashtags #12453
The feature to pin hashtags and to include additional tags for this column worked nicely until some weeks ago, but then I noticed a severe regression of this feature. Since then, the frequency of new messages in the columns with multiple tags has substantially dropped. The regression is that the pinned hashtag search does not search additional tags correctly and omits a substantial number of toots.
The pinned hashtag feature should show all toots that match any of the hashtags in the list.
The pinned hashtag feature does not work anymore with multiple hashtags. It does not display all relevant toots.
Steps to reproduce the problem
Since when: Since a Mastodon update some weeks ago. Before, it worked correctly. The bug is still present in v3.0.1
Thanks @Gargron for your quick answer.
It's unfortunate that it was necessary to limit it to 4 search tags due to performance. It would be great to have more than 4 hashtags in the column. At the moment, I have over 20 tags (which doesn't work anymore, of course).
Thus, 2 questions to you:
//2: In the web interface, the feature is described as "Include additional tags for this column", which is a bit misleading. Wouldn't it be better for now to change the wording to e.g. "Add max. 3 more tags for this column"?
This is maybe where option to follow hashtags #1096 would come in handy. It's the second most
What's more, I had no idea that pinned hashtag search columns were limited to four hashtags - there was no indication in the UI that anything beyond the first four were ignored. So I've opened No indication in web UI that hashtag search pinned columns only work for the first four hashtags #12458!
I close this bug, because the pinned hashtag feature works as intended (Gargron pointed it out).
However, there are two follow-up bugs:
After the comment by @unextro I reopen this bug again.