B-b-b-but I spent so much time tagging all these...
Okay, whatever. It is reasonable after all. Purge them, I'll get over it ._.
Posted under General
jxh2154 said:
So we're getting rid of which?
character_request
copyright_request
artist_request?
What about
annotation_request
collaboration_request
As far as I'm aware, the ones that MagicalAsparagus spammed were copyright_request, artist_request, and tagme. I don't believe the others were touched.
Copyright_request is 99.999% a duplicate of copytags:0
post #1668897, post #1633962, post #1630089, post #1607927, post #1607924, post #1606960, post #1590385, post #1587515, post #1586502, post #1578001, post #1536891, post #1523781, post #1507755, post #1507750, post #1507749, post #1449765, post #1447715, post #1326824, post #1300735, post #1250326, post #1219531, post #1187928, post #1133136, post #1010484, post #59358 and maybe some photos of wallscrolls/magazines that probably shouldn't even be here anymore are all that would require it back from the suggested issue area.
Character probably shouldn't be purged because it's not really a replication of anything. Artist is somewhere in the middle.
MagicalAsparagus said:
If you are going to purge tagme as well I suggest creating a thread for this purpose. Spamming aside, I put tagme on posts that I really don't know how to tag when I do it manually.
When I don't know how to tag some specific thing I like to put an X_request tag on the post, where X is what I don't know how to tag. e.g. food_request, flag_request, bird_request, whatever. Just tagme doesn't tell people specifically what needs to be tagged so it's less likely to get them to do anything.
mass update copyright_request -> -copyright_request
mass update artist_request -> -artist_request
mass update tagme -> -tagme
test for a really bulky update.