Requested Feature: Have the forums show when a post is deleted or edited.

Why it would be useful: So that ordinary users can know who's bumping ancient forum threads by either editing posts or making new posts and then deleting them.

ikdind said:
Requested Feature: Have the forums show when a post is deleted or edited.

Why it would be useful: So that ordinary users can know who's bumping ancient forum threads by either editing posts or making new posts and then deleting them.

I think you're talking about that Ollie Canal post, amirite?

xLuna said:
I think you're talking about that Ollie Canal post, amirite?

Saw that too.

ikdind said:
Requested Feature: Have the forums show when a post is deleted or edited.

Why it would be useful: So that ordinary users can know who's bumping ancient forum threads by either editing posts or making new posts and then deleting them.

You already can see that here

ikdind said:
Requested Feature: Have the forums show when a post is deleted or edited.

Why it would be useful: So that ordinary users can know who's bumping ancient forum threads by either editing posts or making new posts and then deleting them.

Already fixed the problem in the next update, threads will no longer be bumped when a post is deleted inside it.

Rainbow_Slash said:
You already can see that here

Well, there is that, but I guess I also just don't believe in the idea that something posted to the forums should be completely deletable except under disciplinary circumstances. At least leave a "this reply was deleted by the author".

But the original request was motivated by a feeling of annoyance when those forum threads got bumped by... I guess it was cetetic? Dare I ask what cetetic was so afraid would be discovered in 3-year-old forum posts that anyone might actually care about?

No surprise, Google cached it all back in April.

ThenIThought said:
Requested feature: The post history should display the source URL history (I assume that information is kept, if not, start keeping it as well).

Why it would be useful: Recovering from vandalism, see who's contributing useful metadata... the same reasons we can see the parent post, rating, tags field histories.

If there is some way to see this, it's not accessible enough.

tony311 said:
There isn't yet, but it's on our todo list.

For all it's worth, seconding this as well

titaniachkt said:
For all it's worth, seconding this as well

Thirded. I always wondered about that, but forgot to mention it.

Source history is coming in the next update :)

tony311 said:
Source history is coming in the next update :)

<3

tony311 said:
Source history is coming in the next update :)

<3 <3

Requested feature: Make it so when a repost gets deleted (The new or old image) Votes and/or Tags get transferred from the deleted version, to the kept version.

Why it would be useful: there might be some tags in deleted version, that wasn't posted on the kept repost.

Votes on the deleted post should still count, since they still hold the opinion of the voters.

slyroon said:
Requested feature: Make it so when a repost gets deleted (The new or old image) Votes and/or Tags get transferred from the deleted version, to the kept version.

Why it would be useful: there might be some tags in deleted version, that wasn't posted on the kept repost.

Votes on the deleted post should still count, since they still hold the opinion of the voters.

So you're saying you want everything that gets deleted that has a parent post to transfer votes and tags? What if it isn't an exact repost? The system doesn't presently distinguish exact reposts with anything else that gets deleted.

ippiki_ookami said:
So you're saying you want everything that gets deleted that has a parent post to transfer votes and tags? What if it isn't an exact repost? The system doesn't presently distinguish exact reposts with anything else that gets deleted.

Well i guess, it could work the same way as when, favorites gets moved from the deleted image to the new one.

Pool comments, useful if you want to comment on a whole comic instead of a single post

megusta said:
Pool comments, useful if you want to comment on a whole comic instead of a single post

This sounds good. Except if pool gets deleted, maybe.

Requested Feature: Add a popular_by_year category to the popularity search thinger.

Useful Because: e621 has been up for at least some years now, I don't see why not if we have one by month and by day :)

Dunno if this is do-able in some other way already. I is new to internets. Most of my time is spent outside when not fapping to e621 :)

Requested feature: The ability to search tags by whether or not they have an entry on the wiki.

Why it would be useful: Makes it easier to add entries to the wiki, which better clarifies how tags should be used and leads to better tagging, yeah?

Some suggestions

And a question

Requested Feature: Setting a view count on every post.

Why it would be useful: Provides informational, if not useful data that can be used to track the number of views, or the popularity (although the number of views does not always correspond to a post's popularity) of a post. It can also be used as a tool for searching by view count, i.e., searching "order:viewcount" or "order:viewcount_asc".

slyroon said:
Requested feature: When a tag has reached a numbered limit (example: 100). It should be locked in whatever type it is currently in and only moderators/admins should be able to change it after that.

I believe this already exists in a slightly different form. IIRC, priv+ can change tag types past the limit, and it's much lower than 100.

Requested feature: Search by multiple tags with the same meta... i.e. "fav:userA fav:userB" returns the images favorited by both users...

Why useful: For finding shared favorite artists, etc...

I have a feeling this kinda breaks the tag architecture apart, but you could work with it if you had some kind of invisible tags for each image? Thus, favoriting an image would mean to add a "fav:jadesro" tag that is invisible to the image's tag list, but still searchable...

Jadesro said:
Requested feature: Search by multiple tags with the same meta... i.e. "fav:userA fav:userB" returns the images favorited by both users...

I already asked for this. It probably won't happen until various other coding happens.

Requested feature: Enable voting for flagged images.

Why useful: Bad FFDs. If it gets deleted score doesn't matter anyway.

Adrian_Blazevic said:
Requested feature: Enable voting for flagged images.

Why useful: Bad FFDs. If it gets deleted score doesn't matter anyway.

Fixed in the next update.

Requested feature: Enemies list
Why useful: I'm honestly losing track at this rate.

Actually requested feature: Search filter options (ie. exclude posts with specified tags)
Why useful: Allows for better results without having to update my blacklist for a single search. (eg. searching for 'male' but exclude posts with 'straight' would yield gay, male solos and others not tagged properly. perfect. :3)

elad said:
Requested feature: Enemies list
Why useful: I'm honestly losing track at this rate.

Actually requested feature: Search filter options (ie. exclude posts with specified tags)
Why useful: Allows for better results without having to update my blacklist for a single search. (eg. searching for 'male' but exclude posts with 'straight' would yield gay, male solos and others not tagged properly. perfect. :3)

Are.. Are you drunk? What kind of request is this?
Enemies list? is this.. what is this..

anyhow, that's already implimented (and has been for years) just type -TAGNAME in the search, and BAM you got yourself a spicy posta pasta

Aurali said:
anyhow, that's already implimented (and has been for years) just type -TAGNAME in the search, and BAM you got yourself a spicy posta pasta

Even Mama Luigi approves!!

Anyway, what I really came for: whine about my day request a feature
Requested feature: Feeds for (almost) every category of the site (besides posts)
Why *blah blah* useful: I know it's on the API, but for Norm Normalguy it would be more accessible than writing a program to get, for example, a list of updated threads, or new tags added, or look for recently blocked users with comical reasons (yes, I have read some)

Requested Feature: Dtext syntax creating a link to a user's profile. For example: Furry Fanatic (without using a URL link).

Why it would be useful: Provides a quick and simple way to create a link to a user's profile page in text.

Snowy said:
Request: the ability to change your vote on a post
Why this would be useful: Misclicks happen.

-1.

Crap! I meant +1. D:

Request: Thumbnail images for Flash and other non-image files.
Why: Because it's difficult to pick out the file you're looking for from a grid of identical white boxes with "DOWNLOAD" on them.

RenaKunisaki said:
Request: Thumbnail images for Flash and other non-image files.
Why: Because it's difficult to pick out the file you're looking for from a grid of identical white boxes with "DOWNLOAD" on them.

I've heard this suggestion before, and I think that since most flashes start off for a split second with a blank screen or something along those lines, it would be useless.

Raiden_Gekkou said:
I've heard this suggestion before, and I think that since most flashes start off for a split second with a blank screen or something along those lines, it would be useless.

There's no good solution.

You could allow users to upload a separate "screenshot" taken somewhere in the flash, and that would then be used as a thumbnail. Problems:
- most people would be too lazy to include a screenshot
- some people would be too stupid tech-illiterate to take a screenshot of a flash, and even if they could, they'd probably upload it as a BMP
- trolls would upload screenshots totally unrelated to the flash

You could add a new field on the upload page, specifically for flashes, where you could specify how far into the flash you want e621 to got before automatically taking a "screenshot" to be displayed as a thumbnail. Problems:
- again, most people would be too lazy to put a meaningful value into this field
- wouldn't really work with interactive flashes

I liked the original "flash" thumb because it put a dotted border around the last one you visited

Automatic screenshot thumbnails would still be better than the fields of blank flash thumbs when you're trying to find a specific flash. The first time you're clicking on a flash, it probably won't be helpful, but after that it would be.

Munkelzahn said:
There's no good solution.

You could allow users to upload a separate "screenshot" taken somewhere in the flash, and that would then be used as a thumbnail. Problems:
- most people would be too lazy to include a screenshot
- some people would be too stupid tech-illiterate to take a screenshot of a flash, and even if they could, they'd probably upload it as a BMP
- trolls would upload screenshots totally unrelated to the flash

You could add a new field on the upload page, specifically for flashes, where you could specify how far into the flash you want e621 to got before automatically taking a "screenshot" to be displayed as a thumbnail. Problems:
- again, most people would be too lazy to put a meaningful value into this field
- wouldn't really work with interactive flashes

Well, hopefully the thumbnails would be treated similarly to tags. If you notice one is missing, add it. If it's wrong, flag it, and if it's an obvious troll, the uploader can be dealt with as any troll would.

I'm not sure how feasible automatic screenshots would be. If you can detect load screens, any time after them should be fine, even for interactive flash; it just has to give a rough preview to differentiate it from others. Since the entire file is already locally available, loading should only take a second, so maybe you can just screenshot after 2 seconds... again, if you notice a bad thumbnail, replace it.

As for uploading BMPs, surely the software should be clever enough to either convert them to PNG or reject them outright? That's a separate issue.

Requested Feature: The ability to sort posts, users, etc. by update time and an update timestamp for everything that can be updated.

Requested Feature: The ability to bulk fetch favorites and tag history

Useful Because: makes syncing quicker

People should get notified per mail if their avatar gets deleted.
It's only fair.

Munkelzahn said:
People should get notified per mail if their avatar gets deleted.
It's only fair.

No.

Your avatar will say "deleted" instead of being there, which would make a notification redundant.

Rainbow_Slash said:
Requested feature: A button to turn on/off the blacklist

Why it would be useful: When doing a tagging project it would help if you could turn off the blacklist and not just clear it every time first

Seconding this; it does become slightly monotonous having to deselect each tag individually after 10 pages or so
One could always remove the entire blacklist as an alternative, but that seems to defeat the purpose of having one

Requested feature: Add metatags and the like, such as pool:1234, *background, etc. to the blacklist and be able to negate them in searches

Why it would be useful: Help with blacklisting certain things and make searching more specific.

Requested Feature: Locking old threads after a time (3 weeks or so)
Why It Would Be Useful: To avoid derpy necros.

Blaziken said:
Requested Feature: Locking old threads after a time (3 weeks or so)
Why It Would Be Useful: To avoid derpy necros.

No

tony311 said:
No

Yes

Munkelzahn said:
Yes

nah

Requested feature: Have a link next to artists name on the avoid_posting that leads to there take down request

Why it would be useful: So users can see why an artist is on the avoid_posting list

I've got two, I hope that's okay.

Requested Feature 1: Having a RES sort of thing where you wouldn't have to type out the HTML, but you'd only have to press a button. See:

http://i.imgur.com/daMsT.png

Why it'd be useful: It would make commenting a lot easier.

~~~

Requested feature 2: So, I heard a couple months ago that having a blacklist that worked as if you had typed all of the tags in the negative into the search bar wouldn't work because it'd put too much strain on the website. So, this gave me an idea: what if you gave the user 3 slots to put in tags that they really want blacklisted so that the page doesn't get tiny if it's blacklisted. Like, I have the female tag blacklisted, and it'd be nice to have the site auto-search "-female" so I'd get to see double the posts on a single page. Again, the user would only get to do this with 3 (or so) tags so there'd be little to no strain on the server.

Why this would be userful: It'd make searching a lot easier and more convenient.

SpaceWhale said:
I've got two, I hope that's okay.

Requested Feature 1: Having a RES sort of thing where you wouldn't have to type out the HTML, but you'd only have to press a button. See:

http://i.imgur.com/daMsT.png

Why it'd be useful: It would make commenting a lot easier.

I have these: http://i1246.photobucket.com/albums/gg609/xch3l/bar.png Though they don't work as I wanted, but they're usable

slyroon said:
So users can see why an artist is on the avoid_posting list

An Enumerated and Exhaustive List of Why Artists are on the Avoid Posting List:
1. They asked to be put there.

Takedown requests don't factor into it.

slyroon said:
Requested feature: Have a link next to artists name on the avoid_posting that leads to there take down request

Why it would be useful: So users can see why an artist is on the avoid_posting list

I do like this idea, actually, but as Snowy said, really the only reason they're on it is because they asked to be placed on it. At that point the only purpose I could see linking to their takedown request serving is to "prove" that they asked to be put on the list, which seems kind of unnecessary to me. Should we do it anyways though?

Char said:
I do like this idea, actually, but as Snowy said, really the only reason they're on it is because they asked to be placed on it. At that point the only purpose I could see linking to their takedown request serving is to "prove" that they asked to be put on the list, which seems kind of unnecessary to me. Should we do it anyways though?

No, because there isn't guaranteed to be a takedown request for every artist that's implied to avoid_posting. And even then, it's not an exact 1:1 ratio; maybe there's multiple takedowns for one artist, maybe there's none, maybe there is one but it's a different spelling or a different alias of their name. So it would be impractical to "find" the takedown that resulted in the avoid_posting tag.

Please have e621 keep a list of all FFD requests, even those that have already been processed.
Each FFD request could be marked as "approved", "rejected" or "pending".

I realize that this feature is far from essential, but it would be very entertaining to browse the list. It would also help to educate new users about what's a valid FFD reason and what isn't.

Requested feature: A google-esque "Did you mean...?" when somebody types in a tag that isn't associated with any images.

Why this would be useful: It'd help people find images faster if they're typing quickly and misspell a word.

SpaceWhale said:
Requested feature: A google-esque "Did you mean...?" when somebody types in a tag that isn't associated with any images.

Why this would be useful: It'd help people find images faster if they're typing quickly and misspell a word.

That would be very useful, but Id imagine very hard to implement.

Rainbow_Slash said:
That would be very useful, but Id imagine very hard to implement.

I'm no programmer, but I'd imagine that if Google was able to implement it with no problems then it can't be too difficult.

SpaceWhale said:
I'm no programmer, but I'd imagine that if Google was able to implement it with no problems then it can't be too difficult.

Nah, e6 is fine

SpaceWhale said:
I'm no programmer, but I'd imagine that if Google was able to implement it with no problems then it can't be too difficult.

Yeah, but Google's put many years of work and watching how people use the search into that system (although that also accounts for why certain words are treated as the same thing, like 4 and four).

SpaceWhale said:
Requested feature: A google-esque "Did you mean...?" when somebody types in a tag that isn't associated with any images.

There's something similar to this on yande.re and sankakuplex (super NSFW), but they use different builds

titaniachkt said:
There's something similar to this on yande.re and sankakuplex (super NSFW), but they use different builds

Well, yande.re seems to be using cookies to return a list of recently searched tags along with their post index. I suppose as long as they keep it to 1000-2000 results then it only adds 20KB-40KB to the page. Then as the user types in something to search for, it's running a series of regexes for potential matches against the recent tags list.

It's not anything too nifty, like BK-Trees or whatever this damn-near mystical shit is, but it could help if a person can only remember part of a tag name. I'm not really sure how many people struggle to spell "scalie", "canine", or whatnot, so I'm not sure how useful this specific technique will be to e621, but I can totally see how it's useful on a more general hentai site where someone might want to search for kono_minikuku_mo_utsukushii_sekai.

I couldn't be arsed to delve into sankaku complex's javascript to determine how they're doing it, but from the delay between typing and suggestions I'd guess they're calling into a server-side script and it's impossible to know what they're doing.

SpaceWhale said:
I'm no programmer, but I'd imagine that if Google was able to implement it with no problems then it can't be too difficult.

1: How do you know that Google was able to implement it with no problems?
2: Why do you assume that "if google can do it, it can't be hard"? Google is a large corporation with tens of thousands of very smart employees. Search is a core area of their business. "Google can do it" doesn't mean that it's easy to do.

Snowy said:
1: How do you know that Google was able to implement it with no problems?
2: Why do you assume that "if google can do it, it can't be hard"? Google is a large corporation with tens of thousands of very smart employees. Search is a core area of their business. "Google can do it" doesn't mean that it's easy to do.

Whiy not? If Google can do a barrel roll I can do too.
-----
Requested feature: Make this thread a subforum

Why it would be useful: Make this thread more organized separating suggestions and comments. Like these 8 last comments, they could be in SpaceWhale's thread

ikdind said:
but it could help if a person can only remember part of a tag name. I'm not really sure how many people struggle to spell "scalie", "canine", or whatnot, so I'm not sure how useful this specific technique will be to e621, but I can totally see how it's useful on a more general hentai site where someone might want to search for kono_minikuku_mo_utsukushii_sekai]

Did you know that..

If you click on tags, then type: part of a tag followed, or preceded by a *, you can get a list of all tags starting with, ending with, or containg that set of characters...

For example:

can*
-canine
-canine_penis
-candy
-candle
-cane

*can
-scan
-can
-toucan
-trashcan
-native_american

*can*
-canine
-canine_penis
-scan
-arcanine
-african_wild_dog

SnowWolf said:
Did you know that..

If you click on tags, then type: part of a tag followed, or preceded by a *, you can get a list of all tags starting with, ending with, or containg that set of characters...

This also works in the search bar such as *background for example. Also, the "source:" metatag doesn't need a wildcard (asterisk). source:deviantart returns everything with at least deviantart in the source.

Requested feature: Disallow posts with unicode in the private range (U+e000 to U+f8ff, U+f0000 to U+ffffd, U+100000 to U+10fffd). When someone tries to use them, show an error page.

Why it'd be useful:                

ikdind said:
When someone tries to use them, show an error page.

Better yet, show an error *and* a preview of the post, with the offending characters marked in some way. Turning them red might work, but:
- there are colorblind people (who like porn, too!)
- you can use colored text on e621 (Only usable by privileged+)
so if someone posts private Unicode characters formatted as red, the systems fails
then again, that's not very likely
and privileged+ users should know better than to use private Unicode characters, anyway :)

That all seems like a lot of work when we could just say hey please don't use private unicode characters.

Well, Munkelzahn is right when he says in forum #39115:

Munkelzahn said:
You'll never get people to stop using private Unicode characters just by asking.

The fact is, certain irresponsible developers have decided that it's a fun and profitable idea to use private unicode plug-ins to allow users to type what they think are interesting and expressive characters into documents and forms that can then be made public.

Nobody can read these interesting and expressive characters, but why should your average Apple user know, or care? Simply asking them to stop won't help, because they don't have the technical knowledge to discern real unicode from Emoji's (or anyone else's) piles of poo.

And certainly the developers don't care. The user who buys their stuff will then tell their friends to buy and install the unicode package to see these interesting and expressive characters. When these friends do, it's Mission Accomplished. Money in the bank. Abusing an extensible feature for money and profit.

The real people I'm upset at are the developers who make these tools. No doubt these are the same kinds of developers that link into random Windows libraries to call private, unpublished functions, then wonder why their apps have compatibility issues when MS issues a hotfix to a critical security flaw.

It's not like this is an epidemic. If it really gets that bad then it can become a new rule but I don't see it happening.

doorspawn said:
Major (and unlikely) idea.

Request:
Tag each character individually, and allow searching per image or per character.

Why?
Searching for multiple tags often leads to multiple characters each with only some of the tags. This is especially problematic when blacklisting tags.

For example, searching for female -mono_breast can exclude images with 1 normal female and 1 single-breasted one. (Although it seems my example fails as this site has a severe lack of mono-boobed entities).

This could surely be implemented now simply by putting the artist / series name in brackets after the character tag

e.g Amy_rose

becomes

Amy_rose_(sonic_the_hedgehog)

In fact, I've seen some people do this already, so why not simply change the tagging rules for cases where two characters share the same name.

Requested feature: Having gender work like the rating system, so that as well as having to specify explicit, questionable, safe you would have to specify Male, Female Intersex etc, and instead of having go to one or the other by default you would have to click one or the other.

Why it would be useful: Gender would always be tagged correctly by necessity.

therabbidwanker said:
Requested feature: Having gender work like the rating system, so that as well as having to specify explicit, questionable, safe you would have to specify Male, Female Intersex etc, and instead of having go to one or the other by default you would have to click one or the other.

Why it would be useful: Gender would always be tagged correctly by necessity.

not all images have characters in them

ippiki_ookami said:
not all images have characters in them

Fair point.
----
Requested Feature: Having the number of remaining posts you can upload in the upload setion of the site.

Why it would be useful: No need to second guess anymore.

Requested Feature: Blacklist straight from the Tag page. Could be a link on the bar with "List New Help" ect

Useful Because:If I find an artist I don't like, for example, I'd just open the tag page from the "?" link and blacklist it right from there instead of digging into my profile settings and pasting the name.

Munkelzahn said:
Better yet, show an error *and* a preview of the post, with the offending characters marked in some way.

Better yet, make the post but flag it so that only the user who posted it can see it, and nobody else.

Because fuck being helpful.