[X] My Assistant

The system should be more robust to typos, so we don't have to type extremely slowly when applying temp tags to more galleries.

I typoed temp:gentlegiant twice, went back and deleted them from the galleries, and didn't see them in the pending approval tracker, so I thought they were gone.
Now I get PMs that they had to be manually rejected by a moderator anyway, and they are visible in the rejected tracker.
How about if instead of taking you straight to the form, it first says, "No such tag temp:gentletiant. Create this tag?"

This post has been edited by Necromusume: Sep 24 2023, 23:19

You can type slower and/or mark the request as "created by mistake" so we don't have to guess if it's a legit request or not. You can do this after the fact if you realize you made a mistake.

Since it didn't show up in the tracker, I didn't think I needed to.

And expecting users to fill out a form literally every time they make a typo is... not ideal.

This post has been edited by Necromusume: Sep 25 2023, 01:54

There's a window (15m I think?) to give a chance for you to enter sources/information before it goes to the tracker. You can go to https://e-hentai.org/tagjustification.php to see any unprocessed tags created by yourself

It's not possible to make the tagging process more interactive without reworking the entire interface, but I did make a small change so that users can always see their own tags in the tracker right away to avoid this source of confusion.

The system should be more robust to typos, so we don't have to type extremely slowly when applying temp tags to more galleries.

After you or anyone else created the tag (i.e. entered it into the temp tracker), you don't have to add the temp: modifier to use the tag. So after you created a request for temp:gentlegiant, you can afterwards just type "gentlegiant". That will use the newly created temp tag if typed correctly, if typed incorrectly you will get the "use temp: to create a new tag"-prompt, without any risk of accidentally creating another temp tag.

This might not work if the temp tag you created already exists in another namespace.

So, is there any plan of making the tool available for pre-existing temp tags in the forseeable future? Are there technical hurdles preventing it being implemented? It feels like it shouldn't be that far out given what already exists (which I'm aware is a hot guess for a codebase I don't know in the slightest) and as said before, I feel like using the tool rather than the NS thread would be much less tedious when cleaning up old temp tags.

So, is there any plan of making the tool available for pre-existing temp tags in the forseeable future? Are there technical hurdles preventing it being implemented? It feels like it shouldn't be that far out given what already exists (which I'm aware is a hot guess for a codebase I don't know in the slightest) and as said before, I feel like using the tool rather than the NS thread would be much less tedious when cleaning up old temp tags.

There are no plans to do that. Prior to this system being added, it didn't record the necessary information to create the approval records after the fact. And of course it wouldn't have what actually makes the system useful - the information provided by the tag creator about what the tag is.

There are no plans to do that. Prior to this system being added, it didn't record the necessary information to create the approval records after the fact. And of course it wouldn't have what actually makes the system useful - the information provided by the tag creator about what the tag is.

True, it would be quite useless to have that without the info provided by the tag creator. But I feel like you misunderstood me; what I meant was for there to be some way to provide that info for pre-existing temp tags by using the tag justification form rather than having to resort to forum threads.


Just to make sure we are on the same page, here is a basic use case that hopefully illustrates my intention.

What I want to do: Provide information so that an item on the public temp tag repository can be namespaced.

Current approach: Find a gallery where the tag is valid & seek out the necessary information. Post the tag name, the designated namespace, the relevant gallery and the information to the namespacing vigilante thread. Regularly check back to the thread to see if the request was processed or if a namespacer has a question on it.

My dream approach (the part in italics is not yet possible): Find a gallery where the tag is valid & seek out the necessary information. Type "temp*:existingtemptag" (or someting like that) in the tagging field to open up the tag justification form and provide the designated namespace and the information. Receive an automatic PN when the request is processed or a namespacer has a question on it.

"My dream approach" would be less tedious for the one providing the information (due to the automatic notifications when it is processed and already having the tag name and example gallery in the form) and assumably less tedious for the one handling the request (due to it being better organized than the thread).

True, it would be quite useless to have that without the info provided by the tag creator. But I feel like you misunderstood me; what I meant was for there to be some way to provide that info for pre-existing temp tags by using the tag justification form rather than having to resort to forum threads.

My dream approach (the part in italics is not yet possible): Find a gallery where the tag is valid & seek out the necessary information. Type "temp*:existingtemptag" (or someting like that) in the tagging field to open up the tag justification form and provide the designated namespace and the information. Receive an automatic PN when the request is processed or a namespacer has a question on it.

Hm. I suppose it would be possible to make it so that if you (up)vote a temp tag that doesn't have a pending approval record, it creates one and pretends you were the one who created it. I'll look into it.

Uh, say if I reject a "dream approach" petition, is it going to make the existing temp tags go poof as well? That will save us the blocking effort if that's the plan.

Uh, say if I reject a "dream approach" petition, is it going to make the existing temp tags go poof as well? That will save us the blocking effort if that's the plan.

It would, yes.

Edit: Well, this turned out to be a simple addition so I went ahead and added it. If someone with the ability to create temp tags (up)votes a temp tag that doesn't have an existing pending application on a public gallery, they will now be considered the creator of said tag, initiating the standard tag justification process.

Amazing! I was pining for this for the past two months and all I had to do was type it out properly. (IMG:[invalid] style_emoticons/default/biggrin.gif)

Edit: The main issue I see for now is that it makes it pretty easy to start the process unintentionally. Maybe you could do it so that you're only taken to the form if you actually type temp:existingtemptag rather than only upvoting?

This post has been edited by peterson123: Oct 21 2023, 12:43

(Btw, for blocking/slaving/renaming requests, please still use the corresponding threads for those)

Edit: The main issue I see for now is that it makes it pretty easy to start the process unintentionally. Maybe you could do it so that you're only taken to the form if you actually type temp:existingtemptag rather than only upvoting?

Dunno how much of an issue that really is, seeing as it only affects temp tags created before the tag approval system went live. If you upvote a tag, you're already saying "yup, looks good to me", so if you have the capability to create temp tags I would expect you to be able to back it up.

Dunno how much of an issue that really is, seeing as it only affects temp tags created before the tag approval system went live. If you upvote a tag, you're already saying "yup, looks good to me", so if you have the capability to create temp tags I would expect you to be able to back it up.

I know it's not the intended way to do it, but of whenever I wonder if some tag exists or is blocked, I do so by just trying to tag it on some unrelated gallery... now if I get "unlucky", it does exist and I get taken to the form (before I just would have revoked my upvote). I probably should just get used to doing that the proper way. But we'll see if there is an increase if accidental tag form submissions in the next few days.

I know it's not the intended way to do it, but of whenever I wonder if some tag exists or is blocked, I do so by just trying to tag it on some unrelated gallery... now if I get "unlucky", it does exist and I get taken to the form (before I just would have revoked my upvote). I probably should just get used to doing that the proper way. But we'll see if there is an increase if accidental tag form submissions in the next few days.

FWIW, as long as the unrelated gallery is private, it won't trigger a justification request.

From now on, please do NOT upvote any temp tag unless you are prepared to submit the supporting evidence for that tag (or you checked that there is an active and correct petition for the temp tag).

In the event that you do upvote the temp tag by mistake, please don't enter "created by mistake" as your reason, but rather "upvoted by mistake" to notify the namespacers.

I changed it so that if you are just typing the tag without "temp:" it won't trigger the new behavior. It does however still trigger it if you click the "vote up" button on a temp tag, this would require a more fundamental rework to change.

well, it seems not bad