I think on a project, only the project owner should be able to add tags. Some users abuse this system that allows them to put random tags like "waffles".
Support?
Last edited by -iNetMaster- (2011-04-09 16:53:37)
Offline
-iNetMaster- wrote:
I think on a project, only the project owner should be able to add tags. Some users abuse this system that allows them to put random tags like "waffles".
Support?
what would stop the owner of putting "waffles"?
Offline
kayybee wrote:
Sometimes owners tag every possible thing.
There should just be a limit on how many tags a project could have.
The owner deletes the ones he doesn't want so he could add more himself.
but what would happen to projects like this one
Offline
I don't think this is a very good idea... other Scratchers can really help with projects that lack tags.
You can always flag spam tags, btw
Offline
TVflea wrote:
kayybee wrote:
Sometimes owners tag every possible thing.
There should just be a limit on how many tags a project could have.
The owner deletes the ones he doesn't want so he could add more himself.but what would happen to projects like this one
It should only keep the first 40 (if 40 were the limit) on the list or something.
Offline
How about tag approval? When someone adds a tag to a project, the project owner should have the right to choose whether not that tag should appear on the project tag list. It won't prevent the project owner from adding silly spam tags, but it can aid the project owner from getting spam tags made by others. ^^
Offline
cheddargirl wrote:
How about tag approval? When someone adds a tag to a project, the project owner should have the right to choose whether not that tag should appear on the project tag list. It won't prevent the project owner from adding silly spam tags, but it can aid the project owner from getting spam tags made by others. ^^
But like the project TVfkea showed above, the owner of that project would have allowed all the random tags to be put on there...
Offline
kayybee wrote:
cheddargirl wrote:
How about tag approval? When someone adds a tag to a project, the project owner should have the right to choose whether not that tag should appear on the project tag list. It won't prevent the project owner from adding silly spam tags, but it can aid the project owner from getting spam tags made by others. ^^
But like the project TVfkea showed above, the owner of that project would have allowed all the random tags to be put on there...
As I said, my suggestion doesn't prevent spam tags made by the project owner, but it helps prevent spam tags made by Scratchers other than the project owner.
Here's a clarification of my suggestion: Let's say User A wanted to tag User B's project "waffles". Instead of having the tag appear there automatically, User B would get a message saying something like "User A has tagged your project with 'waffles'. Accept of Reject?" and User B would reject the tag (unless, of course, User B wanted the waffle tag but we're running under the premise that User B hates spam tags).
Offline
kayybee wrote:
But then there'd be the problem of someone trying to add 100 tags, the person would receive 100 messages, if it's not answered and the tagger keeps it up, the server would get full of messages...
Maybe one at a time?
That happens, a lot.
Offline
I agree tagging needs major help.
However, project owners also add spammy tags, because it works to get more attention. (Commercial SEO spammers use this technique on sites like youtube.)
The problem:
One tagger is all it takes to give a project full authority in that tag. Tag pages are sorted by generic "love-its" instead of relevance to the tag as determined by the community. So if a popular project is added to a irrelevant tag like waffles by just one person, it instantly dominates in that tag.
How about this instead:
When you tag your project or someone else's:
1. It puts it in your user page with that tag.
(So tagging is first important to for you to organize your user page. On the side it lists all the tags you use, so you (and others that visit) can go back and click to see just "games" you made or liked. So with tagging as part of our reputation, we're less likely to add non-sense or spammy tags.)
2. It puts it in the tag page under "newly tagged as X" for a limited time, and counts as a vote that the project is relevant to that tag.
If people that frequent that tag page agree a project belongs, they'll vote it up and promote it there, otherwise it will soon drop out of view. (With tag pages more relevant, I believe Scratchers will frequent the ones they like; vote up or down projects there to help keep their favorite tags relevant. And we'll be less concerned that there's not enough games/art/doll/music... projects on the front page.)
FaveTags (or something better? please discuss) would require multiple people to use/agree with the tag for a project to become popular in it.... and would give people more reasons to be helpful taggers.
Last edited by JTxt (2011-04-10 18:18:54)
Offline
cheddargirl wrote:
How about tag approval? When someone adds a tag to a project, the project owner should have the right to choose whether not that tag should appear on the project tag list. It won't prevent the project owner from adding silly spam tags, but it can aid the project owner from getting spam tags made by others. ^^
I find this point quite viable plus there should be some thread for project makers making them more aware about how and why they should tag their projects.
Offline
Offline
Only letting owners tag and tag approval are cool thoughts, but would limit tagging more.
Scratch's tagging system is flawed for social tagging because one person is all it takes to give a project full power in a tag. Tag pages are sorted by "love-its" which are too general, instead of by how relevant it is to the tag.
And there is little reason for helpful tagging. Tagging does not help the tagger on Scratch like it does on some sites like delicious.com.
(Tagging helps them organise their user page, then the bonus is that it rates the link in that tag site-wide. (The tag list on the site is in order of relevance instead of when it was added, which I think contributes to Scratch's tags being used like a chat box.) No love-its or rating needed.)
So the solution to tagging must be deeper.
Please read what I wrote above. Agree? Disagree?
Last edited by JTxt (2011-04-11 12:54:20)
Offline