Topic: (OLD) The Feature Request Thread

Posted under Site Bug Reports & Feature Requests

This topic has been locked.

slyroon said:
You can use the metatag inpool:true -things_you_don't_like to search for pools, containing things you like.

But this won't give view like here which is better when browsing pools.

Also if there's pool with e.g. 30 pics, and 29 blacklisted, then that one not blacklisted will still be in the results. I think that dreich wants to find pools that doesn't contains any picture with blacklisted content. Like if you blacklist castration you won't get pool #903 at all.

Updated by anonymous

Gilda_The_Gryphon said:
But this won't give view like here which is better when browsing pools.

Also if there's pool with e.g. 30 pics, and 29 blacklisted, then that one not blacklisted will still be in the results. I think that dreich wants to find pools that doesn't contains any picture with blacklisted content. Like if you blacklist castration you won't get pool #903 at all.

This is correct. If the pool itself was tagged, my blacklist could filter out pools with tags I'd like to not see, and I could browse pools much more easily.

Updated by anonymous

Char

Former Staff

dreich said:
This is correct. If the pool itself was tagged, my blacklist could filter out pools with tags I'd like to not see, and I could browse pools much more easily.

I'm not sure I can see us extending e621's tagging system to allow you to tag pools themselves (it seems to me like this could really cause some issues/disagreements over what a pool should be tagged with).

However, I think one possibility could be the site alerting you if a pool you're viewing contains content that matches your blacklist on ANY of the pages. You'd still have to view the index itself for the pool to know if it contains any posts that match your blacklist, but at least it'd tell you then rather than you discovering yourself later on. It'd be even nicer if it could alert you ahead of time when just browsing the Pool index, but I don't think e621's developers would recommend that.

Another possibility that WOULD allow the tagging of pools though would be pools having a "static" tag list that is not editable by anyone at all, and all it is is a collection of ALL of the tags that appear on the posts in the pool (this might have to be a process that runs once per day?). Then the site could filter out pools according to your blacklist just like it does posts.

I can't promise that either will happen, as the decision ultimately rests on what e621's developers recommend (I'm no developer myself). It's not something that would be impossible, to the best of my knowledge, but it still might be a good deal of work for a "minor" enhancement (in the grand scheme of things).

I'll recommend it to them and see what they think.

Updated by anonymous

I'm in favor of the static tags, which should be updated when a new post is added to the pool. But as char said, force the devs with no cookies happily suggest it and offer cookies :)

Updated by anonymous

pool tags.. tony you up for that? I wouldn't mind, but It would be waaaaay down the road, another thing to consider is blacklisting previews and full sizes.

also

Xch3l said:
You can be:

  • Aurali's sex toy

ew.

Updated by anonymous

Aurali said:
pool tags.. tony you up for that? I wouldn't mind, but It would be waaaaay down the road, another thing to consider is blacklisting previews and full sizes.

I'd say just on the previews, which are a nice warning.

Aurali said:
ew.

What? I didn't say you were going to use it… Just leave it on its package on the highest shelf…

---

Also, do suggestions made here are still reviewed? If so I have one, that has been suggested several times: add a score counter to the comments in posts. I don't know exactly why, but since we have the function to up/downvote comments, it would be nice to see which are the most upvoted of them (or downvoted too)

I'd put this on the script but I think it'll do many requests and probably overload the server, you know, users who installed it plus posts viewed by each of them.

Updated by anonymous

This has likely been suggested before, but what about colored tags for genders? When scanning the tags of an image to make sure it's tagged correctly, and the image has about a bajillion tags, it'd be easier to just scan for that color of text to see if it needs to be changed.

Updated by anonymous

Digital_Kindness said:
This has likely been suggested before, but what about colored tags for genders? When scanning the tags of an image to make sure it's tagged correctly, and the image has about a bajillion tags, it'd be easier to just scan for that color of text to see if it needs to be changed.

This may be multicolored tags, already seen and it does not necessarily improve things.

Otherwise, a system of tags separation into two parts like SoFurry ...
Artist, Sex, Species, Copyright (and a few other important tags at determining) in a separate insert...

Updated by anonymous

Tauxiera said:
This may be multicolored tags, already seen and it does not necessarily improve things.

Otherwise, a system of tags separation into two parts like SoFurry ...
Artist, Sex, Species, Copyright (and a few other important tags at determining) in a separate insert...

That's sort of what I meant. Currently we've got the following color indicators for tags:

Green = Character
Orange = Species
Gold = Artist
Purple = Copyright

Not sure what color we'd use for Sex; can't use blue, as it'd clash with the standard site layout scheme, unless of course we put a border and separate background behind the tag sidebar (sort of like the background behind quotes, or the edit box I'm typing in right now).

Updated by anonymous

Xch3l said:
Also, do suggestions made here are still reviewed? If so I have one, that has been suggested several times: add a score counter to the comments in posts. I don't know exactly why, but since we have the function to up/downvote comments, it would be nice to see which are the most upvoted of them (or downvoted too)

I'd put this on the script but I think it'll do many requests and probably overload the server, you know, users who installed it plus posts viewed by each of them.

A lot of people have suggested score counters to comments, but eh~ It would make comments more of a karma game.

Xch3l said:
Also, do suggestions made here are still reviewed?

Riversyde only made this thread in spite (literally) of me saying I stopped taking suggestions for Ouroboros 1.0 a year and a half ago. Douche :p. Either way, I check the bug checker much more thoroughly then the forums (bugs slip through cracks if you have 20 people commenting on something stupid in bug threads). I'd rather you do it there.

Updated by anonymous

Char

Former Staff

Aurali said:
A lot of people have suggested score counters to comments, but eh~ It would make comments more of a karma game.

While I don't disagree that this would be something to watch for, I think it's kind of confusing for our user account settings to have a section for setting a threshold for hiding comments under a certain score, but not actually display the score anywhere. Users won't know what to set their threshold to if they have no frame of reference for how low the score might be on a comment that they'd otherwise find acceptable. I honestly wouldn't even be able to recommend a number to a user because even I have no idea how many votes comments get and how low or high their scores typically are.

Users are basically forced to just keep fiddling with it until they finally find a level that they're comfortable with.

It's also kind of unfair that the default threshold for hiding comments is 0, meaning that a single initial downvote on your comment will hide it from view from the majority of e621 users. I'd like to recommend a lower value than 0, but I have no idea what it should be because we don't know the scores for any comments. :P

Additionally, seeing scores will help users understand which comments typically get high scores, and which get low scores (again, I'm assuming that comments get a decent amount of votes), thereby giving them vital information regarding how to handle themselves.

Updated by anonymous

Char said:
While I don't disagree that this would be something to watch for, I think it's kind of confusing for our user account settings to have a section for setting a threshold for hiding comments under a certain score, but not actually display the score anywhere. Users won't know what to set their threshold to if they have no frame of reference for how low the score might be on a comment that they'd otherwise find acceptable. I honestly wouldn't even be able to recommend a number to a user because even I have no idea how many votes comments get and how low or high their scores typically are.

Users are basically forced to just keep fiddling with it until they finally find a level that they're comfortable with.

It's also kind of unfair that the default threshold for hiding comments is 0, meaning that a single initial downvote on your comment will hide it from view from the majority of e621 users. I'd like to recommend a lower value than 0, but I have no idea what it should be because we don't know the scores for any comments. :P

Additionally, seeing scores will help users understand which comments typically get high scores, and which get low scores (again, I'm assuming that comments get a decent amount of votes), thereby giving them vital information regarding how to handle themselves.

hmm. I figure -2 is a good point, -4 for visible scores. It would be trivial to get this running if you guys think it wouldn't be abused (my biggest concern) but it's up to you.

Updated by anonymous

Aurali said:
A lot of people have suggested score counters to comments, but eh~ It would make comments more of a karma game.

Karma? How? Since afaik votes are per post and not per user.

Aurali said:
hmm. I figure -2 is a good point, -4 for visible scores. It would be trivial to get this running if you guys think it wouldn't be abused (my biggest concern) but it's up to you.

I have had that number in 0 since registered *shrug* And abuse it? Awf cawrse nawt! downvote ALL comments!

This'll require some experimenting…

Updated by anonymous

Char said:
Another possibility that WOULD allow the tagging of pools though would be pools having a "static" tag list that is not editable by anyone at all, and all it is is a collection of ALL of the tags that appear on the posts in the pool (this might have to be a process that runs once per day?). Then the site could filter out pools according to your blacklist just like it does posts.

This sounds like the best of these options to me.

Updated by anonymous

Not sure if I suggested this before or if anyone else did (CBA reading thought 16 pages :x), but having a timestamp when a post was deleted in your profile under "deleted posts" would be really useful... Also hyperlinks to the takedown request (if there is one) would be neat from the "Reason" tab.

Updated by anonymous

Aurali said:
why?...why?
okies

hmm, i thought about it abit too. the PM system would be good if user, admin, and system messages where separated into three different boxes.
while i havnt ever missed a system message, i HAVE missed admin/user to user pm's in the clutter

Updated by anonymous

Another feature which could be handy is export PMs to text/other file. So you could save backup copies to PC/whatever, then delete them from the server.

Updated by anonymous

Please give us the ability to report an image. When there's a tagging dispute or a clusterfuck of ignorance in the comments, it'd be nice to report the image in general and not have to report a single comment and the clarify that you're not actually flagging the comment or user, but the image.

Updated by anonymous

Rocket_Corgi said:
Please give us the ability to report an image. When there's a tagging dispute or a clusterfuck of ignorance in the comments, it'd be nice to report the image in general and not have to report a single comment and the clarify that you're not actually flagging the comment or user, but the image.

Generally, putting in "Report" on one user, then including "INciting "X" Problem with users X, X, and X" Replacing X with names as needed tends to get the admins looking where they need to be looking.

Updated by anonymous

Princess_Celestia said:
Generally, putting in "Report" on one user, then including "INciting "X" Problem with users X, X, and X" Replacing X with names as needed tends to get the admins looking where they need to be looking.

While I won't disagree with you on that, it's still a clunky way to do it. Having a 'report image' link on the side (with appropriate rules for its usage of course) would help streamline the process somewhat.

Updated by anonymous

on the reports...the ability to either add extra information user might have missed on first reporting, or an edit ticket button/delete ticket button. i know you guys on the stuff hate it when we report the same user twice, though usually that happens when we have to add extra information to the ticket.

Updated by anonymous

Esme_Belles said:
on the reports...the ability to either add extra information user might have missed on first reporting, or an edit ticket button/delete ticket button. i know you guys on the stuff hate it when we report the same user twice, though usually that happens when we have to add extra information to the ticket.

Now the ability to edit tickets submitted, that could come in REAL handy.

Updated by anonymous

I'd like to see search/sort functions for the tag edits page of a user, for example, being able to sort my own tag edits to see which ones have been changed, etc. Not sure how easily/feasible a change it is, but it's one I'd like to see.

Updated by anonymous

I like the changes. Visible comment scores and less strict default threshold are good. I hope to see less "blanket downvotes" when every second comment is hidden.

It would be nice to align scores on the right though, as currently there is a bit too much clutter in the comments section. Separators "|" are redundant too, I think, but that is a matter of taste.

Updated by anonymous

Requested feature: doublepost check

Why it would be useful: is obvious. eliminated accidental duplicate posts
just check if what you entered matches an existing post

Updated by anonymous

Also an anti-creepy rule should probably be applied to descriptions as well as comments.

Updated by anonymous

Falord said:
Or just do this

Description

to thing that have alot of text

well would be easier

Sorry, that's actually what I meant. I'm used to spoiler text on other sites being a collapsible field, not a blacked-out section.

Do what this guy said, not what I said.

Updated by anonymous

Uploads should only be visible after they've been approved.
That would reduce the number of troll posts.

Trolls could still annoy the modmins with pointless uploads, but they wouldn't have a big audience for it.

Updated by anonymous

Munkelzahn said:
Uploads should only be visible after they've been approved.
That would reduce the number of troll posts.

Trolls could still annoy the modmins with pointless uploads, but they wouldn't have a big audience for it.

Agreed

Updated by anonymous

I'm rather for hiding not-approved posts with score under certain score threshold. And they should be still visible if user searches for them with status:pending

Updated by anonymous

Don't prevent us from seeing un-approved posts. It's okay to let us hide them, but don't take away our choice to see them.

Updated by anonymous

How about a profile option to hide unapproved posts? Enabled for unregistered and enabled by default.

This way, they'll get a much lower audience without restricting people who want to see unapproved posts from seeing them.

Updated by anonymous

Can we make deleted posts thumbnails clickable? So, for example, it would be easy to see their reason of deletion.

Updated by anonymous

Gilda_The_Gryphon said:
But what if I want to search for specific deleted posts? For example posts that I approved and were deleted. Aren't whole deleter:user and status:deleted searches meaningless if there is no access to the results?

Fair enough.

Updated by anonymous

Seven_Twenty said:
How about a profile option to hide unapproved posts? Enabled for unregistered and enabled by default.

This way, they'll get a much lower audience without restricting people who want to see unapproved posts from seeing them.

I think this is the best way to implement this if it does in fact get added at all. I would be annoyed if the option to view them at all was taken away.

Updated by anonymous

I would like to see the preview thumbnails for images which are "Download", "Deleted", or "Blacklisted" be colored in some manner so that they can be more easily distinguished with out pausing to read the text on them.

My suggestions:
A red X from corner to corner across Deleted
A red circle with a line through it for Blacklisted
A green arrow pointing down behind the text of Download

I might have missed some of the thumbnail text images, those were the ones I thought of offhand.

Updated by anonymous

Not sure if this idea was here already, but how about a mass source edit function? or something like edit tag script function. So you can add a source or remove bad source from a set of images fast.

Updated by anonymous

Hey how about for new users you have a few tags blacklisted that tend to cause problems...like scat cub watersports etc?
Then if they want to see it, THEY NOW KNOW WHERE THE BLACKLIST IS!

Updated by anonymous

Feature:
In upload screen children field besides existing parent

Reason:
Would be useful when uploading bigger version of existing posts.

Updated by anonymous

Limitation:
Set a "max resolution" for uploading files, by ether automatically or by making the uploader change the resolution. (if a max res already exist then perhaps lowering it)

Reason:
There are times when a Picture's resolution is so high that my browser can't handle it. (ex:#332312) Plus at that size i can't enjoy what the picture has to offer.
Not only would me and a few others appreciate it but I'm sure the servers would too.

p.s. I'm sorry if this has already been discussed.

Updated by anonymous

shadowslick said:
Limitation:
Set a "max resolution" for uploading files, by ether automatically or by making the uploader change the resolution. (if a max res already exist then perhaps lowering it)

Reason:
There are times when a Picture's resolution is so high that my browser can't handle it. (ex:#332312) Plus at that size i can't enjoy what the picture has to offer.
Not only would me and a few others appreciate it but I'm sure the servers would too.

p.s. I'm sorry if this has already been discussed.

There are user settings that allow you to view all images scaled down to fit in the browser window, and to show reduced-resolution samples in place of full-size images. More dynamic resizing is also in the works.

Updated by anonymous

Combine the username change page with namechange tickets, so we don't have to navigate to separate pages just to process them.

Updated by anonymous

Requested Feature: More obvious post id/avatar... er, box thing in user settings.

Why is would be useful: I'm getting bored of new users asking about this.

Updated by anonymous

Renard_Queenston said:
Requested Feature: More obvious post id/avatar... er, box thing in user settings.

Why is would be useful: I'm getting bored of new users asking about this.

Then ignore it.

Updated by anonymous

Could we perhaps move the upload subtab from within the post tab to its own tab? I was thinking between "My Account" and "Posts".
This would be useful because you wouldn't have to go through as many pages just to get to the upload page.
You could also add an upload button to the main home screen...perhaps to the left of "posts"

Updated by anonymous

Moon_Moon said:
Could we perhaps move the upload subtab from within the post tab to its own tab? I was thinking between "My Account" and "Posts".
This would be useful because you wouldn't have to go through as many pages just to get to the upload page.
You could also add an upload button to the main home screen...perhaps to the left of "posts"

I'm not sure if making the option to upload conspicuous will be entirely beneficial.

Updated by anonymous

How about when items are in the black list, they don't show up in the tag list and don't affect the count of per-page results.

I swear it must have been a pony invasion, but on the first couple pages there were only a handful of images shown on each.

Updated by anonymous

KodaForShort said:
How about when items are in the black list, they don't show up in the tag list and don't affect the count of per-page results.

I swear it must have been a pony invasion, but on the first couple pages there were only a handful of images shown on each.

Currently impossible, but is in the works already.

Updated by anonymous

How about a 'reason' field for when you do tag edits. It'd be nice to state your reasoning for adding/removing tags so people don't later look at the tag edit history and go 'why the fuck did they do THAT?' It'd be optional to put something in the field, obviously.

Updated by anonymous

Rocket_Corgi said:
How about a 'reason' field for when you do tag edits. It'd be nice to state your reasoning for adding/removing tags so people don't later look at the tag edit history and go 'why the fuck did they do THAT?' It'd be optional to put something in the field, obviously.

(in b4 the obligatory "No." from someone on the staff)

Actually, it's a very good idea :-)

Updated by anonymous

Rocket_Corgi said:
How about a 'reason' field for when you do tag edits. It'd be nice to state your reasoning for adding/removing tags so people don't later look at the tag edit history and go 'why the fuck did they do THAT?' It'd be optional to put something in the field, obviously.

I wonder how that would work in tag wars.

Updated by anonymous

Butterscotch said:
I wonder how that would work in tag wars.

it would keep the tag wars out of the comments

Updated by anonymous

Munkelzahn said:
(in b4 the obligatory "No." from someone on the staff)

Actually, it's a very good idea :-)

I just know that there's been times where I've seen a tag on an image, removed it because it didn't seem appropriate for the image, and then someone mentioned in the comments why it was added (like a small recognizable part of an established character was in the image, but not readily noticeable).

Updated by anonymous

Rocket_Corgi said:
How about a 'reason' field for when you do tag edits. It'd be nice to state your reasoning for adding/removing tags so people don't later look at the tag edit history and go 'why the fuck did they do THAT?' It'd be optional to put something in the field, obviously.

Great idea. I actually looked for an edit summary box on my first tag edit.

Updated by anonymous

A thought, after my 2nd, or 3rd typo in an alias suggestion (I know, be more careful, sometimes I'm tired), the ability for users to edit and/or delete alias and implication suggestions that they created.

That way, we can fix our won typos and put the right suggestion in.

Updated by anonymous

How about when you put your cursor over your favorites counter and small display shows how many S/Q/E images are in there.

Example: S(Safe):257 Q(Questionable):425 E(Explicit):314

Updated by anonymous

Queen_Tyr'ahnee said:
How about when you put your cursor over your favorites counter and small display shows how many S/Q/E images are in there.

Example: S(Safe):257 Q(Questionable):425 E(Explicit):314

That would take four different searches (Total/S/Q/E). Not that hard to do, though.

---

Edit: How about a different border color for posts that are in the DNP List? Like color #FF7700? (artist color) Yeah, I can't do \[color] tags, don't even ask

Updated by anonymous

Xch3l said:
Edit: How about a different border color for posts that are in the DNP List? Like color #FF7700? (artist color) Yeah, I can't do \[color] tags, don't even ask

Well, if they're on the DNP list, then they'll be deleted pretty quickly anyway (and we don't need a border to find DNP images), and if they're an exception (like promotional stuff), then the border is pointless. Plus, only one border color can be shown at once, so either you'll keep seeing yellow borders instead of useful red (flagged), blue (not approved), etc., or you'll never see the yellow border, you'll see those instead.

Updated by anonymous

tony311 said:
Well, if they're on the DNP list, then they'll be deleted pretty quickly anyway (and we don't need a border to find DNP images), and if they're an exception (like promotional stuff), then the border is pointless. Plus, only one border color can be shown at once, so either you'll keep seeing yellow borders instead of useful red (flagged), blue (not approved), etc., or you'll never see the yellow border, you'll see those instead.

Huh, you're right. I had one of those moments when an idea comes and you say "why not?"
And about borders, I forgot that there can be only one *derp* As for them, there must be something to show different statuses (Pending approval + Flagged, Pending + With children, Pending + Parent)

Hey, I thought you were MIA (heh, not really, just less active). Also, did you got the PM? One about sections.

Updated by anonymous

Xch3l said:
Hey, I thought you were MIA (heh, not really, just less active). Also, did you got the PM? One about sections.

Nope, same as always. And yeah, that issue was fixed (maybe not live yet).

Updated by anonymous

If we're having counter how many times picture was viewed then how about counter if/how many times certain user viewed pic? And tag like viewedby:username or just viewedbyme:true to search pictures that were (not) already viewed by user.

Updated by anonymous

Gilda_The_Gryphon said:
If we're having counter how many times picture was viewed then how about counter if/how many times certain user viewed pic? And tag like viewedby:username or just viewedbyme:true to search pictures that were (not) already viewed by user.

We currently don't check if a user views an image or not.

Updated by anonymous

Tagging_error

Requested feature #1: alias words like "it's", "the", "we" and such to "tagging_error" or something like that

Why it would be useful: to make it easier for "tag-cleaners" to find posts where someone forgot underscores when tagging

underage tag

Requested feature #2: a tag for characters below the recommended age for doing stuff such as sex

Why it would be useful: some people (at least i know i do) prefer not to see that kind of stuff, while not caring about humor or such like in post #11022

tag group(s)

Requested feature #3: tag grouping saying "artist(s)", "character(s)" and so on

Why it would be useful: it would look better (IMO)

bloodlust color scheme bug

Requested feature #4: (about bloodlust color scheme(and possibly also other color schemes)) change colors in general (wiki pages are blue on dark red and such)

Why it would be useful: it feels weird (for me) to read blue on dark red

broken preview?

Requested feature #5: previews seems to be broken?(box shows up, but doesn't show a picture, only tags and stuff)

Updated by anonymous

BananFisk said:

Tagging_error

Requested feature #1: alias words like "it's", "the", "we" and such to "tagging_error" or something like that

Why it would be useful: to make it easier for "tag-cleaners" to find posts where someone forgot underscores when tagging

underage tag

Requested feature #2: a tag for characters below the recommended age for doing stuff such as sex

Why it would be useful: some people (at least i know i do) prefer not to see that kind of stuff, while not caring about humor or such like in post #11022

tag group(s)

Requested feature #3: tag grouping saying "artist(s)", "character(s)" and so on

Why it would be useful: it would look better (IMO)

bloodlust color scheme bug

Requested feature #4: (about bloodlust color scheme(and possibly also other color schemes)) change colors in general (wiki pages are blue on dark red and such)

Why it would be useful: it feels weird (for me) to read blue on dark red

broken preview?

Requested feature #5: previews seems to be broken?(box shows up, but doesn't show a picture, only tags and stuff)

Feature #1: If those tags are not already aliased to invalid_tag, feel free to submit tag aliases for them.

Feature #2: We already have the young and cub tags.

Feature #3: This is already in place, unless I'm severely misunderstanding you.

Feature #4: Agreed, some of the different color schemes are a little wonky (not being able to see spoiler sections on Bloodlust, for example).

Feature #5: This has been disabled for some time now. I think they had issues with it, and disabled it so they could fix it.

Updated by anonymous