I have a question. Is it allowed for me to tag images such as post #162135 with bad_id?

The source field says it is from deviantart but it gave me 404 error message when I click it.

My instinct is to say leave it pixiv, because the wiki states that and there are probably some specific scripts and such applying it specifically to pixiv posts. If we opened it up to DA we'd have to make it for AN picture with a broken source link, really.

jxh2154 said:
If we opened it up to DA we'd have to make it for ANY picture with a broken source link, really.

Perhaps we do need a broken_source tag for just that, then?

Couldn't hurt.

glasnost said:
Perhaps we do need a broken_source tag for just that, then?

I agree. As far as I know, we don't have proper tag for non-pixiv images with broken source.
Also, what about images that have no source at all? Should they have their own tag too?

I suspect that broken_source will probably be misused a lot. Often the source has hotlink protection (especially FC2 sites and other image blogs), so that the link itself will not work, but the image is still there if you open it with an empty referrer (i.e. copy URL and open in new tab).

Wouldn't that fall under source request?
EDIT: In response to kunangkuadrat

T5J8F8 said:
Wouldn't that fall under source request?

Oh, I totally forgot that. Please disregard the latter part of my comment.

I hope you're not saying that source_request should be used even when you don't actually want to know.

Interesting, according to forum #15554 a year ago

source request- Used somewhat like the current 'tagme'; for when an image is thought not to be original but the series isn't known.

I had a feeling at the time source_request would be misconstrued for the source field and it appears that came true. Perhaps we need to move source_request copytags:0 to something more intuitive like series_request?

e: Not all of them but most of them, they will have to be checked for sources as well since the tag changed or whatever happened.

How about copyright_request, to match with artist_request and character_request

Fencedude said:
How about copyright_request, to match with artist_request and character_request

+1

Using copyright_request sounds good to me.

If we were to use it, we'd have to clarify that original is a valid copyright as well.

piespy said:
I suspect that broken_source will probably be misused a lot. Often the source has hotlink protection (especially FC2 sites and other image blogs), so that the link itself will not work, but the image is still there if you open it with an empty referrer (i.e. copy URL and open in new tab).

This. Pixiv is nice and predictable, and very common on Danbooru. Hotlink protection on other sites would just make things confusing.

Certainly don't want anything else getting mixed in with the bad id tag, either.

jxh2154 said:
there are probably some specific scripts and such applying it specifically to pixiv posts

(waves)

copyright request? Are you serious? No. The vast majority of danbooru users don't understand that we use the word "copyright" in an extremely questionable way to denote a fictional universe, or however you want to define what we call a "copyright".

Thats nice, who cares?

RaisingK said:
Pixiv is nice and predictable, and very common on Danbooru. Hotlink protection on other sites would just make things confusing.

Certainly don't want anything else getting mixed in with the bad id tag, either.

Maybe bad_id should be changed to bad_pixiv_link or something to prevent confusion.

Or prevent the tag to be manually added so that only the script can (providing the site can make the difference).

Cyberia-Mix said:
Or prevent the tag to be manually added so that only the script can (providing the site can make the difference).

Out of ~30,000 posts tagged bad_id yesterday, only 8 did not have pixiv sources. That's about how many it was last time I checked, a while back. Very easy for me to take care of. There is no problem here.

That's fine if it's no trouble but I don't get why you wouldn't want this additional security since there's apparently nothing to gain from users contribution to tagging here, just as it's been suggested for the *res tags to work.