You are viewing a single comment's thread from:

RE: [Crowdsourced solutions] The problem with Tags...

in #crowdsource7 years ago

I feel like there’s something here, but it seems possibly too complex. What if you just made tags the vehicle of the upvote? In other words, you wouldn’t upvote or flag a post and also a tag—you’d upvote the post by upvoting one of the attached tags. Maybe that’s what you’re suggesting, already. So you wouldn’t get to upvote/flag a bunch of different tags, but I think it would still approximate a community consensus of what the post is and where it belongs.

Sort:  

The essential idea isn't that complex. From a user interface perspective, it works pretty well on LinkedIn and I think it could be replicated very similarly here. My brother is the author of the post and wouldn't be familiar with the inner workings of the Steem blockchain. I do think voting on the post should be separate from voting on tags, because the two are conceptually separate. One is to reward contributions, the other is for collectively sorting/curating content.

I don't know what the best way to do it from a technical perspective is. We could either have an SMT for tag curation or we could have part of the reward pool dedicated to it. Almost certainly it would need a hard fork IMO.

Yeah—that makes sense; conflating specificity with quality is certainly the weakness of my suggestion. Basically, I think design is about trade-offs, and in this case I’m inclined to promote simplicity over specificity. I can totally see why you wouldn’t want that, though, especially if you have experience with the system working as intended.