Not sure if bug or feature but:
Requested feature: Make pool import respect the set: metatag.

Why it would be useful: Not everyone puts comics/etc in pools and some do semi-batched uploads leading to fragmentation and difficulty to use the import tool efficiently on its own. This is especially apparent if no artist and since the arttags: metatag never works for me there's no real alternative but to add the posts one by one. Of course a pool mode would be easier in the first place. Then there's the pool: metatag... But still...

Requested feature: Signatures in comments, posts, etc.

Why it would be useful: Could be used by people who commonly send people to certain pages to make it so you don't have to copy-paste the same code over and over again, and just say "Click the TWYS link in my sig", etc. Personally, for me, it could be used to link to a thread in which I explain why I'm so fucked up in the head, and that anything I say should not be taken personally, because I probably don't actually mean it.

ShylokVakarian said:
Requested feature: Signatures in comments, posts, etc.

Why it would be useful: Could be used by people who commonly send people to certain pages to make it so you don't have to copy-paste the same code over and over again, and just say "Click the TWYS link in my sig", etc. Personally, for me, it could be used to link to a thread in which I explain why I'm so fucked up in the head, and that anything I say should not be taken personally, because I probably don't actually mean it.

You can just use the space on your userpage for that.

requested feature: being able to search posts via the number of tags it posesses

Why it would be useful: itd be an effective way to find images with low amounts of tags and fix them, and also allow people to see images with a large amount of tags as a guidance on how to do it.

how to implement it: prefferably itd have multiple applications such as sort:tagcountup (ascending) and sort:tagcountdown(descending), along with "tagcount=?, tagcount>? and tagcount<?"

just a thought

Languedoc said:
requested feature: being able to search posts via the number of tags it posesses

Why it would be useful: itd be an effective way to find images with low amounts of tags and fix them, and also allow people to see images with a large amount of tags as a guidance on how to do it.

how to implement it: prefferably itd have multiple applications such as sort:tagcountup (ascending) and sort:tagcountdown(descending), along with "tagcount=?, tagcount>? and tagcount<?"

just a thought

There is one:

order:tagcount
order:tagcount_asc

Kida said:
You can just use the space on your userpage for that.

Yes, but not everybody will check userpages.

Requested feature: Add text to the suggest implication page about character -> species implications not working well.

Why it would be useful: It would cut down on such suggestions.

Why it wouldn't: It could be confusing, and it's not like we get many in the first place.

Requested feature: Display thread title on every on page of a forum thread

Why it would be useful: Mostly useful if you're a multi-tasker and either open several forum threads at once, or leave threads open for later review. (I know the html title show the thread title, but with many open tabs that often becomes more or less unreadable).

Chessax said:
(I know the html title show the thread title, but with many open tabs that often becomes more or less unreadable).

If you hover your mouse over the tab it should show the title in a tooltip. Or you could get Firefox and have a different set of problems. *runs*

Chessax said:
Requested feature: Display thread title on every on page of a forum thread

Why it would be useful: Mostly useful if you're a multi-tasker and either open several forum threads at once, or leave threads open for later review. (I know the html title show the thread title, but with many open tabs that often becomes more or less unreadable).

Reasons why I still use Opera 12: #3: Native tab stacking

Unless you don't wanna change your browser, of course. Yeah, I know my version is way too outdated but it can still kick

Requested feature:
You shouldn't be able to upvote your own comments.
Or downvote them, for that matter.

Why it would be useful:
Nobody would downvote their own comments.
And upvoting your own comments is like cheating.

Xch3l said:
Reasons why I still use Opera 12: #3: Native tab stacking

Unless you don't wanna change your browser, of course. Yeah, I know my version is way too outdated but it can still kick

Opera 12 still works for you? Goddamnit, it quit on me, so I had to switch to Firefox.

Requested feature: Add a "Comments on deleted inferior" section to posts that have been deleted in favor of a larger resolution. That, or just move the comments from the inferior to the superior.

Why it would be useful: Too many good comments are lost this way. Prime examples include #736560 and #706439

BismuthGalaxy said:
Requested feature: Add a "Comments on deleted inferior" section to posts that have been deleted in favor of a larger resolution. That, or just move the comments from the inferior to the superior.

Why it would be useful: Too many good comments are lost this way. Prime examples include #736560 and #706439

I think comments on deleted posts (but not destroyed posts) should be accessible. Moving them to parent posts could create big problems.

Request: Link to stats page on sitemap

https://e621.net/static/more
https://e621.net/stats

Lance_Armstrong said:
Request: Link to stats page on sitemap

https://e621.net/static/more
https://e621.net/stats

Nice catch. Added for next update. :)

BismuthGalaxy said:
Requested feature: Add a "Comments on deleted inferior" section to posts that have been deleted in favor of a larger resolution. That, or just move the comments from the inferior to the superior.

My vote for this. The way things are now, uploading a better version has a nasty price: all comments are effectively deleted. That's just wrong. Uploading a better version should be a free action for the uploader.

Lance_Armstrong said:
I think comments on deleted posts (but not destroyed posts) should be accessible. Moving them to parent posts could create big problems.

The best way to make them accessible is to show them under the better image. Linking the deleted image kind of defies the purpose of deleting.

There should be some indication that the comment comes from a different post, but other than that, I'd say just mix the comments together and sort by date.

hslugs said:
There should be some indication that the comment comes from a different post, but other than that, I'd say just mix the comments together and sort by date.

And if that is not good enough of a reason to keep comments, then hide them initially, that way no one can complain.

Requested Features
Tag Locks (admin feature only)
Tag Lock Reason (also admin only)

Why it'd be useful
Admins will get the final say, for real
Confused taggers will be told why an admin has locked a certain tag to a certain picture
Tagwars will be resolved more easily

xXMAGIKzMushroomXx said:
Requested Feature:
Ability to Crop pictures to use as avatar.
Why it would be useful:
So that pictures with a large background for example, can be adjusted to just focus on the character, or so that you could use a picture of someone from a frame in a comic.

I second this, I had a picture deleted but after looking through the site cant find the rule against uploading cropped images. Not looking to complain, just agreeing with the feature! :3

1. Go to Set: Edit Posts
2. One or more of the post ids you add has been deleted, but has a parent post. Transfer on Delete option is enabled.
3. (Feature) Deleted posts are replaced with parent posts if found.
4. (Feature) When the "Posts updated" success message is displayed, display a new line in the green box for each swap:

Posts updated
post #749841 was added instead of post #749912
post #748315 was added instead of post #687164
...

Why I need this feature:

I copy from "Data" section on this set, reverse the order of the lines, and paste it into Edit Posts. I only spotted the deletion because the number I wrote manually and the number of posts in the set after updating did not match.

Maybe this'll get shot down, but... please make it possible for members to enable the use of 'Edit tag script' and 'Apply tag script' modes.

My reasoning is that since members can still access 'Edit posts' mode, it probably wouldn't be too hard to emulate the tag script behavior with a user script or browser extension. Why make the unnecessary work for someone to write such a script?

I can understand not wanting people to have access to tag scripts before they know how to use them correctly, but the ability could be off by default with some slightly sneaky way to enable it.

Could we get a note on the Flag for Deletion menu stating:

"Do not flag images for deletion for an unfitting reason! If the reason you want something deleted for is not on the list then DO NOT flag it!"

or at least a link to the wiki page?

This would probably cut back on irrelevant or poor quality posts being flagged.

Could you add a DText code similar to [[tag]] which links to the wiki but also shows an up-to-date count of how many posts the tag appears on? Would be useful for those threads with lots of alias/implication suggestions.

Would look something like [[[cute]]] -> cute (25193)

Other possible syntax: [[tag]]#, ((tag)), #tag#

Requesting extensions of date keyword feature:

• yesterday and decade keywords (easy)
• decade is for future proofing, because there is still 16 months before the oldest post #14 is 10 years old
• range syntax (harder)

Described here:

https://e621.net/forum/show/156271

Requested feature:
New flag reason: manually upscaled version of parent post and/or version at the source

Why it would be useful:
Because people upload shitty upscales.
I could use "This post is a duplicate or an inferior version of another post (smaller, lower quality, etc.)"
but the new flag reason would make it clear why the upscaled version is inferior, even if it's got more pixels and more kilobytes.

Munkelzahn said:
Requested feature:
New flag reason: manually upscaled version of parent post and/or version at the source

+1. It's depressing.

Requested feature:
Blacklist by score, e.g. score:<10

Why it would be useful:
Can't currently blacklist like this (as far as I know) and it would be helpful to hide posts that aren't well-liked.

Blind_Guardian said:
Requested feature:
Blacklist by score, e.g. score:<10

Why it would be useful:
Can't currently blacklist like this (as far as I know) and it would be helpful to hide posts that aren't well-liked.

+1. It would definitely help users who want to do this sort of blacklist.

Currently you would have to do something like this:

score:-11
score:-12
score:-13
score:-14
score:-15
score:-16
etc

which, of course, is very time consuming and annoying.

IIRC the problem was that the blacklist doesn't allow the use of range syntax but I'm not 100% on that.

Requested feature:
Allow posts to have multiple parents

Why it would be useful:
post #752910 is a composite of:
- post #752917
- post #752918

post #751666 is a composite of:
- post #543674
- post #543671

Requested feature:
Preview of animated posts
(Take a still image from the animation, or use its parent post + an "animated" banner.)

Why it would be useful:
Lets users preview animated posts. Don't have to load them to see what's inside.

Requested feature:
Option to ignore my blacklist for items I have in favorites.

Why it would be useful:
There are a few images with blacklisted tags in my favorites, due to my disagreement with some content tags on these images, they are hidden by default.

Requested feature:
Deleting a pool requires one to enter a reason, which is then send as a dmail to the creator of said pool.
The given reason could also show up in the Moderator actions.

Why it would be useful:
Simply creates an option for us to keep track of why a pool got deleted, as well as it allows us to explain to the creator of the pool why their pool got deleted, thus benefits the user and us in the long run.

Pandra said:
Requested feature:
Option to ignore my blacklist for items I have in favorites.

Why it would be useful:
There are a few images with blacklisted tags in my favorites, due to my disagreement with some content tags on these images, they are hidden by default.

The good news is that this is already available, sort of. When you're viewing your favorites page (https://e621.net/post?tags=fav%3APandra), on the left side of the page there's the search field, under that is the 'Mode' drop down menu, and under that will be a clickable link labeled "Blacklist" which will allow you to un-hide any images on that page of favorites which are currently blocked by your blacklist. It only shows up when an image on that page is currently being blacklisted, so it's an easy way to check if your blacklist is active on that page of favorites or not and how many images are hidden. Clicking on it will show you which blacklist entry the image fell under so that you know what to expect. And you can click that link to temporarily unhide it. Clicking it again re-hides it. Refreshing the page will also re-hide because it blacklists by default whenever you load a page.

There's a chance you already knew this and were asking for a setting to tell your blacklist to not activate whenever you're looking at your favorites page, but still continue to work everywhere else. I'm not sure if that will ever be a feature or not. But at least using this method, you can easily view the few favorites that are being hidden by your blacklist with just a few clicks. It's not perfect but for the meantime it does get close.

Requested Feature
A way for users to rate and sort pools.

Why it would be useful
There are some kinds of pools that users do or don't want to see, maybe no image sets or only comics. This is already a feature in posts, being able to search by rating, so why not pools?

Requested Feature
Option to download images from thumbnail (i.e. view native image from its URL).

Why it would be useful
Viewing full images in comics can take a while, and downloading them directly from their pool would make this much faster.

Zest said:
Requested Feature
Option to download images from thumbnail (i.e. view native image from its URL).

Why it would be useful
Viewing full images in comics can take a while, and downloading them directly from their pool would make this much faster.

A "download pool" button would be amazing for this.

Welcome note request
Persian: !خوش آمدید

Glutamate said:
Welcome note request
Persian: !خوش آمدید

but e621 is illegal in iran!

Munkelzahn said:
but e621 is illegal in iran!

Uh oh, @alirezatm hasn't posted in 4 days.

Munkelzahn said:
but e621 is illegal in iran!

God bless VPNs :]

Lance_Armstrong said:
Uh oh, @alirezatm hasn't posted in 4 days.

Thanks to my asshole mother who found my furry porn stash I'm banned from using teh internetz

aurel said:

@ali
oh dear,
hope she liked what she saw
hope it was not drawn by nezumi
hopefully the situation wont get worse

Let's hope so dear

aurel said:
wait... you... printed your porn stash? :o

wanted to see how it looks like as a magazine :< :|

If your family were muslim, would you be dead now?

Munkelzahn said:
If your family were muslim, would you be dead now?

Probably

alirezatm said:
Thanks to my asshole mother who found my furry porn stash I'm banned from using teh internetz

Just use favorites bruh. Or a set.

Lance_Armstrong said:
Just use favorites bruh. Or a set.

> over 44,000 favorites.
> View Posts (2106)

pls

parasprite said:
> over 44,000 favorites.
> View Posts (2106)

pls

It gets bigger: https://e621.net/set?name=&shortname=&username=&order=postcount

Lance_Armstrong said:
It gets bigger: https://e621.net/set?name=&shortname=&username=&order=postcount

https://e621.net/set?user_id=33842 :/

parasprite said:
https://e621.net/set?user_id=33842 :/

Heh, what are u tryna say bout my massive pair of sets?

Requested feature: Re-order items in a pool

Why it would be useful:As best as I can tell, users are unable to retroactivly re-order posts within a pool without creating a new pool.

As can be seen here: https://e621.net/pool/show/6991 : I have uploaded previously missing sections of a comic that was originally posted by another user. As it stands, I have no way to properly re-order the images so that the pair that I uploaded fall in the right place.

As a side note, if proper procedure is simply to delete the old pool and make a new one, then I shall do so. I just need to be sure that that's actually what I'm supposed to do.

schaghticokekid said:
Requested feature: Re-order items in a pool

Why it would be useful:As best as I can tell, users are unable to retroactivly re-order posts within a pool without creating a new pool.

https://e621.net/pool/order/6991

The link is "Order" on the pool's page: https://e621.net/pool/show/6991

Ctrl+F to look for "Order" if you don't see it

Lance_Armstrong said:
https://e621.net/pool/order/6991

The link is "Order" on the pool's page: https://e621.net/pool/show/6991

Ctrl+F to look for "Order" if you don't see it

holy shit, of course it was that obvious... much appreciated my mono-testicle'd friend.

Requested feature: Let users change their default sorting method.
Why it would be useful: I have typed order:favcount far too many times, and I'm sure other users face the same problem.

leomole said:
Requested feature: Let users change their default sorting method.
Why it would be useful: I have typed order:favcount far too many times, and I'm sure other users face the same problem.

I'd recommend bookmarking order:favcount or sticking it on your profile for convenience.

That being said, a dropdown menu might be workable, but the menu will have to be trimmed a bit first (there's 10 ways to sort, but having them all in there is a bit messy).

I don't think that a dropdown with ten options would be too clunky for the settings page.

Snowy said:
I don't think that a dropdown with ten options would be too clunky for the settings page.

I was thinking more by the search bar, but the settings page would probably be fine.

Though a few like order:set would be kind of useless for the most part.

Requested feature: Hotkey for editing
Why it would be useful: I often edit hundreds of posts in a sitting, and scrolling (a different amount every time!) down to the Edit function is a real PITA. Hitting the E key, for example, to go directly to editing would save a ton of time and effort. The Edit Posts mode is okay, but I generally want to see all of a post's tags at once, and I don't want to be sent to the top of the page.

Requested feature: Vertical resize option
Why it would be useful: I suspect that users often want to view an entire image, without having to scroll down. A vertical resize option is a natural complement to the existing horizontal resize option.

Sorry for making so many posts. I hope some of them are useful to e621!

Requested feature: Add

or

to beginning of submit_quick_edit() function in at least Edit Posts mode.

Why it would be useful: If you do multiple tag edits and don't keep closing the "Post updated" notice, you don't know if the latest tag edit was successful. This can cause you to skip tag edits.

Requested feature:

When this textarea is made visible, the cursor position in the textarea should change to 0, and a space should be inserted.

This action activates it:

Why it would be useful: If you do multiple tag edits in Edit Posts mode, the cursor will sometimes end up in the middle of a tag. With the above solution you can begin typing your tags immediately. It doesn't matter how many spaces end up in the textarea since the server ignores extra whitespace. Only one space will be added by the code below.

How to do it:

The code is located at https://e621.net/javascripts/application-min.js

This should add the space:

to

Take your pick on how to set the cursor position to zero:

http://stackoverflow.com/questions/499126/jquery-set-cursor-position-in-text-area

It will end up looking like $("post_tags").setCursorPosition(0); with the needed function added as a prototype somewhere.

More on the above two suggestions.

1. This is noticeable on slower connections when the tag edit does not complete within 1 to 2 seconds.

2. The textarea cursor stays in the last known position in at least Firefox. This is because the code reuses the same textarea repeatedly. If you type some tags and the cursor is at position 11 when you click Update, the next image's tags you open will have the cursor at position 11. If the cursor position is in the middle of a tag, you can't immediately start typing your tags. The seconds you lose add up over time.

Changing both could make Edit Posts tag editing up to 20% faster.

Requested feature 3:

Add the following style:

This would override cols="60". You can drag the corner of the textarea to resize it but making it the full width of the screen by default would make tag editing faster.

Unlike the other 2 suggestions this could have compatibility concerns with older browsers.

I already gave it a larger default size that's already live on e9, but what you've laid out here looks promising and seems to fix some nagging issues I've had with using the edit mode in the past. Honestly I assumed most people didn't know about that mode. :x

I'll plan to get this added.

Is there any way to jump to page 'X'? :) I thought it would be clicking the "..." between the page numbers but that doesn't work. I presume it's there somewhere but I just haven't found it, hence not labeling this as a request. It kinda sucks having to click on page after page just to reach the middle. I did look around but I couldn't find it, so sorry if it does exist and I'm just wasting time >_<

H0rnyOmega said:
Is there any way to jump to page 'X'? :) I thought it would be clicking the "..." between the page numbers but that doesn't work. I presume it's there somewhere but I just haven't found it, hence not labeling this as a request. It kinda sucks having to click on page after page just to reach the middle. I did look around but I couldn't find it, so sorry if it does exist and I'm just wasting time >_<

You'll need to do it in the browser. Once you search your bar will look something like this:

https://e621.net/post/index/1/rating:safe

The /1/ indicates the page number you are viewing. To get to, say, page 19, change it to:

https://e621.net/post/index/19/rating:safe

I hope that helps.

DragonFox69 said:
You'll need to do it in the browser. Once you search your bar will look something like this:

https://e621.net/post/index/1/rating:safe

The /1/ indicates the page number you are viewing. To get to, say, page 19, change it to:

https://e621.net/post/index/19/rating:safe

I hope that helps.

Didn't think of that :) Thanks for the help!

H0rnyOmega said:
Didn't think of that :) Thanks for the help!

Anytime! :)

Requested feature: A setting that restricts viewing of a user's favorites, uploads, sets, etc. to those who have an account on the website.

Why it would be useful: I believe this feature would be useful to provide privacy and peace of mind if one uses the same username elsewhere on the internet. I love this community, don't get me wrong; the simultaneous titillation of my funny bone and lower bone is my favorite part of this site. Unfortunately, I'm twisted - twisted and ashamed.

Requested feature:
1) Only allow valid URLs in the Source field.
2) Change "Source" to "Source URLs".

Why it would be useful:
1) https://e621.net/post/index/1/hassource:true%20-source:http <-- 227 pages
2) So people know that you have to use URLs, and that you can use more than one (up to 5)

Requested feature: A search option to exclude every tag that implies a specified tag. (e.g. the search "hair not:hair" or "hair -implies:hair" would return everything tagged hair, but not brown_hair, long_hair, hair_over_eye, etc.)

Why it would be useful: It would allow users (maybe only above member status) to apply more specific tags to posts. It would provide a workaround for broken searches like "disney copytags:1" which don't return the expected results. It would allow users to find tags which should, but do not currently, imply another tag.

SaimonPSmith said:
It would provide a workaround for broken searches like "disney copytags:1" which don't return the expected results.

I'll start a job for fixing the copytags at the very least. I do like your idea though.

Munkelzahn said:
Requested feature:
1) Only allow valid URLs in the Source field.
2) Change "Source" to "Source URLs".

Why it would be useful:
1) https://e621.net/post/index/1/hassource:true%20-source:http <-- 227 pages
2) So people know that you have to use URLs, and that you can use more than one (up to 5)

#1 is part of an ongoing fix up that still needs a lot of work.

#2 is a good idea, I'll push that now.

Edit: Something like this?