Topic: (OLD) The Feature Request Thread

Posted under Site Bug Reports & Feature Requests

This topic has been locked.

I was perusing the pool history and just had a idea pop into my head...well several really. DAMN YOU IMAGINATION!!!
Is it possible to set up a sort of (very basic) image carousel?
I can think of a few things this can be used for...though I am not talking about one where it loads the next image after clicking an arrow. No I mean an animated carousel like how the kindle fire works, like a wheel.
Possible uses:
Pools, and sets: both viewing the individual pools at page size image resolution and or when viewing the recent changes. (Heck just having small thumbnails would help with the recent changes pages, make it easier to spot images being added or removed that shouldn't have been)
Same could be said for the page that displays the pool titles, a thumbnail carousel would be nice to see what the comic entails before clicking.
Just a few thoughts bouncing around in my head...

Updated by anonymous

Requested feature: Change the "download" button to present an actual download prompt (via sending Content-Type or Content-Disposition headers) upon left-clicking the link.

Why it would be useful: With the addition of WebM video support (and the possibility of more formats supported in the future), the download link noticeably does things other than "download".

- For images, the "download" button opens the image standalone in the current tab, instead of downloading it.

- For WebM, the file is attempted to be played at a set resolution, with varying successes in different browsers. In Firefox (current stable branch) the user is erroneously presented with a "Video can't be played because the file is corrupt" message, whereas Chrome (current stable branch) displays the video correctly in the current tab as if it was an image instead of downloading it. Obviously Firefox's issue is due to a bug, but even if it worked as in Chrome the behavior is not what the button implies.

- For flash, the flash file is reloaded pseudo-fullscreen (taking up the entire tab), which will disable even shortcuts like CTRL+S once the flash instance has control focus.

So the main concern is that none of these results are an actual download option despite the button being labeled "download", and all the results require additional steps to download the file after left-clicking the link.

Though I suppose this might also require the addition of an "Display Standalone" or "Load In Current Tab" button or something to preserve older behavior. Or rename the existing button to that and add a new "Download" button that sends the download headers or whatever.

EDIT: Thought I saw a typo...

Updated by anonymous

Rydian said:
Requested feature: Change the "download" button to present an actual download prompt (via sending Content-Type or Content-Disposition headers) upon left-clicking the link. (...)

There's an HTML5 attribute for the <a> tag, download, that will force the browser to download the target file instead of displaying it. Though it might have some support issues, mainly with IE and Safari.

BTW, right-clicking on the download link and selecting "save link as" will also do the job.

Updated by anonymous

Request: easy read and night mode color page formats.

Reason: easy read is like a soft yellow, reducing eyestrain.
And night mode would be either red, or black and red. Or black.
Useful for at night less bright, less waking roomies or also eye burn.

Updated by anonymous

Request: Different error message when an alias has been suggested

Reason: Currently, if you suggest an alias or implication that has been suggested, but not approved, yous till get the same message as if the alias was active. This can be very confusing.

Updated by anonymous

Circeus said:
Request: Different error message when an alias has been suggested

Reason: Currently, if you suggest an alias or implication that has been suggested, but not approved, yous till get the same message as if the alias was active. This can be very confusing.

+1 to that, this one drives me crazy. I'd be happy if it just added ?query=x to the URL.

Updated by anonymous

Requested feature: 'Dynamically Resize to 100% browser width'

Why it would be useful: Scrolling a bit to the right would give you the image in full display resolution instead of downscaling to fit the side bar

Also, upscaling smaller images in dynamic-resize mode would be nice

Updated by anonymous

paulapig said:
Requested feature: 'Dynamically Resize to 100% browser width'

Why it would be useful: Scrolling a bit to the right would give you the image in full display resolution instead of downscaling to fit the side bar

I don't know, personally I'd find it annoying if I had to scroll to the right every time I'd like to see the entire post. (I have it set to "Show reduced samples", btw.) So, I'm only giving it a vote if automatic scrolling/positioning is included.

Also, upscaling smaller images in dynamic-resize mode would be nice

Against. Images can be pretty small. But they can also be really small.

Updated by anonymous

Request: Remove the ability to update ones own comments.

Reason: You don't know how many times I wish this where the case when finding creepy comments where the user in question (probably knowing they will get downvoted) up votes all their comments. For me all it takes to hide a comment is a single red vote... But if the owner upvotes then it remains at 0 and visible.

Updated by anonymous

Requested Feature: Follow a tag so you get a message whenever something is tagged with it.

Why it Would be Useful: if you want to see a certain thing but it's only posted rarely, you don't have to manually check every few days.

Updated by anonymous

LEGOEPIC said:
Requested Feature: Follow a tag so you get a message whenever something is tagged with it.

Why it Would be Useful: if you want to see a certain thing but it's only posted rarely, you don't have to manually check every few days.

This isn't exactly what you are talking about, but the site does support Atom feeds: https://e621.net/post/atom?tags=cookie+cat

Atom feeds are designed with news in mind, which means it's easy to set them to periodically check and notify you of new posts. I don't use them myself so I don't have any suggestions for actual readers, but I know they are readily available (some browsers have them built-in). If you're curious, here's an example of a rendered feed using an online reader - link

Esme_Belles said:
Request: Remove the ability to update ones own comments.

Reason: You don't know how many times I wish this where the case when finding creepy comments where the user in question (probably knowing they will get downvoted) up votes all their comments. For me all it takes to hide a comment is a single red vote... But if the owner upvotes then it remains at 0 and visible.

Probably isn't the most reliable way of hiding them. :/

+1 either way.

paulapig said:

Also, upscaling smaller images in dynamic-resize mode would be nice

I'm going to go ahead and say no on this one.

EsalRider said:

Against. Images can be pretty small. But they can also be really small.]

post #63540

Updated by anonymous

LEGOEPIC said:
Requested Feature: Follow a tag so you get a message whenever something is tagged with it.

Why it Would be Useful: if you want to see a certain thing but it's only posted rarely, you don't have to manually check every few days.

eSix Extend can actually do that. If you add a custom link to the UserBar with a URL like /post/index/1/<query>, replacing <query> with whatever you want to search for, the script can check for updates on that search and notify you by displaying the link in italics.

parasprite said:
post #63540

Congratulations, you managed to make me laugh for a good five minutes. Also, I lost :P

Updated by anonymous

EsalRider said:
Against. Images can be pretty small. But they can also be really small.

The obvious answer to that is 'impose a limit on scaling multiplier'. Most images look fine at 200% IMO, even if you have interpolation turned on (default for most browsers). 300% looks fine if you turn interpolation off via CSS, though I suspect some people might disagree with me on that.

Updated by anonymous

parasprite said:
This isn't exactly what you are talking about, but the site does support Atom feeds: https://e621.net/post/atom?tags=cookie+cat

Atom feeds are designed with news in mind, which means it's easy to set them to periodically check and notify you of new posts. I don't use them myself so I don't have any suggestions for actual readers, but I know they are readily available (some browsers have them built-in). If you're curious, here's an example of a rendered feed using an online reader - link

Probably isn't the most reliable way of hiding them. :/

+1 either way.

I'm going to go ahead and say no on this one.

post #63540

The kindle typoed...that wasn't update it was up vote

Updated by anonymous

Requested feature: Mobile friendly sources

Why: Multiple sources are nice, but on a touch only device you can't really mouse over the first to expand the sources without directly clicking the first link, having an option to expand the sources manually would allow the use of all source links.

How: Maybe make the "Source:" clickable to expand the field, or have a ► besides the sources to click/touch.

Updated by anonymous

Requested feature: Prevent the report function from reporting the same thing twice (or up to five times) when there is already an open ticket about the exact same thing (for example a comment).

Why it would be useful: It prevents me from starting to drink when I have 5 different tickets about the exact same comment/forum post/blip in the queue.

Updated by anonymous

Requested feature: Make the ticket answer field a multi-line text field (like the forum post/dmail/comment/blip/description fields) instead of a single-line field with a width shorter than my BD toys are thick.

Why it would be useful: So the ticket answers can have a nice formatting and are able to be spellchecked for more than the last 16 letters that were typed in.

Updated by anonymous

Requested feature: Removed the already filled in "Artist requested removal" in the Post deletion reason on the takedown form, and leave it empty.

Why it would be useful: It turns out that I have the attention span of a goldfish on ecstasy and I forget way too often to alter the reason to mirror the real reason for a takedown request. Having it empty forces me to write one out, thus it's easier to keep it proper.

Updated by anonymous

Requested feature: Add a possibility to favorite pools.
Why it would be useful:
- You don't need to remember all titles of your favorite pools.
- You have all pools you like at one place.

I suggest to favorite a link to the mainsite of the pool as the links that are shown in the pool-search. So you can get directly to the thumbnailsite.

Updated by anonymous

0schi said:
Requested feature: Add a possibility to favorite pools.

There is a trick in the meantime (favoriting pools would be awesome), make a new private set, then put the first image of each pool you'd like to keep into that set. Now you have every pool easily accessible.

Updated by anonymous

NotMeNotYou said:
There is a trick in the meantime (favoriting pools would be awesome), make a new private set, then put the first image of each pool you'd like to keep into that set. Now you have every pool easily accessible.

Okay I did not know about private sets, but until now I did it the same way ^^'
Just didn't like to search through all my favourites :D

Updated by anonymous

Requested Feature: A separate blacklist for site uploads, avatars, and user comments (user comments including forum posts, blips etc)

Why this would be useful: The way it's currently implemented, you have one blacklist that can only be applied to all situations equally, or not at all.
i.e, you can:

  • Blacklist posts only (via tags, metatags etc. This includes user uploads but not user comments, forum posts etc)
  • Blacklist posts and avatars
  • Blacklist posts, avatars, and users (this includes both users and user uploads)

These options are independent of each other- You can't have a separate blacklist for users, a separate list for user posts, and a separate one for avatars.

To illustrate with some examples:

Say we have a site user called Asdf, because I'm too lazy to come up with a real name:

  • Let's say Asdf doesn't like the type of content that ExampleUserA uploads (maybe the quality is consistently poor),
    • they would add user:ExampleUserA to their blacklist, which prevents uploads by ExampleUserA from showing up.

No problems there.
Now, what if there's a person (we'll call them ExampleUserB) whose comments on posts are really intolerable for whatever reason? (Maybe They Type Like This, oR tHiS, OR THIS)

  • Asdf could add that name to their blacklist- user:ExampleUserB and check the Apply blacklisted users to forum posts, comments, Dmails, and blips option, which ensures no more comments from ExampleUserB

Here's where we run into a problem: Since the same blacklist is used for multiple functions at a time, it's not possible to selectively choose what gets blacklisted. i.e.

  • Uploads from ExampleUserA and ExampleUserB are now blacklisted
  • Forum posts, comments, Dmails, and blips from ExampleUserB and ExampleUserA are now blocked

Notice how ExampleUserB's uploads and ExampleUserA's comments etc. are blacklisted, even though that wasn't the intended purpose.

Conclusion: You cannot selectively blacklist users or tags from uploads (or comments etc.)

Note: I haven't included avatars because it's still possible to show/block avatars by adding the post id to the blacklisted tag

* e.g. If you have ExampleTag blacklisted, but still want to see ExampleUserA's avatar (id #123), you can add ExampleTag -id:123
* Conversely, if you don't have ExampleTag blacklisted, but don't like ExampleUserA's avatar, you can add id:123 to your blacklist

Updated by anonymous

Requested Feature:
Sort a user's post comments by score (optionally)
(currently, they're always sorted by date)

Why this would be useful:
So you can see which of your comments have made other people happy, and which ones haven't.

Updated by anonymous

Requested Feature: Allow users to sort their own tag edits history list to show edits which have since been changed by another user at the top.

Why this would be useful: It would aid new users to discover which tags they are using incorrectly and help them learn to use the tagging system more efficiently.

Updated by anonymous

DragonFox69 said:
Why this would be useful: It would aid new users to discover which tags they are using incorrectly and help them learn to use the tagging system more efficiently.

It would also help to spot tag mistakes, abuse, and tag warring.

Updated by anonymous

Requested feature: Change /tag/index API behavior. Make after_id return the tags with the ids closest to the given value instead of acting merely to filter out ids while still otherwise returning tags as determined by order and page.
Why it would be useful: It would make it possible to use after_id to iterate /tag/index more easily and efficiently.

Alternatively, add before_id to /tag/index with the requested behavior so that a change to existing API behavior is not required.

Editted after giving it a little more thought.

Updated by anonymous

Requested feature: If the website recognizes the upload as a flash file, allow for a custom thumbnail.

Why it would be useful: Right now, browsing swf files on here is semi-blind. You only have the submissions scores and mouse-over tags to work with, which is slow and cumbersome...at least IMO :)

Updated by anonymous

Terraraptor said:
Requested feature: If the website recognizes the upload as a flash file, allow for a custom thumbnail.

Why it would be useful: Right now, browsing swf files on here is semi-blind. You only have the submissions scores and mouse-over tags to work with, which is slow and cumbersome...at least IMO :)

This is actually a pretty frequent request and has been on the todo list for quite a while now. We are generally shying away from user-submitted thumbnails due to the potential for abuse/quality control, but automating the process isn't very easy to do because of how flash files are designed.

Still has my +1

Updated by anonymous

Maybe regular users can submit a thumbnail only if there is not one yet and it must be approved?

Updated by anonymous

parasprite said:
This is actually a pretty frequent request and has been on the todo list for quite a while now. We are generally shying away from user-submitted thumbnails due to the potential for abuse/quality control, but automating the process isn't very easy to do because of how flash files are designed.

Still has my +1

Yes. I assumed that to be the case. This is why I narrowed this feature request to only flash files, to at least narrow the exposure to abuse. You still have a self-policing community at-the-ready to downvote and flag any abuse cases.

I think the thumbnail should only be available to the file submitter, done only during the initial submission phase.

Updated by anonymous

Terraraptor said:
Yes. I assumed that to be the case. This is why I narrowed this feature request to only flash files, to at least narrow the exposure to abuse. You still have a self-policing community at-the-ready to downvote and flag any abuse cases.

I think the thumbnail should only be available to the file submitter, done only during the initial submission phase.

animperfectpatsy said:
Maybe regular users can submit a thumbnail only if there is not one yet and it must be approved?

I like this idea. ^

Updated by anonymous

feature: a vote, upload etc counter that floats in the corner of the screen (similar to the "this has been changed, upvote saved etc banner that floats at the top of the screen, but constant).
Maybe show a timer that shows how much time till it refills?

Reason: when I am doing my ticket sweep of comments I tend to try to downvote the really bad ones, I also tend to not keep track of how many I've used.
If this was implemented it would help both uploaders keep track of how many uploads they have left to use and when they can upload more (especially helpful if your doing other stuff or staring at the screen waiting for it to replenish). If it was multi type it would help keep track of comments, comment votes, and post votes. A lot of the time I find a really bad commenter and run out of votes, then wait an hour and click downvote only to get the "can't downvote" banner... so a timer display would be nice.

Updated by anonymous

Requested feature: Tag Justification

Allow non-obvious tags to be attached to an image, and have those be marked with special descriptors. All tags would be considered as "obvious" by default, but could be labeled as, say, "stated" or "previously_established" to indicate that those tags refer to information that is written somewhere on the image or information that was already given at some point in a sequence of images, but isn't made obvious in the current image respectively.

Why it would be useful:
Since the good old "Tag what you see" approach doesn't work for all cases and requires a few exceptions to work at all (namely characters, species, visibility of incest and such), I propose that we begin allowing non-visible or non-obvious tags to be attached to an image with special descriptors that would indicate how said tag is related. This could potentially help reduce the amount of tag in-fighting as well as (provided such info is accessible in search requests) allow users to filter posts where such information was indirectly found (for instance search for vore, but not if previously_established, so only actual, currently happening vore).

Some examples of what I mean

First, we presume that everything about an image is known (as if we were the authors), and that we're meant to be tagging that. We're only using the "justifiers" to indicate that this aspect of the image is debatable depending what you consider as part of the image.Ambiguous: Arguably visible, but can be interpreted in different ways.
post #341527
cuntboy (Can be seen as one, but not what the author intended)
flat-chested (Whether this is a cboy or not, no breasts+vagina)
female <ambiguous> (As mentioned by the author and arguably justified by the content of the picture)Stated: The aspect being tagged is established through text.
post #632248
incest <stated> (Because we only know they're related through dialogue)Implied: Not actually visible, but elements of the image can be used as proof.
post #495727
male/female <implied> (Sexual dismorphism would have it that the shinx is male and the luxio is female) (That's not actually what's intended by the author, but if it were, that's how it would be tagged)Obfuscated: The tagged aspect is twisted in some way so that it can't be tagged literally. Obfuscation can affect the image's rating.
post #152625
bdsm <obfuscated> (This is only "supposed" to represent a wood structure)
nipple_piercing <obfuscated> (Wood structures don't have nipples)post #34693
penis <obfuscated> (due to creative_censorship)
balls <obfuscated>And so on.
Any number of those could be added to that list to cover extra use-cases, those just happen to be the ones I had in mind.

How it could be implemented:
Assuming e621 works with a relational DB where the tag and post tables are linked by a cross-reference table (n:m), one could simply add an optional field for "justifiers" (or however they'd be named) as an integer-field. While tagging an image one would use a special symbol to match a tag with its justifier, not unlike what's currently being done with tag types.

Updated by anonymous

Requested feature: Make anonymous blacklist stats available. A user should be able to search a tag combination (e.g. male solo) and see a count of how many blacklists that combination appears in. If there were some way to see how many blacklists contain one combination of tags but not another, that would be even more helpful. It'd be nice if tag combinations and their counts were browse-able and available in the API as well.

Why it would be useful: Useful in making decisions about changing tag implications and aliases. Also, it's just interesting info to have.

Updated by anonymous

Requested feature: "child:id" tagging metatag
Why it would be useful: For adding children to a parent post, in the same way the "parent:id" metatag works.

Updated by anonymous

Requested feature: Don't inflict upload penalty when uploading a larger version of your own post.

Why it would be useful: Currently, users are penalized for uploading a larger version of their own posts, losing 0.25 uploads when the inferior post is deleted. Removing this penalty would encourage users to upload larger versions of their own posts.

This could be done by not counting deletions where the uploader is the same for both the larger and smaller post, or by adding a 1/4 bonus for replacing your own posts.

Updated by anonymous

parasprite said:
This is actually a pretty frequent request and has been on the todo list for quite a while now. We are generally shying away from user-submitted thumbnails due to the potential for abuse/quality control, but automating the process isn't very easy to do because of how flash files are designed.

Still has my +1

Honestly, as I've said in the past, even just putting the md5, or even part of the md5, on the icon would be an enormous help. It's not super helpful in finding what you're looking for the first time, but it would help out with finding a post again. It would also make dealing with pages of flash or video easier since it would provide a reference point to keep track of where you were on the page. Anything would be an improvement on the current endless sea of identical thumbs (assuming you're searching for flash/video).

Updated by anonymous

Snowy said:
Honestly, as I've said in the past, even just putting the md5, or even part of the md5, on the icon would be an enormous help. It's not super helpful in finding what you're looking for the first time, but it would help out with finding a post again. It would also make dealing with pages of flash or video easier since it would provide a reference point to keep track of where you were on the page. Anything would be an improvement on the current endless sea of identical thumbs (assuming you're searching for flash/video).

Might as well add the id number as well/instead in that case. Speaking of which, I gotta add this to my Chrome extension. Thanks for the suggestion :).

Updated by anonymous

chdgs

Privileged

Suggestion: Advisory to mobile uploaders.

Perhaps the upload page should advise against uploading from mobile devices. Some are very bandwidth-conscious and compress saved images upon uploading even when using wifi.

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

I personally find this degradation in quality to be unacceptable. As an archive of sorts, it doesn't do well to upload inferior versions of images when better ones are readily available.

_
EDIT: As Tuvalu suggested below, the advisory to mobile users should recommend they post using direct links instead.

Updated by anonymous

chdgs said:
Suggestion: Advisory to mobile uploaders.

+1 to this. Notice should also suggest using direct URL uploads.

Another suggestion, I think the upload by URL feature should be more obvious. I doubt many people are aware of its existence.

Updated by anonymous

qwertyzzz18c said:
Requested feature: Don't inflict upload penalty when uploading a larger version of your own post.

Why it would be useful: Currently, users are penalized for uploading a larger version of their own posts, losing 0.25 uploads when the inferior post is deleted. Removing this penalty would encourage users to upload larger versions of their own posts.

This could be done by not counting deletions where the uploader is the same for both the larger and smaller post, or by adding a 1/4 bonus for replacing your own posts.

On the one hand, yes, on the other, you could question why the smaller one was uploaded in the first place....but on a related argument I've had this happen to me, as a flash game developer, where my older versions of my flash are deleted after the new version is posted. Not gonna worry too much about it though, since I don't upload that often.

Updated by anonymous

Requested feature:
Automatically add tag "uploaded_by_artist" to posts, if Uploader's username matches Artist tag.

Why it would be useful:
I've seen a fair amount of artists who do upload their own stuff on here, but there's no way to find them.

Updated by anonymous

aurel said:

2. Artists often use different E6 and artist names.

As long as the artist has their e6 profile linked to the tag (which we can already do), that shouldn't be an issue.

It would be nice if we had a more obvious way to let artists request linking their profile to the tag, though.

Updated by anonymous

Request: no more flash ads

Reason: I keep reading about flash being abandoned by everyone, and Firefox (my favorite browser, because I'm German) even has flash turned off by default.

Updated by anonymous

Munkelzahn said:
Request: no more flash ads

Reason: I keep reading about flash being abandoned by everyone, and Firefox (my favorite browser, because I'm German) even has flash turned off by default.

I can't guarantee this will happen, but they should at least be falling back to gifs when flash doesn't work.

I'll communicate your feedback to the dragonfru.it team so they can look into this.

Updated by anonymous

Requested feature: Either more (or infinite) space in the Blacklisted box or an 'Artist Blacklist' feature.

Why it would be useful: Since there's a limit of space in the Blacklisted box and new artist images are being posted daily, there's gonna be a point where you're out of room and can't Blacklist anymore (like I can't, lol). To help avoid seeing wasted images by new artists (for being low quality or in a style you don't like, etc.) and further helping make sure you only see things you like each page, either of those requests would be useful.

Can't think of any other ways around this, because I doubt a 'low-quality' or 'noob with crayons' tag is gonna catch on.

Updated by anonymous

Requested feature: Stop the show more aliases/implications link from jumping to the top of the page by adding event.preventDefault(); to the onclick handler.

e.g. Go to feathers, scroll down, and click on the (9 more) link in the list of implications. The browser jumps to the top (as that's how fragment links work) so you have to scroll back down to look at the implications you just showed.

Why it would be useful: It wouldn't really, it's just a minor annoyance. Still though, doesn't hurt to suggest.

Updated by anonymous

Not quite a feature request -- I'm sure something like this has been requested before, -- so much as an example of how a particular feature could work:

Requested feature: Tag completion [eager complete, as opposed to autocomplete]

Why it would be useful Anyone who's ever tagged a post probably knows this; but, making tagging easier, especially making existing tags more discoverable and reducing the incidence of useless dupe tags. This particular idea for *how* to do tag completion, IMO, absolutely minimizes the amount that a user has to type.

Content: this 45-sec GIF animation . Tagging an existing E621 post image, offline, with tags taken from that post, by typing tag fragments. (sped up 3x; realtime it took about 2 minutes to do that tagging)

Summary of content :

Visible content: User types multiple tag fragments, using - as a wildcard; they are automatically matched to the 'best-ranked' tag. Tags are applied once the user presses Enter.

What's happening behind the scenes:

  • User types tag fragment. '-' is used as a wildcard because it is easy to type.
  • Wildcards are inserted at beginning and end of fragment, if they aren't already there. This constructs a glob-style pattern
  • The list of existing tags is matched against this glob pattern.
  • Tags that have already been matched to an earlier fragment are discarded as candidates. (eg. typing 'b b b b' will match four different tags beginning with b, not the same tag four times).
  • Tags are ranked according to, in this order: a) the earliness of the match to the pattern in the tag name, b) Levenshtein similarity ratio between the fragment and the tag name, c) the tag name itself.
  • These candidates are displayed to the user, updating as they type. (you can observe in a few places that I realize I didn't type the right fragment to match what I want, so I retyped part of the fragment)

I wrote this as part of a much more general tagging solution with TMSU and Lighthouse, which hopefully I'll have up on github soon. It supports untagging also (by prefixing the fragment with -), which is not demonstrated here.

I'm aware that any web based solution a) needs caching of the overall tag list, and b) probably can't be quite as responsive as in this demo.
Still, if it could even be half as responsive, that would make tagging vastly easier and quicker.

Updated by anonymous

I'm incredibly original, as you're about to see.

Requested feature: Clicking an image that is in a pool will make it go to the next image in the pool. OR by pressing the left/right arrow. EXCEPT when it is a flash or animated.

Why it would be useful: Come on, it's so simple. Basically every porn gallery site has BOTH of these and I honestly prefer going to g.e hentai or wherever than this site whenever I want to see a comic. Much better than clicking the tiny ass forward arrow on my 16:9 1920x1080 screen in the top left corner.

Oh and I'm gonna double dip:

Requested feature: You can navigate pools in fullscreen. Like a gallery mode.

Why it would be useful: Clicking download merely opens the image. Should the image belong to a pool, it would be cool if I could have something to get to the next image in the pool without having to go back and click that motherfucking forward arrow.

Updated by anonymous

Dragonlayer said:
I'm incredibly original, as you're about to see.

Requested feature: Clicking an image that is in a pool will make it go to the next image in the pool. OR by pressing the left/right arrow. EXCEPT when it is a flash or animated. (...)

Clicking on the image already has a function, it toggles the visibility of notes on an image. Just click on the image (not on a note) on post #117709 and you'll see.

Also, the problem with click-on-image or keyboard navigation for pools is that a single post may be included in multiple pools at the same time. Luckily, eSix Extend already provides a solution. You can use it to "subscribe" to a pool, which will allow you to use customizable hotkeys to navigate that pool.

Updated by anonymous

Dragonlayer said:
I'm incredibly original, as you're about to see.

Requested feature: Clicking an image that is in a pool will make it go to the next image in the pool. OR by pressing the left/right arrow. EXCEPT when it is a flash or animated.

Why it would be useful: Come on, it's so simple. Basically every porn gallery site has BOTH of these and I honestly prefer going to g.e hentai or wherever than this site whenever I want to see a comic. Much better than clicking the tiny ass forward arrow on my 16:9 1920x1080 screen in the top left corner.

This is kind of a tricky one as (aside from the pool system being clunky as hell) images can be in multiple pools. Shouldn't be too hard to find a workaround, but this is something that's been on our todo list for a while now.

+1 to eSix Extend. I'd love to get that integrated into the site natively.

Human-Shaped said:
Requested feature: Either more (or infinite) space in the Blacklisted box or an 'Artist Blacklist' feature.

Why it would be useful: Since there's a limit of space in the Blacklisted box and new artist images are being posted daily, there's gonna be a point where you're out of room and can't Blacklist anymore (like I can't, lol). To help avoid seeing wasted images by new artists (for being low quality or in a style you don't like, etc.) and further helping make sure you only see things you like each page, either of those requests would be useful.

Can't think of any other ways around this, because I doubt a 'low-quality' or 'noob with crayons' tag is gonna catch on.

This number is actually directly linked to cookie size limits and there's little we can do to help it without rewriting the blacklist function to not use cookies (which we will probably need to do eventually anyways).

The best you can do is pay attention to implications/aliases to optimize the list (which unfortunately doesn't help a whole lot with artists). Either way I went ahead and optimized your blacklist by removing some duplicate and redundant* entries, which shaved off ~300 characters. I also kept the pre-optimized blacklist in my notes, so if you want me to restore it to how it was before just let me know.

*For instance, you don't need to blacklist both intersex and cuntboy because blacklisting intersex works for both already.

Updated by anonymous

parasprite said:
This number is actually directly linked to cookie size limits and there's little we can do to help it without rewriting the blacklist function to not use cookies (which we will probably need to do eventually anyways).

The best you can do is pay attention to implications/aliases to optimize the list (which unfortunately doesn't help a whole lot with artists). Either way I went ahead and optimized your blacklist by removing some duplicate and redundant* entries, which shaved off ~300 characters. I also kept the pre-optimized blacklist in my notes, so if you want me to restore it to how it was before just let me know.

*For instance, you don't need to blacklist both intersex and cuntboy because blacklisting intersex works for both already.

Thank you, that gave me a lot more room to blacklist new stuff if I don't like them! :3

Whenever you get around to updating the blacklist function to not use cookies, would it then be possible to have unlimited blacklisting space?
That would be awesome! owo

Updated by anonymous

Human-Shaped said:
Thank you, that gave me a lot more room to blacklist new stuff if I don't like them! :3

Whenever you get around to updating the blacklist function to not use cookies, would it then be possible to have unlimited blacklisting space?
That would be awesome! owo

Unlimited, or a high enough limit that it might as well be unlimited.

Updated by anonymous

geraldford said:
Requested feature: Saved searches

Why it would be useful: It allows you to check back on or view more of content from fruitful searches.

https://e621.net/user/edit

Copy and paste searches into your About me. However it is more work than your feature and not private.

Or bookmark the search.

Updated by anonymous

If you're not worried about other users finding your web history, just use the browser place history, not even bookmarking. Typing 'fri co d' in the location bar in Firefox brings up this search as the first result for me, for example.

Place history has almost completely replaced bookmarks for me.

Updated by anonymous

geraldford said:
Requested feature: Saved searches

Why it would be useful: It allows you to check back on or view more of content from fruitful searches.

While it's not a one-click procedure, you can use custom links with eSix Extend that will even notify you if there are new posts in the search.

Updated by anonymous

parasprite said:
Unlimited, or a high enough limit that it might as well be unlimited.

Really looking forward to that then! owo

I filled in the rest of the space I had with more artists already. With the rate at which new stuff gets posted and I blacklist the ones I don't like, having that much space would be a godsend xD

I'll wait patiently though. Keeping a closer eye on that 'news' section at the top of the screen from now on >:3

Updated by anonymous

Request Feature: Being able to Turn Off Comments and delete Comments

Useful Because: It's a way to get rid of unwanted comments.

Updated by anonymous

Requested feature:
Multi-part arguments in implications and aliases
Why it would be useful:
Would offer billions of possibilities for implications and aliases, and make tagging pretty easy.

Example: male sex -female -cuntboy -dickgirl -herm -maleherm -intersex -i-> male/male

Requested feature:
Tag suggestions? Basically, it's like implications, except it doesn't force them on you, it merely asks you if you want to add that tag as well. It would be used to suggest tags that commonly go together.
Why it would be useful:
Helps newfigs tag posts better, and reminds everyone else that other tags exist.

Example: male/male -s-> penis

Requested feature:
Ability to include metatags in implications and aliases
Why it would be useful:
Would allow for automation of certain tags, and partial automation for ratings.

Examples: sex -i-> rating:e, width:>10000 height:>10000 -i-> superabsurd_res

Updated by anonymous

Heartman98 said:
Request Feature: Being able to Turn Off Comments and delete Comments

Useful Because: It's a way to get rid of unwanted comments.

You can hide your own comments from other people, and on your settings page you can turn off comments by unchecking "Show comments".

ShylokVakarian said:
Requested feature:
Multi-part arguments in implications and aliases
Why it would be useful:
Would offer billions of possibilities for implications and aliases, and make tagging pretty easy.

Example: male sex -female -cuntboy -dickgirl -herm -maleherm -intersex -i-> male/male

It isn't actually an implication, but we have a mass edit tool which pretty much does this. The trouble is that using it for adding tags requires that images are thoroughly and accurately tagged in order to work.

For instance, using your example if any posts tagged male are missing female/intersex tags, that implication would cause it to be mistagged as male/male. With the mass edit tool you can clean things up beforehand, but an implication would last indefinitely and require a lot more ongoing cleanup.

ShylokVakarian said:
Requested feature:
Ability to include metatags in implications and aliases
Why it would be useful:
Would allow for automation of certain tags, and partial automation for ratings.

Examples: sex -i-> rating:e, width:>10000 height:>10000 -i-> superabsurd_res

The mass edit tool actually works pretty well for this.

Updated by anonymous

It isn't actually an implication, but we have a mass edit tool which pretty much does this. The trouble is that using it for adding tags requires that images are thoroughly and accurately tagged in order to work.

For instance, using your example if any posts tagged male are missing female/intersex tags, that implication would cause it to be mistagged as male/male. With the mass edit tool you can clean things up beforehand, but an implication would last indefinitely and require a lot more ongoing cleanup.

It'd still be useful, but it would probably have to be used for things that won't screw everything up.

The mass edit tool actually works pretty well for this.

Yeah, but it'd be good to just start automating some of the tags.

Updated by anonymous

Requested feature:
Checkbox to turn off blacklist
Why it would be useful:
So we can turn off the blacklist temporarily while tag work is being done, without having to cut and paste our blacklist into notepad.

Updated by anonymous

ShylokVakarian said:
Requested feature:
Checkbox to turn off blacklist
Why it would be useful:
So we can turn off the blacklist temporarily while tag work is being done, without having to cut and paste our blacklist into notepad.

+1 to this idea, I have my little pony blacklisted as well as some less popular fetishes I just don't like, but I wouldn't mind looking at those posts if I was just fixing up tags.

Updated by anonymous

ShylokVakarian said:
Requested feature:
Checkbox to turn off blacklist
Why it would be useful:
So we can turn off the blacklist temporarily while tag work is being done, without having to cut and paste our blacklist into notepad.

In the meantime, you can click "Blacklisted" under the search bar and mode dropdown, then click a tag you have blacklisted and it'll show everything that was hidden. It might be a chore if you have many blacklisted things or are viewing a lot of pages/searches at once though.

Updated by anonymous

TonyLemur said:
In the meantime, you can click "Blacklisted" under the search bar and mode dropdown, then click a tag you have blacklisted and it'll show everything that was hidden. It might be a chore if you have many blacklisted things or are viewing a lot of pages/searches at once though.

To add to this, you can also "comment out" entries by putting a # before them like this:

my_little_pony
male
#rating:s
#cat fish -dog

It doesn't actually do anything special, but since almost no tags start with the # character it will cause them to not match anything, effectively disabling them.

Updated by anonymous

TonyLemur said:
In the meantime, you can click "Blacklisted" under the search bar and mode dropdown, then click a tag you have blacklisted and it'll show everything that was hidden. It might be a chore if you have many blacklisted things or are viewing a lot of pages/searches at once though.

Yeah, but you have to do that on EVERY PAGE, and quite honestly, yes, I do have a lot of blacklists.

Updated by anonymous