corgi_bread said:
I don't think it even needs to be that long. I mean, look at the valid FFD reasons:

'Artist is DNP'
'Smaller/cropped/inferiorrepost version of post #xxxxxx'
'RL porn'

I can't think of any reason to have the FFD length be any longer than those.

Artists who fail the check to find out about the Take down and for public amusement.
Also to give room for explanations and links, you too often paste the entire URL into the reason which cuts of up to 120 characters.

NotMeNotYou said:
Artists who fail the check to find out about the Take down and for public amusement.
Also to give room for explanations and links, you too often paste the entire URL into the reason which cuts of up to 120 characters.

That's why god invented tinyurl.

How about a message on the upload page that tells you about the one-week membership requirement to upload?

How about instead (or besides) that, the rules appear for newly registered users?

Xch3l said:
How about instead (or besides) that, the rules appear for newly registered users?

The rules are there before you even register. This is the sign-up page: https://e621.net/user/signup

"By creating an account, you are agreeing to the terms of service. Remember, you must wait at least a week to upload posts or comment, and three days to edit posts to prevent spamming. Editing a post counts as changing the tags, parent ID, rating, or source."

People should be reading these rules the moment they sign up, they're practically thrown in your face.

Suggested Feature 1: Sets/pools organization.

Currently they aren't organized at all, and it sucks. I think that it's high time they have their own ratings and tags. Currently, it's rather difficult to find pools that contains only mlp (inpool:true mlp gets a result when you have to go through hundreds of pages of same comic to find something else. I don't want to search for pages, I want to search for pools. I want to have organized view like this.) It's even worse when you want to search for SFW comics. Even if you get page during inpool:true search there always can be explicit page earlier or later.

Really, tags and rating for whole pools/sets are needed. It could be done automatically (Pool rating is the same as the most explicit page. Tags are union of all pages' tags.) or manually.

I'm using pools as examples because there are few public sets now, but it would be problem also for sets in the future.

Suggested feature 2: Better forum search.

I tried to search on forum where the full rule about gay tag was mentioned before. Searching for "gay" gives hundreds of results where gay word was used at least once. It's not good result. This page is not helpful at all. I don't know how/if can I search for what's in topic, or can I filter results to Tags and Wiki category.

Either I suck and searching or forum is too big and search options too limited.

Sub-forums for feature requests and bug reports

We currently have a bug report thread and a feature request thread

It would be nice if we had a sub-forum for bug reports and a sub-forum for feature requests.
This way, we could have one post per bug report / feature request, instead of one big forum post with interleaved discussion threads.

Munkelzahn said:
Sub-forums for feature requests and bug reports

We currently have a bug report thread and a feature request thread

It would be nice if we had a sub-forum for bug reports and a sub-forum for feature requests.
This way, we could have one post per bug report / feature request, instead of one big forum post with interleaved discussion threads.

Sub-forum for alias/implication suggestions would also be nice.

Be able to Accept or Deny/Block Set requests.....this is needed.

We really need a way to deny or block set maintainer requests.

I recently got forced to be a maintainer in the "Renamon covered in cum" set. https://e621.net/set/show/207

It seems there is no way to remove myself or deny it, I rather not be forced to be in sets like this.

Can we have a way to deny or block requests like this?

https://e621.net/forum/show/84638?page=1

it'd be cool if the blacklist were disregarded while viewing favorites, because i've favorited one or two things that fell under my blacklist

Warning message when someone else is already using an image as an avatar.

Not particularly important but it would be nice.

1. Ability to quickly revert changes in sets just like in pools.
It would be useful when you make bad judgment in making one person maintainer, or make mistake in mass adding to sets.

2. Option to order images in set by date when they were added to it.
I don't see it in a cheatsheet and I think it could be useful.

New members must wait <x days> before they can FFD

According to this, new members must wait up to a week before doing all kinds of things: http://e621.net/help/users

This should include flagging posts for deletion.
Reason: some people register new accounts just to flag something for deletion.
IMHO 2 weeks would be a good length for the waiting period.

I've also submitted this feature request here: http://bugs.ouroboros.ws/view.php?id=108
(From now on, I'll submit all bug reports / feature requests here and on the Mantis tracker)

Wolframite said:
Warning message when someone else is already using an image as an avatar.

Not particularly important but it would be nice.

Why

Wolframite said:
Warning message when someone else is already using an image as an avatar.

Not particularly important but it would be nice.

I've suggested something similar, and it got refused: http://bugs.ouroboros.ws/view.php?id=106

Munkelzahn said:
I've suggested something similar, and it got refused: http://bugs.ouroboros.ws/view.php?id=106

Oh right, thanks anyway.

Renard_Queenston said:
Why

Mainly just because it feels impolite to use an avatar that someone else is already using, and vice-versa.

Wolframite said:
Warning message when someone else is already using an image as an avatar.

Not particularly important but it would be nice.

I was thinking about this the other day, but had a different variation of it:

I thought it might be even better if there was a list next to the image of who currently has it as their avatar. Could be right under the "favorited by:" list which is already next to the image. Wouldn't be much different than the favorited by list actually. But the advantages would be huge:

• could see if there's 2 or 25 other people currently using it. To some people this matters more than others.

• could check to see if any of them are active. Just a notification that someone else is using it won't tell you if they actually were banned or haven't been seen in years, or never forum post, etc.

• would make it less of a shock when you see the same image being used by someone else, because the information was always available.

• would prevent accidentally taking one being used by an admin and then having an ohgodwtfhaveidone heart attack later on. (lol)

I think some users won't care, so to them it won't matter much. But for those people that do, a feature like this could be much needed information. Right now it's just a guessing game: with no way of knowing who you'd be associated with or if you're likely to see it somewhere else. So for those that care, this might be a simple sanity saver. Just a suggestion.

ETA: just to clarify, I don't think avatars should be limited to x set number of users. I think if dozens want to share it that's perfectly fine. I just think people should be able to make the decision in as informed a way as possible so that if it matters to them, they can tailor their avatar choices according to their own ideas on the subject. Information is gold.

I don't think warning boxes or only allowing one user to use an avatar is the right way to go about this. A small link to "Users with this avatar" below the set avatar button on posts could be good, though. It doesn't insist that you need a unique avatar, but leaves a choice to the user whether they want to avoid having the same avatar as somebody else.

There's a thread over here which has gotten derailed over reminding them to secure permission. But it also contained a site suggestion to add the site's mission statement to a clearly visible place on the main page or so. So that it would help to properly brand the site's purpose/goals and dispel misconceptions. One of the main points they brought up was good:

Kida said:
...I don't feel like enough people realize this site is for archiving, not for strictly uploading one's content like on dA or FA...because the original artist thought I was "stealing their art" [for uploading it]...[which] shows that not many people are really aware of the purpose of this site. ...[once they] realized what the site was, they didn't have a problem with their art being here and even considered thanking me.

Now if an artist was approached right, this might have gotten cleared up beforehand while securing permission. That's true. But I think the issue and suggestion is a lot broader than that.

Because most of our traffic is not one-on-one solicited, we constantly have people coming here and assuming what we're supposed to be about based on the first couple hundred random images they came across. And that can cause problems. A concise 1-2 sentence mission statement in a banner or prominent can't-miss-it place on each page might go a long ways towards clearing up a lot of ongoing issues we tend to have on this site. (It could even link to the existing sticky thread for more details.) By clarifying what this site is "meant" for it would ease a lot of issues:

• It would cut down on erroneous "this doesn't belong here I'm gonna FFD" misunderstandings. Because when people are used to seeing what the site is meant for succinctly stated on any page, they are a lot less likely to get the wrong ideas about the site in the first place.

• It would cut down on the never-ending confusion over whether we're supposed to be exclusively furry, or exclusively art, or exclusively porn. None of which are correct. I'm sure everyone is sick of hearing it constantly come back up again. And a short mission statement at the top of each page would get more traffic than a thousand forum posts on the subject.

• It also helps people coming to the site for the first time who are trying to decide how to categorize this site in their minds. Is it a furry site? Is it an archive? Is it a porn site? Is it just a random image dump their work will get lost in? Is it like 4chan? Having a clear site purpose in a highly visible place would dispel a multitude of misconceptions about what it is we even do here.

Even after artists have been asked for permission, they may want to verify what they've been told by viewing the site themselves. Which is great. But do we want whatever is randomly scattered on the main page to solely represent what the site is meant for? Just looking at what's recently been uploaded can send mixed signals sometimes.

Or do we want a concise and clear statement somewhere prominent (like a site banner) that lets members, artists and lurkers alike know what the site's main goals are. The more easily they can find what the site's mission statement and purpose is, the smoother it will be to ease concerns or clear up any misconceptions they may have. It's cutting down on guesswork by visitors of every type. And a site mission statement/definition/identity/stated purpose/etc can be just a line of text, nothing fancy. Just something which helps first impressions, is highly visible from even the main page and doesn't rely on waiting until they work their way over to the forums to see the sticky (if they ever do).

And of course uploaders should always ask for permission from the artists. I know it's an important concern. But that shouldn't overshadow the rest of their suggestion. The idea is a good one that I think would benefit the site in a lot more ways than they brought up. Which is why I'm posting the actual suggestion to the official suggestion thread, along with a link back and any points I could add to it. I thought it deserved due consideration.

I would adore a shorthand to link to a parent post dynamically without cementing the post-number (via ''parent'':URL), so that the link won't break or be wrong if it changes.

Just something like {parent} or somesuch would be great. Ideally it would work both in an image-post's description and also in the discussion for it.

Peekaboo said:
I would LOVE a button or option to turn off/on blacklist. It'd be great when tagging since I would otherwise not see the posts with content I have blacklisted.

If you click on the "hidden" text (on the left upper corner) you can make visible one by one every thing you have in your blacklist. Though maybe one click button would be nice if you have long blacklist.

What IMO would be more useful is button for switching temporarily switching blacklist to whitelist. So after click previously blacklisted pictures on page would be visible and everything other not.

Artists as numbers only

Summary:
Instead of having artist tags that are linked to artist wikis, e621 should use only the number of the artist wiki.
So instead of tagging a post with "kacey", you'd tag it with "artist#701"

Implementation:
Since most people won't know the internal number of the artist they want to tag, there should be an option to search for an artist when you're in tag edit mode.
It would work just like the current artist search:
https://e621.net/artist/index (search by name or by URL)

The only difference for artist wikis would be:
Instead of a "Name" field and an "Other Names" field, there'd only be a "Names" field.
The first name in this field becomes the artist name that e621 displays in a post's tag list, under the heading "Artists" (see below).

In tag edit mode, the "artist tag" would be displayed as "artist#701".
Outside of tag edit mode, the "artist tag" would be displayed as "kacey" (first entry in the artist wiki's "Names" field).

Problems this would solve:
- If an artist changes their name, you don't have to set up an alias or create a new artist and retag all of their posts.
Just add their new name to the beginning of the "Names" field in their wiki.
- No more naming conflicts: if an artist has the same name as a common tag, or a character, or another artist, this often leads to confusion (for example, people changing the tag type from artist to character and back again)
- If you don't know the "right" name for the artist (someone on Pixiv, for example) => just use whatever appears appropriate (like the pixiv username, which is in English), and someone else can change it later if it's incorrect

I've also submitted a feature request on the Mantis bug tracker:
http://bugs.ouroboros.ws/view.php?id=117

Peekaboo said:
I'm not sure if I'm the only one on this, but... I think we need to cut down on some of the privileges that new accounts have after its creation. Well, not cut down on, but increase the amount of days/weeks it takes for a new user to use functions like creating threads on the forum, uploading on the site, commenting etc.

I've mostly thought about this since we've been flooded with smegheads here on the site lately.

We can handle it just fine and don't want to discourage new people from joining because they won't be able to do anything for a week or month anyway.

Improvements to Reverse Image Search

- Position: the RIS links are currently in the lower left corner below "Related Posts", where they're easy for newbies to overlook. They should be either above or below the image itself. IMHO the best place would be between the image and the "Edit | Respond | Download | Full Size" bar.

- Open in new tab: when you click on one of the RIS links, e621 opens it in the current tab. IMHO, e621 should open the RIS in a new tab (just like clicking on a source URL).

- Horizontal RIS bar: if the RIS links are above or below the image, then IMHO they should be arranged like this:
Reverse Image Search: All | Google | TinEye | SauceNao | IQDB | Inkbunny

- Inkbunny search: IB lets you search by a pic's MD5 sum. While this isn't as good as a true RIS, it can still be useful. Unfortunately, it's tedious:
1) Copy the link to the full-sized image on e621
2) Go to the IB search page, tick the "MD5 Hash" checkbox
3) Paste the link from step 1 into the search bar and remove anything except the raw file name

I've also submitted this feature request on the Mantis tracker:
http://bugs.ouroboros.ws/view.php?id=118

edit:
Posts where the source is a direct link to a Deviantart, like post #382503:
http://fc07.deviantart.net/fs71/f/2010/339/a/8/dancing_bleakcat_by_bleakcat-d34afnd.jpg

"Google Search by Image" doesn't always find them, but googling for the image name almost always does. So what I do is take the raw file name:
dancing_bleakcat_by_bleakcat-d34afnd.jpg
and extract the individual words:
dancing bleakcat bleakcat

It'd be great if there were an option to do this automatically:
1) Extract the individual words from a direct Deviantart link
2) Put "deviantart" in front of them
3) Google the resulting string

Improvement to Home Page: Avatar Selection/Rotation Locking

I like a small selection of the avatars (Mostly eSix, Hexerade, and Mirage) and would like to have a rotation of just those small few avatars. Mostly though, I just want to stop Dylan from popping up occasionally because I'm tired of arma-dick popping up in my face. >_>; Made a thread about this because I vaguely remembered hthere being a way to at least stop it from cycling, and was recommended to make a feature request for it, so here it is.

An 'or' search function would also be nice... like, "female OR straight" would show any picture that either has females or has females and males in a straight situation, or "-female male OR gay" which would show any picture without females that has males or is gay (so would show solo males too) or "female rabbit OR dog" that shows any rabbit or dog that is female. Thus if a picture has at least one of the OR tags, it'll be listed, rather than having to match every tag individually. Unsure of how to format- a simple _OR_ gate between the two tags might suffice, might not.

123easy said:
An 'or' search function would also be nice... like, "female OR straight" would show any picture that either has females or has females and males in a straight situation, or "-female male OR gay" which would show any picture without females that has males or is gay (so would show solo males too) or "female rabbit OR dog" that shows any rabbit or dog that is female. Thus if a picture has at least one of the OR tags, it'll be listed, rather than having to match every tag individually. Unsure of how to format- a simple _OR_ gate between the two tags might suffice, might not.

~female ~straight is female or straight, though I'm unsure how well can you combine it with other things, like negation.

Gilda_The_Gryphon said:
~female ~straight is female or straight, though I'm unsure how well can you combine it with other things, like negation.

! Thank you for that information. That's a search function modifier I was not aware of prior (obviously, lol). That's quite useful; Can't believe I missed that in the tag's help post.

Tag editing: submit only the diffs

It's currently possible for people to overwrite each other's tag edits.
Example:
1) User A goes into tag edit mode
2) User B edits the tags on the same post
3) User A submits his tag changes

User B's tag changes will be overwritten by those of User A.

Solution:
Only submit the actual tag changes, i.e. tag removals and tag additions. Or, in the case of sources, the source changes.

I've also reported this feature request on the Mantis tracker:
http://bugs.ouroboros.ws/view.php?id=119

That sounds like a great idea, Munkelzahn.

Option to sort comment searches by date of last comment on that post, rather than just by date of the searched comment

Reason: There is no way of knowing if there has been a reply to a comment I've made on a post without actually looking at that post.

Tag Change Reasons

When you change the tags on a post, it'd be nice if you could optionally give a reason for the changes (like you can in a revision control system).

I've also submitted this feature request on the Mantis tracker:
http://bugs.ouroboros.ws/view.php?id=122

Munkelzahn said:
Tag Change Reasons

When you change the tags on a post, it'd be nice if you could optionally give a reason for the changes (like you can in a revision control system).

I feel that would juts cause tag wars on the reasons on herm and dickgirl images.

Munkelzahn said:
Tag Change Reasons

When you change the tags on a post, it'd be nice if you could optionally give a reason for the changes (like you can in a revision control system).

I've also submitted this feature request on the Mantis tracker:
http://bugs.ouroboros.ws/view.php?id=122

I submitted this months ago, and they never said anything about it. Here's hoping you have better luck, because this would be a very useful feature. There's times when I've changed a tag because I didn't see it in the image, and then someone commented and pointed out this small little thing in the corner; having it for every tag changed/removed/added after the initial upload tags would be helpful.

Conker said:
I feel that would juts cause tag wars on the reasons on herm and dickgirl images.

Or help prevent them.

corgi_bread said:

Or help prevent them.

Until you see people putting the reason of tag changings as "felt like it" gaaaaaaay" or "THIS IS MY FUCKING OC AND SHES A HERM NOT A DICKGIRL FUCKING TAG IT RIGHT FAGGOTS!" and "STOP CHANGING THE FUCKING TAG, IM RIGHT YOU ARE WRONG HUGGING DICKS ISNT GAY!" or the back & forth of "this is a dickgirl" "no this is a herm" "no thats a dic-....ect ect" Or people who change tags and leave no reason at all....or even worse when someone adds 12 tags and only mentions the reason for 1 tag change. It seems more of a pain and more trouble then its worth. The tag wars would move from the comment section onto the tag reason change log.

Conker said:
Until you see people putting the reason of tag changings as "felt like it" gaaaaaaay" or "THIS IS MY FUCKING OC AND SHES A HERM NOT A DICKGIRL FUCKING TAG IT RIGHT FAGGOTS!" and "STOP CHANGING THE FUCKING TAG, IM RIGHT YOU ARE WRONG HUGGING DICKS ISNT GAY!" or the back & forth of "this is a dickgirl" "no this is a herm" "no thats a dic-....ect ect" Or people who change tags and leave no reason at all....or even worse when someone adds 12 tags and only mentions the reason for 1 tag change. It seems more of a pain and more trouble then its worth. The tag wars would move from the comment section onto the tag reason change log.

This.

Just use the comments section if need be.

I also will use the description when someone uses it first to make a line about "stop changing mah tags, hur dur!"

Edit: For example, post #383237

Conker said:
long paragraph with words, some capitalized, some not

And if people are acting like that in the tag reasons section, then they'll have a banstick shoved up their ass, just like if they were acting like that in the comments.

corgi_bread said:
And if people are acting like that in the tag reasons section, then they'll have a banstick shoved up their ass, just like if they were acting like that in the comments.

Then that makes a reason change log for tags pointless then. Also the users I see doing this arent even banned.

I think that placing tagging disputes in separate place then comments is a good idea. Comments are not connected to the tag change itself, and can be downvoted so they can be missed more easily.

Conker said:
Then that makes a reason change log for tags pointless then. Also the users I see doing this arent even banned.

You have to report them, and include examples of specific post(s) when it occurs in the report.

A feature request: Have a option to set blacklisted images to appear under the icon "blacklist" so they show up under normal posts with the rest of the images but still have the blacklist icon over them.

I am not sure if this has been brought up before, and if so I am sorry for re-proposing it.

PROPOSAL: That a favorite also votes the image up 1.

REASON: I have noticed for years now that nearly every image has more favorites than up-votes. This just seems asinine to me. If you favorite it, then you are also essentially saying it is a good piece of art. I will be honest though, even I have not taken the time to go back to the image after favoriting it to up-vote the image every time, but I try.

I just think it would be easier and make the rating system just a bit more useful.

How about a feature that lets you organize a pool the same way you put pictures in a set. This would make for easier organizing if a post is missed when creating the pool.

Queen_Tyr'ahnee said:
How about a feature that lets you organize a pool the same way you put pictures in a set. This would make for easier organizing if a post is missed when creating the pool.

I don't know how sets work (never made one, yet -- proof) but that already exists. When vieweing a pool, there's a link at the top that says "Order".
Then, on that page, you can write a number corresponding to, say, the page of the comic.

Xch3l said:
I don't know how sets work (never made one, yet -- proof) but that already exists. When vieweing a pool, there's a link at the top that says "Order".
Then, on that page, you can write a number corresponding to, say, the page of the comic.

Thanks for pointing that out, I never saw that. Now I feel dumb. :I

How about when adding/removing tags:
One person can add tags normally, just like it currently is.
But to remove tags (e.i. all this herm/dickgirl bullshit) it gets treated like an ffd? Like it gets approved by a higher up and what not, instead of just adding a tagging decription.
Like a reason behind the tag.
That or you could set this system for certain "problematic" tags that tend to change just out of the blue. Mainly genders and such.
Like this would only apply to members, privy and above could just ignore this stuff.

Moon_Moon said:
How about when adding/removing tags:
One person can add tags normally, just like it currently is.
But to remove tags (e.i. all this herm/dickgirl bullshit) it gets treated like an ffd? Like it gets approved by a higher up and what not, instead of just adding a tagging decription.
Like a reason behind the tag.
That or you could set this system for certain "problematic" tags that tend to change just out of the blue. Mainly genders and such.
Like this would only apply to members, privy and above could just ignore this stuff.

The admins have trouble handling tickets and regular FFD's sometimes, and you want to dump a backlog THAT BIG on them? It sounds good in theory, but in practice it would make wayyyy more work than it fixes.

corgi_bread said:
The admins have trouble handling tickets and regular FFD's sometimes, and you want to dump a backlog THAT BIG on them? It sounds good in theory, but in practice it would make wayyyy more work than it fixes.

Agreed. It would just be miles of paperwork over every little change. Besides, a lot of those tag vandals get caught and handled through other methods. So something this extensive isn't necessary and would just grind regular tagging to a halt.

corgi_bread said:
The admins have trouble handling tickets and regular FFD's sometimes, and you want to dump a backlog THAT BIG on them? It sounds good in theory, but in practice it would make wayyyy more work than it fixes.

It could be more than just the admins doing that work, we could make privys pull their weight.

Also, this would only be a part when gender tags are changed. all other tags would be fine.

Admins should be able to lock specific tags on a specific post. This would prevent "tag tampering" I guess you might call it. (changing dickgirl to herm and back and forth)

I also have pretty simple request.
Please make a (show all in blacklist)/(hide all in blacklist) type toggle. Something under the "Hidden" on the left when searching.
Just temporarly turn off/on the blacklist for the current search just like you would with a single entry.

How about option to make some tags impossible to apply directly? They could be only added by implication or alias? It would, for example, help keeping bronies for tagging fim tag to their OCs, or force users to use more detailed tags. Like <color>_hair instead of hair, or <language>_text instead of text.

Wolframite said:
Option to sort comment searches by date of last comment on that post, rather than just by date of the searched comment

Reason: There is no way of knowing if there has been a reply to a comment I've made on a post without actually looking at that post.

2nded.

FEATURE IDEA: I would really love a personal aliasing or tag-shortcut setup of some kind. I find myself often wanting to put in requests for aliases for things that only I'd use or on typos that only I'd make. If personal shortcuts were a thing for the site, I could go ahead and enter all the petnames I want for artists whose stuff I upload and it wouldn't bother or confuse anybody.

Pro: The main advantage community-wise (other than reducing tags with/which are typos) would be that groups of tags could be added to relevant pictures swiftly especially for the curators on this site who kinda go on crusades to get certain subsets of things tagged up correctly. They'd be able to proceed without waiting days/weeks/hours for the mods to approve an alias or implication they might be leveraging, and in addition they may have a specific strategy which they'd apply in a small set of cases where an implication or such might be overly broad across the whole site.

Some examples:

If someone got the drop on a bunch of new Pokémon or other show characters who suddenly have r34 of them, they wouldn't have to wait for the implication to go through for things to be right right-away.

...Say we knew the trainer's name for the thing so we'd have like m:Mr_Granite (or whatever the syntax for a user-macro would be... it could simply be implicit without a new syntax just like site-wide implications or aliases are) expand to "geodude_(pokemon) pokemon Mr_Granite_(pokemon) rock_type_(pokemon)" or whatever. Obviously this would be with some new creature and not one of the original 150 in a real case.

Pro: As a personal macro, this could also help prevent confusion with characters from other shows also called Mr Granite. A throwaway example would be searching for chaos, which returns I guess chaotic scenes, the goopy bad guy Chaos from the Sonic dreamcast game, some Discord, and some warhammer 40k stuff.

Pro: If I'm a fan of some character with a commonly held name, it would be easy for me to go ahead and mask that name so I don't cause collisions accidentally. Say if I like Trunks from DBZ and post any art I find of him scoring with furry characters, I'd have trunks just map to trunks_(dragonball_z) or similar rather than the swim item.

Any macro/shortcut (or whatever it is this would get called) would map one 'user macro' type tag to one or more actual tagging keywords e.g. say my entering 'Forces' would map over to 'Forceswerwolf.'

TL;DR: It would reduce errors and increase tagging efficiency to let users define their own little shortcuts which would let them easily apply one (or more) site/community-recognized tag(s) to an image post.

ragswift said:
FEATURE IDEA: I would really love a personal aliasing or tag-shortcut setup of some kind. I find myself often wanting to put in requests for aliases for things that only I'd use or on typos that only I'd make.

Aliasing things is not for personal use.

Conker said:
Aliasing things is not for personal use.

Which is exactly why he would like that as a seperate, personal feature to make tagging quicker by giving personal shortcuts to long tags.

ragswift said:
FEATURE IDEA: I would really love a personal aliasing or tag-shortcut setup of some kind.

(...)

...Say we knew the trainer's name for the thing so we'd have like m:Mr_Granite (or whatever the syntax for a user-macro would be... it could simply be implicit without a new syntax just like site-wide implications or aliases are)

I really like this idea. However either it has to have special syntax (like m:Macro), or be done by modifying tags textarea content by separate button. IMO otherwise it could by really error prone, especially if user set shortcut same as existing alias/implication and forgot about it.

---

BTW
Feature request: Automatically remove trailing whitespace from alias/implication suggestions.

It's really not that hard to make that mistake, and I don't believe that any valid tag should end with space. See forum #84564 for example.

NotMeNotYou said:
Which is exactly why he would like that as a seperate, personal feature to make tagging quicker by giving personal shortcuts to long tags.

But we already have this feature, I use it all the time to use common things I tag with a list on this site. Its part of the fav tag feature (not sure what its called), but it can give you a list of tags you add so no mistakes. You should know what I am talking about...

Conker said:
But we already have this feature, I use it all the time to use common things I tag with a list on this site. Its part of the fav tag feature (not sure what its called), but it can give you a list of tags you add so no mistakes. You should know what I am talking about...

No this is not the same, but it could be integrated with favorite tag feature. It could work like that:
you define personal implication:

normalRainbowDash -> rainbow_dash_(mlp) rainbow_hair
 blue_fur blue_feathers purple_eyes feral pegasus

then by just one click on normalRainbowDash it would add all seven tags to the picture. And it could be extended to removing tags, so defining

ponyImpl -> pony horse equine 

and clicking on it when highlighted would remove all three tags with one click.

Gilda_The_Gryphon said:
No this is not the same, but it could be integrated with favorite tag feature. It could work like that:
you define personal implication:

normalRainbowDash -> rainbow_dash_(mlp) rainbow_hair
 blue_fur blue_feathers purple_eyes feral pegasus

then by just one click on normalRainbowDash it would add all seven tags to the picture. And it could be extended to removing tags, so defining

ponyImpl -> pony horse equine 

and clicking on it when highlighted would remove all three tags with one click.

Yet if we left it up to users to make these alias....it would be abused -.- or someone claiming they put the tag dog but fuckable_fox was aliased without them knowing.

Conker said:
Yet if we left it up to users to make these alias....it would be abused -.- or someone claiming they put the tag dog but fuckable_fox was aliased without them knowing.

That's why this aliases are suggested to be private. Nobody else is affected by your favorite tags list, nobody else is affected by your blacklist, and nobody else would be affected by your personal shortcuts.

And, as you probably know, clicking on favorite tags only adds/removes tags from textarea. It does not submit changes. The same thing would be with shortcuts.

Gilda_The_Gryphon said:
I really like this idea. However either it has to have special syntax (like m:Macro), or be done by modifying tags textarea content by separate button. IMO otherwise it could by really error prone, especially if user set shortcut same as existing alias/implication and forgot about it.

You're right that the user's tag-transformations/custom tags being able to mask public tags could be a problem if the UI didn't tell them "oh hey your input has triggered use one of your custom tags right now." This would allow masking if users were brave enough. Maybe the system could just alert them if a tag they've chosen is already in use. We might just need a syntax or a tickbox by 'save/submit/upload' to ignore custom tags to get around that. Here's what I suggest...

Quick example:
Assume normally my custom tag for Twilight expands to [Twilight_Sparkle mlp fim pony unicorn]. If I were uploading something I found that takes place during the twilight time of day, say, I could just put it as "Twilight" (with quotes or something) which would bypass my own defined transformations and go straight to the public alias-and-implication mapping.

This user-defined tag-transformation could be either JS or AJAX processed.

It occurred to me that public implications and aliases could be expanded actively as well, BUT having both mapping layers applying still in order (private first, then public) but almost instantaneously fast might be too confusing to users.
One or two UI elements that could toggle expansion/conversion/mapping on and off could clear this process up. Then tagging could work like the "preview" button that we enjoy here on the forums. It would be nice but there is still always just hitting EDIT after you've made the wrong assumption about the tags you've entered.

As Gilda suggested, this system could work instead just by making the "recent tags" section customizable (probably give them a different column or color/font to differentiate) with little commands basically, which could just be clicked to add or remove tags. I would personally prefer keyboard support for its speed, but buttons in addition could totally help people understand how to use such a feature.

Suggestion: in the comments screen] I would love it if we could have modes for both:

• "view only comment threads on images you have added"
• "view only comment threads in which you've participated"

Having the second would be absolutely lovely. I don't know if folks would banter too much if encouraged this way, but if we were afraid of that, why enable comments on images in the first place, right?

Question/suggestion: Is there a reason that mentions) can't be used in image post threads like they can in blips (or can they)? Enabling this (esp. if easier) would also serve to address the issue some.

I should be dry of ideas for a while after this I think B:

Suggestion: disliked/de-ranking syntax -- a softer minus

Sometimes I'm afraid I might miss border-cases on searches I've run by being too selective with omitting things [tag1 -tagWhichIsTypicallyUndesirableGivenTag1]. Other booru-y sites allow spoiler-covers to be added, but this then requires like 3 extra clicks to see something that there's only a small chance of liking, which almost seems backwards; I'd rather click 3 times to get an image I'm confident I will like.

The blacklist silently kills off pictures which you maybe would really enjoy; it's hard to know for sure sometimes. Blacklist should ofcourse be kept for things that are totally squicksville for folks and that they are quite sure they never want to go see.

A good partner to this might be a box in the user-settings which would tweak ordering of results (e.g. it'd always show monochrome pictures last for someone, say).
This could also have its own separate syntax for individual searches where the rules are more context sensitive (for example if you typically dislike seeing giraffes giving oral... or something, then you would just apply this whenever you wanted giraffes).

So instead of all that, I'd really like a syntax such as the following:

tag1 --tagWhichIsTypicallyUndesirableGivenTag1 --anotherTagWhichIsTypicallyUndesirableGivenTag1

This way, users could sift through the very last of the only-potentially-desirable stuff at the end of the pages that the search returned all at once, namely any images which match the first tag but also contain the other --'d tags would be kicked to the last set of pages of the search. The cream would rise to the top, and they also wouldn't miss anything that was outright hidden via blacklist.

ragswift said:
I should be dry of ideas for a while after this I think B:

Suggestion: disliked/de-ranking syntax -- a softer minus

Sometimes I'm afraid I might miss border-cases on searches I've run by being too selective with omitting things [tag1 -tagWhichIsTypicallyUndesirableGivenTag1]. Other booru-y sites allow spoiler-covers to be added, but this then requires like 3 extra clicks to see something that there's only a small chance of liking, which almost seems backwards; I'd rather click 3 times to get an image I'm confident I will like.

The blacklist silently kills off pictures which you maybe would really enjoy; it's hard to know for sure sometimes. Blacklist should ofcourse be kept for things that are totally squicksville for folks and that they are quite sure they never want to go see.

A good partner to this might be a box in the user-settings which would tweak ordering of results (e.g. it'd always show monochrome pictures last for someone, say).
This could also have its own separate syntax for individual searches where the rules are more context sensitive (for example if you typically dislike seeing giraffes giving oral... or something, then you would just apply this whenever you wanted giraffes).

So instead of all that, I'd really like a syntax such as the following:

tag1 --tagWhichIsTypicallyUndesirableGivenTag1 --anotherTagWhichIsTypicallyUndesirableGivenTag1

This way, users could sift through the very last of the only-potentially-desirable stuff at the end of the pages that the search returned all at once, namely any images which match the first tag but also contain the other --'d tags would be kicked to the last set of pages of the search. The cream would rise to the top, and they also wouldn't miss anything that was outright hidden via blacklist.

stupid hypothetical example

• I would like to find furries who are skateboarding.
• I typically find helmets, kneepads, and shoes to be uncool in this context
• Despite this, I have totally seen some depictions of skateboarding furries who have safety gear (or footwear) to be so supremely awesome that I don't want to completely negate these from my search... I just probably want to deal with a finer level of sifting at the very tail end of results.

Let's say I query on [skateboarding --knee-pads --helmet --elbow-pads --shoes]

Let's say there are 3 images for the tag skateboarding with the following tags:

• {skateboarding andrewsarchus knee-pads elbow-pads male}
• {skateboarding salmon mohawk kickflip ambiguous_gender}
• {skateboarding tapir helmet female piercings}

I would then get them in the following order:

1. {skateboarding salmon mohawk kickflip ambiguous_gender} (has no strikes)
2. {skateboarding tapir helmet female piercings} (one strike)
3. {skateboarding andrewsarchus knee-pads elbow-pads male} (two strikes)

I would REALLY like to see this go in. I don't generally like Pony art, but some of it is just really good, and I like good art regardless of what the content is.

Requested feature: Proper, resizeable textbox when answering tickets and making deletion reasons.

Why it would be useful: So I can proofread what I typoed in with sentences longer than 63 characters (which is nothing).

Requested feature: A Handled By column on the ticket page.
Why it would be useful: Yes.

Requested feature: A box that marks all other pms on the page, so its easier to hide about 2 years of pms without clicking them all.
Why it would be useful: Saves time and every pm/email system has this useful feature.

Inline with the above:

Requested feature: Feature to autohide outgoing record created/removed/edited and ticket/namechange spam.

Why it would be useful: Makes it much easier to find important mails if the pages aren't cluttered with those and hiding them manually is tedious.

Responses to those shouldn't be hidden though and manual responses to those responses should also stay.

Warning when you upload DNP artists

When you upload a pic with a DNP artist tag, e621 automatically adds the avoid_posting tag (via an implication).

If a post has the avoid_posting tag (via an implicaton, obviously), it'd be nice if e621 didn't upload it right away. Instead, it should display a warning page, asking the user if they really want to upload the pic.

Q: Why not just refuse to upload the pic?
A: Because some artists aren't "completely" DNP.

https://e621.net/wiki/show?title=avoid_posting
Conditional Do Not Post:
- Jameless (only commissions are DNP)
- Jollyjack / Phillip M Jackson (Commercial work is DNP)
- MoodyFerret ("hardcore/weird/fetishy" stuff, everything else is fine)
- Nekomata_Neko (Neko-Maya is still ok to post)
- Tanidareal (only explicit artwork; safe/questionable still ok)

I've also submitted this feature request on the Mantis tracker:
http://bugs.ouroboros.ws/view.php?id=125

Requested feature: Edit or delete our own tickets

Why it'd be useful: I left a comment report about something that evidently got handled while I was typing it up. I did check the ticket list before submitting the report, but I presume that it had been reported as User Complaint. (Which I can't see at my user level.) So my report is completely redundant now, and I wish I could delete it...