I always access Danbooru over HTTPS and I started getting the following message today:

400 Bad Request

The plain HTTP request was sent to HTTPS port

nginx/1.2.1

Not exactly an issue, but I don't know where else to talk about this...

Gorilla is an artist tag, not a normal tag.

game2009 said:

Not exactly an issue, but I don't know where else to talk about this...

Gorilla is an artist tag, not a normal tag.

single post artist moved to gorilla_(hero_up) instead. all gorilla posts consistent to wiki definition and common perception; and back to gentag.

Looks the like the category cache for gorilla was still set to artist. I cleared the cache.

I have a question here. Is it possible to organize frequent tags by groups or subtitles or something like that? Like create a "hair" group, and there go all sorts of hairtags. My list is a mess now and I get lost in it.

MagicalAsparagus said:

I have a question here. Is it possible to organize frequent tags by groups or subtitles or something like that? Like create a "hair" group, and there go all sorts of hairtags. My list is a mess now and I get lost in it.

No, there's not really a good way to use frequent tags like that. I guess you could fake it though, like if you put this in your frequent tags:

HAIR_GROUP:
black_hair
blue_hair
OTHER_GROUP:
1girl
5boys

Those all-caps names could sort of work as titles for different groups. Not really a great solution.

Hm. Sounds good for now, thanks. Maybe this can somehow be done in the future updates?

MagicalAsparagus said:

Hm. Sounds good for now, thanks. Maybe this can somehow be done in the future updates?

Well there's this suggestion, which if implemented would basically allow grouping of different tags and searches you want to keep track of. Similar to what you want.

Is searching order:commentary not possible?

Schrobby said:

Is searching order:commentary not possible?

It's order:artcomm.

uxw said:

It's order:artcomm.

Thanks.

uxw said:

It's order:artcomm.

That doesn't give the correct order. An older comment is first in the list, one from 2 hours ago isn't listed at all.

Schrobby said:

That doesn't give the correct order. An older comment is first in the list, one from 2 hours ago isn't listed at all.

Can you give more information? What search are you using specifically, and what post are you expecting to appear doesn't?

Toks said:

Can you give more information? What search are you using specifically, and what post are you expecting to appear doesn't?

Sure. I searched order:artcomm commentary user:Schrobby and expected the result to be pictures I uploaded with translated artist commentary in the order those comments were created. Right now that list should begin with post #1633046, the artist comment & translation are about 4 hours old. Instead the list begins with post #1106917 and post #1633046 is nowhere to be seen.

I experimented and found that substituting the commentary tag with -commentary_request seems to deliver the correct result. I'm happy with this, but it's still weird since both searches should give me the exact same result.

Schrobby said:

I experimented and found that substituting the commentary tag with -commentary_request seems to deliver the correct result. I'm happy with this, but it's still weird since both searches should give me the exact same result.

No, those two are not necessarily the same. Those tags are manually added, so mistakes/missing tags are possible. For post #1633046, nobody added the commentary tag to the post after the commentary was translated, so it is not returned when searching for commentary.

I added the commentary tag to that specific post so it should be returned now.

Toks said:

No, those two are not necessarily the same. Those tags are manually added, so mistakes/missing tags are possible.

True. Maybe that should be automated, would be quite easy to do.

Schrobby said:

True. Maybe that should be automated, would be quite easy to do.

Not really. What if someone only half-translated a commentary? The site wouldn't be able to tell it's only half-finished so it would wind up adding the commentary tag erroneously.

Would also be a problem for commentary that is originally in English and doesn't need a translation.

Toks said:

Not really. What if someone only half-translated a commentary? The site wouldn't be able to tell it's only half-finished so it would wind up adding the commentary tag erroneously.

Would also be a problem for commentary that is originally in English and doesn't need a translation.

Right. Well, I'm going to use -commentary_request anyway.

That said, maybe adding commentary_request should be automated anyway. I just found massive amounts of filled artist commentary fields without the commentary_request tag. As it is they'll probably never get translated.

See page 2 of order:artcomm -commentary_request user:Schrobby, it consists almost entirely of such posts.

I think when you look for commentary to translate it's better to find some false positives and remove the tag than to not find commentary needing translation.

I don't like the idea of false positives and negatives everywhere because the site itself uses the tag wrong. And the solution isn't as simple as letting people manually remove/add the tag when they come across problems. That would mean we'd need to let people edit the tag normally, in addition to having it be automated (as opposed to locking the tag in and disabling manual editing). This raises several new issues.

Besides, if a post is missing the commentary_request tag, maybe that actually means that nobody is requesting it be translated? I mean, it is a request tag, not really a "watch out here comes some commentary" tag, so a post doesn't necessarily need the tag even if it has untranslated commentary. This is how all the request tags work (or should), including translation_request.

What we could do though, is add search options for the artist commentary itself, including options for whether the original is present and whether a translation is present. This should basically allow searching for what you want, regardless of whether people screwed up the tags or not, while avoiding having the site screw up the tags.