As most of us know the substrate-node tag has been finding its way into many posts; often it is auto-suggested. This tag is redundant. It is like placing a programming tag on a Stack Overflow question.
This is a follow-up post after having discussions in chat with @JNat.
We came up with a remedy for this issue that we would like to present to the community:
- Create a node synonym tag for substrate-node tag and merge the two tags, resulting in only the node tag being allowed to be used.
As commented by @JNat:
Creating a synonym for a tag prevents the "source" tag from being used, and any time a user tries to use it the system will automatically remap it to the "target" tag — for that to work retroactively, we'd need to merge the tags
@JNat also asked if perhaps the questions that have substrate-node tag made more sense with "related" synonyms such as archive-node, full-node, rpc-node, etc. If this was the case then our approach at solving this issue would be different. However, after reviewing the 261+ questions with the substrate-node tag, I do not think this is the case - none of these questions had the context of a related tag.
If we can get confirmation that creating one synonym: node and not multiple related synonyms is the way to solve this issue, then we will go ahead, create the node synonym and merge the tag node with substrate-node.
substrate-node
around as a synonym ofnode
, then anyone who typessubstrate
into the Tags field will see the [node] tag as a suggested tag.