# Introduce per-device tags **URL:** \ **Category:** Feedback\ **Created:** [June 21, 2026, 2:45am UTC](https://forum.gl-inet.com/t/introduce-per-device-tags/69469 "2026-06-21T02:45:17Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![adziahel](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/adziahel/32/30285_2.png) [@adziahel](https://forum.gl-inet.com/u/adziahel)\ **Post date:** [June 21, 2026, 2:45am UTC](https://forum.gl-inet.com/t/introduce-per-device-tags/69469/1 "2026-06-21T02:45:17Z")
Hi, what I miss here is discussion tags for devices, e.g. `Flint 3|BE9300`, so users would not resort to a full-text search to find relevant info. Thank you in advance. ---
**Author:** ![will.qiu](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/w/b38774/32.png) [@will.qiu](https://forum.gl-inet.com/u/will.qiu)\ **Post date:** [June 25, 2026, 2:03am UTC](https://forum.gl-inet.com/t/introduce-per-device-tags/69469/2 "2026-06-25T02:03:33Z")
Hi Thank you for the suggestion. We have considered this approach before. However, since some users may not add tags when creating new topics, relying solely on tags for searching could cause relevant discussions to be missed. For now, we prefer to continue using full-text search, as it is more likely to find useful information across the forum. We are also exploring ways to improve the search experience in the future, such as introducing features similar to Google's AI Overviews. ---
**Author:** ![adziahel](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/adziahel/32/30285_2.png) [@adziahel](https://forum.gl-inet.com/u/adziahel)\ **Post date:** [July 5, 2026, 5:04pm UTC](https://forum.gl-inet.com/t/introduce-per-device-tags/69469/4 "2026-07-05T17:04:53Z")
As long as “Flint 3” considered an alias of “BE9300” by the full-text search, sure. But it isn’t at the moment, amirite? So if in a certain topic BE9300 is called one uniformly, users searching “Flint 3” will not see these topics, correct? Just did a quick test and that seems to be the case. ---
**Author:** ![will.qiu](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/w/b38774/32.png) [@will.qiu](https://forum.gl-inet.com/u/will.qiu)\ **Post date:** [July 7, 2026, 4:35am UTC](https://forum.gl-inet.com/t/introduce-per-device-tags/69469/5 "2026-07-07T04:35:15Z")
> [@adziahel](#): > > But it isn’t at the moment, amirite? Yes, for now we will likely still need to search twice: once using **BE9300** plus the relevant keywords, and once using **Flint 3** plus the same keywords. ---
**Author:** ![adziahel](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/adziahel/32/30285_2.png) [@adziahel](https://forum.gl-inet.com/u/adziahel)\ **Post date:** [July 9, 2026, 5:26pm UTC](https://forum.gl-inet.com/t/introduce-per-device-tags/69469/6 "2026-07-09T17:26:38Z")
Precisely. So, unless you’ve got means to tweak FTS to make it treat BE9300 a synonym to “Flint 2” etc., tags seem like the next best solution. ---
**Author:** ![will.qiu](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/w/b38774/32.png) [@will.qiu](https://forum.gl-inet.com/u/will.qiu)\ **Post date:** [July 10, 2026, 8:58am UTC](https://forum.gl-inet.com/t/introduce-per-device-tags/69469/7 "2026-07-10T08:58:31Z")
Hi, We understand the improvement you're suggesting. By adding tags such as `Flint 3 | BE9300`, users could search using either name and find the relevant information. However, as we mentioned previously, this still doesn't fully address the underlying issue: 1. Existing threads do not have these tags, so users would still need to search for both **BE9300** and **Flint 3** separately to find all relevant results. 2. Even for new threads, some users may not add the appropriate tags when creating a post, resulting in relevant content being missed. 3. In some cases, users share findings or workarounds within broader discussion threads, such as **[Firmware v4.9 Preview: What to Expect](https://forum.gl-inet.com/t/firmware-v4-9-preview-what-to-expect/68088)**. These posts cannot be fully covered by tags either, so users would still need to search for both **BE9300** and **Flint 3** separately to discover them. For these reasons, we believe adding tags would provide only limited benefit in this case. It could also create the impression that searching by tags will find _all_ relevant content, causing users to overlook other useful information. At the moment, searching for **BE9300** and **Flint 3** separately is still the most effective approach. We are also internally testing a feature similar to **Google AI Overview** to see whether it can help address this issue in the future. ---
**Author:** ![ViRomero](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/v/b2d939/32.png) [@ViRomero](https://forum.gl-inet.com/u/ViRomero)\ **Post date:** [July 22, 2026, 1:20am UTC](https://forum.gl-inet.com/t/introduce-per-device-tags/69469/8 "2026-07-22T01:20:52Z")
What if tag suggestions worked when posting? Like, if someone mentions BE9300 in their post, suggest adding the Flint 3 tag. Doesn't fix existing threads but might help future ones without forcing people to remember. ---
**Author:** ![will.qiu](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/w/b38774/32.png) [@will.qiu](https://forum.gl-inet.com/u/will.qiu)\ **Post date:** [July 22, 2026, 8:22am UTC](https://forum.gl-inet.com/t/introduce-per-device-tags/69469/9 "2026-07-22T08:22:21Z")
Hi, It looks like Discourse is planning to add a **search synonyms** feature. However, the priority seems to be relatively low and the development may be more complicated, so it has not been released yet. > **[Add search synonyms](https://meta.discourse.org/t/add-search-synonyms/142050)** > > I have been reading a lot here lately and see that ‘post’ and ‘reply’ seem to be used somewhat interchangeably. If this were done, it would result in fewer bothersome questions when someone uses the wrong one of the two for their searching before... We will also evaluate internally to see if there are any better approaches to address this issue. Thanks for your suggestion in anyway.