JavaScript is required to use Bungie.net

#feedback

Edited by Recon Number 54: 1/16/2013 6:11:11 PM
34

Tag confusion, a (potential) simple solution?

I've noticed that there is a lot of discussion as to the use, intent, misuse, abuse, lack of direction, etc. when it comes to tags and tagging. If I may suggest, I think that there could be a relatively simple answer. 3 kinds of tags, from 3 sources. 1: OFFICIAL 2: Semi-Official 3: user-created Official tags would be ALL-CAPS. Only created and usable (in an OP) by Bungie-staff. Examples: #BUNGIE #MAILSACK #DESTINY Semi-Official would contain caps, but not be all-caps. Would be auto-created with a group creation (#Groupname) and if/when a particular 3rd-tier tag reaches a particular threshold (based on count, frequency, consistency and longevity) of usage (#Flood, #Off-Topic, #Politics, etc.) user-created tags would be in all lower-case.

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
  • I say limit a post to three tags or so. Most of the posts with a ton of tags are just using things like their name and random things. There really isn't a reason to need more than 3. Even in this post #feedback and # BungieNext shouldn't really be separate tags, and #feature and #featurerequest are also basically the same. 3 is enough for a group to share a thread into two somewhat related tags, so I think that should about do it. Bungie employees could have a #all that posts in all the tags or something.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon