Danbooru

Tag Vandalism

Posted under General

Log said:
No idea, I hadn't even seen half of them so I imagine I accidentally pushed approve all instead of hide all or something. Possibly that the kitten was walking on the keyboard since I had the queue open when I went to bed.

The flag message was just because it was first thing after I woke up and one of them was something I wouldn't approve ever and I was like "what the fuck."

Heh, the same think happened to me a week or so ago. I hadn't even realized it until one of the pics I accidentally approved was flagged by someone else.

nanami said:
Sorry to do this, but I have to revive this thread because of some recent tag vandalism.

user #342632, alexscout001, has either replaced the "fuuro_(pokemon)" tag with "taina_imatake" or added "taina_imatake" to posts with "fuuro_(pokemon)". Lots of posts were affected.

EDIT: All of his "taina imatake" edits have since been undone, BTW. But it seems the user would restart time after time.

I'm willing to assume that's been a very inept attempt at some meaningful action, given how clumsy all of his/her edits were. I'll mail him/her and ask for an explanation.

S1eth said:
mrbtkzrt
In case you can't access his profile, here his tag history

He removed all tags and the source from posts and changed the rating from s to e.

I can only go as far as accessing the block page, but hitting the submit button resulted in failbooru. Which is weird because I used to submit ban for a few users whose profiles I couldn't access.

Edit: cleared the cache fixed that.

Updated

Hardie reverted post #337229's tag history to a point before the loli tag was added, removing some other tags in the process without readding them later on.

Since he is a member, he shouldn't be able see the image, let alone edit its tags. Can you simply input the tag history URL of any loli/shota image and edit it?

http://danbooru.donmai.us/post_tag_history/index?post_id=976293

It only happened on a single image and I don't know if that's worth any punishment, but I thought I'd report anyway.

Can the IP be locked out somehow to prevent this from reoccurring? It would probably also be a good idea to change the permissions for new accounts to prevent malicious edits of pools and wiki's, maybe to a week minimum or up to a month.

1 2 3 4 5 6 10