LittleBaconBits said:
Sorry if this has been said, but...

Request: Make the thumbnail for GIF's be white with the word GIF on it like flashes and videos.

Useful Because: We'll know which posts are GIF's and which aren't.

i may be wrong and i'm pretty sure that there are static GIF's too, if you want to search for animated gifs you can use type:gif animated if you don't want to search for gifs you can simply blacklist type:gif i know that by the thumbnail you probably won't be able to judge what is animated GIF or not, but you also won't be able to judge if its an static gif.

I just don't know if it would be useful or not.

Just_Another_Dragon said:
i may be wrong and i'm pretty sure that there are static GIF's too, if you want to search for animated gifs you can use type:gif animated if you don't want to search for gifs you can simply blacklist type:gif i know that by the thumbnail you probably won't be able to judge what is animated GIF or not, but you also won't be able to judge if its an static gif.

I just don't know if it would be useful or not.

There are static gifs but it would be pretty simple to program a check on upload that marked gifs with multiple frames, but it just hasn't been added yet.

Although I think there's a way to trick full color in a gif with multiple frames (normally gifs have limited color), so I'm not sure if that is as simple as I think.

LittleBaconBits said:
Sorry if this has been said, but...

Request: Make the thumbnail for GIF's be white with the word GIF on it like flashes and videos.

Useful Because: We'll know which posts are GIF's and which aren't.

I disagree, it's nice to actually tell what we're looking at. But a way to distinguish GIFs would still be nice...

Okay how about this

Transparent letters that spell GIF are shown on the original thumbnail, almost like a watermark.

parasprite said:
There are static gifs but it would be pretty simple to program a check on upload that marked gifs with multiple frames, but it just hasn't been added yet.

Although I think there's a way to trick full color in a gif with multiple frames (normally gifs have limited color), so I'm not sure if that is as simple as I think.

You can somehow animate PNGs...

LittleBaconBits said:
Okay how about this

Transparent letters that spell GIF are shown on the original thumbnail, almost like a watermark.

Just put a little icon in the bottom right of the thumbnail, like what Furaffinity does, only our own version.

Furrin_Gok said:
You can somehow animate PNGs...

It's an unofficial extension on the PNG format. Basically the extra frames gets added after the section that says "END IMAGE HERE" and if the program doesn't support APNG it'll just ignore the rest of the data.

It's not technically correct, but it's probably close enough for a simple explanation.

Oh, and as far as I know scanning for those would probably be about as easy (probably easier since GIF is an ancient format).

parasprite said:
It's an unofficial extension on the PNG format. Basically the extra frames gets added after the section that says "END IMAGE HERE" and if the program doesn't support APNG it'll just ignore the rest of the data.

If someone uploads an APNG here, and the browser is capable of viewing APNG, and the PNG has not been automatically resized by e621 settings, will the animation play?

Lance_Armstrong said:
If someone uploads an APNG here, and the browser is capable of viewing APNG, and the PNG has not been automatically resized by e621 settings, will the animation play?

Yup. We even have a tag for it, though there aren't many on here. animated_png - Works in vanilla Firefox/Safari and Chrome with the APNG extension on the Chrome store.

Shouldn't the animation play regardless of auto-resize? As far as I can tell the auto-resize just changes the width and height values on the <img> element used to display the post's image.

Tested with post #307082 (actually the only particularly large APNG on e621) / Firefox 34 . Resizing on, resizing works, animation works, whether full size or not.

(unless you mean the 'show image samples' setting, which might well cause that effect)

Lance_Armstrong said:
If someone uploads an APNG here, and the browser is capable of viewing APNG, and the PNG has not been automatically resized by e621 settings, will the animation play?

It should, but the handful of currently available examples show otherwise. Those posts also have jpeg preview images. Even the smaller ones, like post #358609.

EsalRider said:
It should, but the handful of currently available examples show otherwise. Those posts also have jpeg preview images. Even the smaller ones, like post #358609.

All of those work for me, resized or un-resized, without 'show sample images'.
If I enable 'show sample images', post #427670 works at all times, and I have to click 'Full Size' before the other posts in your list work.

I guess the thumbnailer isn't APNG-aware. It's odd that post #427670 alone works when 'show sample images' is on, though.

Got post #359089 to work by opening Download since I have "Show image samples" enabled.

Very neat, and superior to GIF.

Lance_Armstrong said:
Got post #359089 to work by opening Download since I have "Show image samples" enabled.

Very neat, and superior to GIF.

Just to clarify for debugging purposes: The animation does not work when you click 'Full Size'? I guess your browser might incorrectly cache a 'is this image an animation' flag if that's so, which would be a bug in its APNG support.

savageorange said:
Just to clarify for debugging purposes: The animation does not work when you click 'Full Size'? I guess your browser might incorrectly cache a 'is this image an animation' flag if that's so, which would be a bug in its APNG support.

No, it works. I checked and it loaded instantly because the full download was cached. I just don't use the Full Size link ever since I enabled "show image samples".

Enabling "show image samples" has enabled me to avoid multimegabyte monster image loads.

Suggested feature: Make it harder to change tag types.

Nowadays, there's rarely any need to change the types, except for new tags. Most changes are done by mistake and need to be fixed: general tags get changed into character tags or vice versa, etc.

If I remember right, any tag with less than hundred posts can be changed by anybody. I suggest lowering that to twenty, maybe even lower. That'd stop some tags from constantly bouncing between various categories, and it might even make taggers realize that they should be using some other tag (or disambiguation) instead..

Genjar said:
Suggested feature: Make it harder to change tag types.

Nowadays, there's rarely any need to change the types, except for new tags. Most changes are done by mistake and need to be fixed: general tags get changed into character tags or vice versa, etc.

If I remember right, any tag with less than hundred posts can be changed by anybody. I suggest lowering that to twenty, maybe even lower. That'd stop some tags from constantly bouncing between various categories, and it might even make taggers realize that they should be using some other tag (or disambiguation) instead..

Lower it to 20 for member level at least, since they're the most likely to repeatedly change them. I occasionally see newer users with tag histories that look like "+general:sex +general:male +copyright:konami +character:krystal +explicit +invalid_tag"

Suggested feature: Search tags by partial words

I can't understand why I can search tag alias and implications using parts of a word, but I can't do it in tags.

For example:
Searching for 'green' in implication
Searching for 'green' in tags

blackest_vulture said:
Suggested feature: Search tags by partial words

I can't understand why I can search tag alias and implications using parts of a word, but I can't do it in tags.

For example:
Searching for 'green' in implication
Searching for 'green' in tags]

You can by using what's called search "wild cards": basically use the * to make the site search for "anything after this" or "anything before this". So searching green* gives you this and searching *green gives you this and searching *green* gives you this and you can even use multiple wildcards in the same search if you are having to guess a specific tag or want to narrow it down. It's extremely handy. Works in both the tag index and in the regular search box. Doesn't work in the implications/aliases page though, so that's part of why it does that automatically there.

furrypickle said:
You can by using what's called search "wild cards": basically use the * to make the site search for "anything after this" or "anything before this". So searching green* gives you this and searching *green gives you this and searching *green* gives you this and you can even use multiple wildcards in the same search if you are having to guess a specific tag or want to narrow it down. It's extremely handy. Works in both the tag index and in the regular search box. Doesn't work in the implications/aliases page though, so that's part of why it does that automatically there.

It really comes in handy. Thanks

blackest_vulture said:
It really comes in handy. Thanks

Note that combining them with - or ~ in the same search term doesn't work. In other words, green* -hat and green* ~hat ~cake work fine, but -green* hat doesn't.

That being said, the wildcard is also a great lazy way to type really long tags into the search (e.g., that_one_bug*). :P

Feature Request: Add number of responses to "View Responses" blip links.

All "View Responses" links without replies would be changed to "View Responses (0)", but you obviously could still click on the link (in case a response was made since you viewed the page).

Feature Request 2: Inline blip responses so you can see blips that are the grandchild, great-grandchild etc. of the first blip.

Style: Extra 1em or more margin-left for each new level (less like the forums, more like Reddit or other tabbed discussions). No more margin after a certain level (4?)

However keep the "View Responses" link, which would not include the parent of the blip for which you clicked "View Responses". See below:

Reddit, others:

• 1
• 2 <- you are here
• 3
• 4

e621:

• 2 <- you are here
• 3
• 4

User settings option to disable the format.

Why it would be useful: Because you don't know if there are responses to a response until you click "View Responses" to open a separate page. And these responses aren't included on the top level blip.

Problem: A neverending chain of replies would create a lengthy page. Potential solution: Maximum number of sublevels shown as a user setting, or a "next" button after a certain number of responses (it may already do this, but I wouldn't know because I haven't seen a single blip with 20+ responses).

Would it be possible to mark the thumbnails of animated images somehow? Different border color maybe?

It's tough to tell those apart from still images when tag scripting, and being able to see those at glance would no doubt be useful for regular users too.

Genjar said:
Would it be possible to mark the thumbnails of animated images somehow? Different border color maybe?

It's tough to tell those apart from still images when tag scripting, and being able to see those at glance would no doubt be useful for regular users too.

As a slight workaround, I just blacklisted animated so I at least know when they are coming.

But yeah, this would be awesome.

Genjar said:
Would it be possible to mark the thumbnails of animated images somehow? Different border color maybe?

It's tough to tell those apart from still images when tag scripting, and being able to see those at glance would no doubt be useful for regular users too.

I think that can be done with pure CSS:

http://www.w3schools.com/cssref/sel_attribute_value_contains.asp

The rule should match 'img' elements with a 'class' attribute containing 'preview', and a 'title' attribute containing 'animated'. I remember how to do -some- of that..

Now that I think about it, this is probably how the existing color variation according to rating/status is done, so it might be doable just as a bit of copy/paste/edit in the stylesheet.

And of course if you can work out the rule you need, you can apply it locally using an addon like Stylish, in the mean time.

Feature request: e621 Android Wear app, e621 for round and square smartwatches.

Why it would be useful: One Wrist, One Hand, One fApp.

Bumping some real requests (no Android Wear fapps)

• Number of responses and inline blip responses
• Character count for compose blip.
• today and yesterday keywords for date syntax
• Automatically add md5 prefix
• Please link the stats page on the sitemap.
• Tag history changes
• Prevent tag history dupe
• Score numbers on the comments index should be green or red if you have already upvoted or downvoted the post.

Requested feature: Some kind of way to identify artists who have had previous posts taken down

Maybe a checkbox or something on their artist profile that says 'Has made a takedown request in the past'

And a different tag colour or additional implicated tag

Why it would be useful: Cuz drama

titanmelon said:
Requested feature: Some kind of way to identify artists who have had previous posts taken down

Maybe a checkbox or something on their artist profile that says 'Has made a takedown request in the past'

And a different tag colour or additional implicated tag

Why it would be useful: Cuz drama

You can search artistname status:deleted and check reason of deletion for posts with orange border.

Requested feature: Notify the user of any search terms they are using that have been aliased away.
For example, transgender searches for invalid_tag -- obviously the latter is a vastly broader search.

Suggested format : 'The following tags in your search are aliased: foo→ bar, baz → fiz', placed near the top of the page.

Why it would be useful:Particularly with blanket tags like invalid_tag or invalid_color as the 'aliased to:' tag, searching for a tag that you don't know is aliased can return results that are misleading (may seem plausible but the actual query is for stuff much different than intended). It would also have a side effect of informing people about updates of tag names.

savageorange said:
Requested feature: Notify the user of any search terms they are using that have been aliased away.
For example, transgender searches for invalid_tag -- obviously the latter is a vastly broader search.

Suggested format : 'The following tags in your search are aliased: foo→ bar, baz → fiz', placed near the top of the page.

Why it would be useful:Particularly with blanket tags like invalid_tag or invalid_color as the 'aliased to:' tag, searching for a tag that you don't know is aliased can return results that are misleading (may seem plausible but the actual query is for stuff much different than intended). It would also have a side effect of informing people about updates of tag names.

Holy hell, I was just about to do that. You put it a lot better than I did, though. +1111 to this though.

savageorange said:
Requested feature: Notify the user of any search terms they are using that have been aliased away.
For example, transgender searches for invalid_tag -- obviously the latter is a vastly broader search.

Suggested format : 'The following tags in your search are aliased: foo→ bar, baz → fiz', placed near the top of the page.

Why it would be useful:Particularly with blanket tags like invalid_tag or invalid_color as the 'aliased to:' tag, searching for a tag that you don't know is aliased can return results that are misleading (may seem plausible but the actual query is for stuff much different than intended). It would also have a side effect of informing people about updates of tag names.

Thirding this. That feature would be very good to have.

savageorange said:
Requested feature: Notify the user of any search terms they are using that have been aliased away.
For example, transgender searches for invalid_tag -- obviously the latter is a vastly broader search.

Suggested format : 'The following tags in your search are aliased: foo→ bar, baz → fiz', placed near the top of the page.

Why it would be useful:Particularly with blanket tags like invalid_tag or invalid_color as the 'aliased to:' tag, searching for a tag that you don't know is aliased can return results that are misleading (may seem plausible but the actual query is for stuff much different than intended). It would also have a side effect of informing people about updates of tag names.

Been on my mind for a while, but I like this solution a lot. Fourthing!

I'll take a 5th on this one.

savageorange said:
Requested feature: Notify the user of any search terms they are using that have been aliased away.
For example, transgender searches for invalid_tag -- obviously the latter is a vastly broader search.

Suggested format : 'The following tags in your search are aliased: foo → bar, baz → fiz', placed near the top of the page.

Why it would be useful:Particularly with blanket tags like invalid_tag or invalid_color as the 'aliased to:' tag, searching for a tag that you don't know is aliased can return results that are misleading (may seem plausible but the actual query is for stuff much different than intended). It would also have a side effect of informing people about updates of tag names.

Did this get enough votes yet? If not, here's my +1.

savageorange said:
Requested feature: Notify the user of any search terms they are using that have been aliased away.
For example, transgender searches for invalid_tag -- obviously the latter is a vastly broader search.

Suggested format: 'The following tags in your search are aliased: foo→ bar, baz → fiz', placed near the top of the page.

Why it would be useful:Particularly with blanket tags like invalid_tag or invalid_color as the 'aliased to:' tag, searching for a tag that you don't know is aliased can return results that are misleading (may seem plausible but the actual query is for stuff much different than intended). It would also have a side effect of informing people about updates of tag names.

Supported. I've long desired some way of knowing which tag(s) I just added were non-kosher.

It's been on my todo list for a while, yeah.

A quick suggestion:

Requested feature: Urls like https://e621.net/forum/show/30573 get linked as-is even when formatted with DText like this one. Can we get a push that detects internal links and formats the url as /forum/show/30573 instead for DText links?

Why it would be useful: Users who browse e926 get linked back to e621 when links like this one are followed but not this one. Manually formatting them so that doesn't happen is kind of a pain.

parasprite said:
A quick suggestion:

Requested feature: Urls like https://e621.net/forum/show/30573 get linked as-is even when formatted with DText like this one. Can we get a push that detects internal links and formats the url as /forum/show/30573 instead for DText links?

Why it would be useful: Users who browse e926 get linked back to e621 when links like this one are followed but not this one. Manually formatting them so that doesn't happen is kind of a pain.

They actually do

Edit: Nevermind... I had to read what was in the post n_n;

Don't know if it's already suggested, sorry if it is, but will suggest anyway^.^!

Requested Feature: Ability to "friend" users on the site for ease of sending pm's, following their favourites, uploads, comments e.t.c

Why it would be useful: It would Allow a better relationship between users, could potentially generate more views for artwork on the site if you check your friends favourites and see something you missed (perhaps you have different words in your tag subscriptions) and generally speed up pm's/ roleplays e.t.c

friends list plz

heheh too late

Add a favorite option for the sets.
As it is right now, the sets are very sparse in usability.
Adding the option to favorite/follow sets would make them far more useful than they are in their current state.

Lance_Armstrong said:
heheh too late

"Durandal"

I've... I've never had a friend before... ;_;

Requested feature: Update Tag History's search to distinguish between added and removed tags. So "-cute" would yield all recent tag edits that removed this tag in particular, or "+cute" would yield all edits that added this tag.

Why it would be useful: Additional clean-up power. Inspired by the "cute" tag argument that pops up every now and again, most recent being this one

A "shuffle image" button, for shuffling images displayed by tag searches or favorites. Mind you, the distinction between it and "random image" is that it'd reorganize ALL of the images and display them.

Is there a syntax that would work better for "Search for myself in forums" for users? For example:

https://e621.net/forum/search?query=blip
https://e621.net/forum/search?query=blip+said

If it could be done as an exact phrase search ("name+said") it could be even better.

Lance_Armstrong said:
Is there a syntax that would work better for "Search for myself in forums" for users? For example:

https://e621.net/forum/search?query=blip
https://e621.net/forum/search?query=blip+said

If it could be done as an exact phrase search ("name+said") it could be even better.

/forum/search?query=stuff+user:parasprite

Edit: Never mind, I just noticed it includes quotes. "TEXT user:USER" works better than "user:USER TEXT" though, the latter of which seems to show no results pretty consistently.

Siscokidder said:
A "shuffle image" button, for shuffling images displayed by tag searches or favorites. Mind you, the distinction between it and "random image" is that it'd reorganize ALL of the images and display them.

If I understand correctly, adding order:random to your searches should do the trick.

Add character count to compose blip reusing blacklist code:

<tr>
<td>
<textarea cols="40" id="blips_body" name="blips[body]" rows="20" style="width:540px; height:300px;"></textarea>
</td>
</tr>
<tr>
<td>
<input value="Post" type="submit">
<input name="preview" onclick="new Ajax.Updater('preview', '/blip/preview', {asynchronous:true, evalScripts:true, method:'get', onSuccess:function(request){$j('#preview').fadeIn('slow')}, parameters:Form.serialize(this.form) + '&amp;authenticity_token=' + encodeURIComponent('V02XbuvmSXETv3UJxE3CkdaReqaCrOeYxAHCVBPWyME=')});" value="Preview" type="button">
<a href="/help/dtext" target="_blank">Formatting help</a>
| <a href="/wiki/show?title=howto%3Acomment">Commenting help</a>
</td>
</tr>

<tr>
<td>
<textarea onkeyup="countInput(this,0,255,'blip-length')" cols="40" id="blips_body" name="blips[body]" rows="20" style="width:540px; height:300px;"></textarea>
</td>
</tr>
<tr>
<td>
<input value="Post" type="submit">
<input name="preview" onclick="new Ajax.Updater('preview', '/blip/preview', {asynchronous:true, evalScripts:true, method:'get', onSuccess:function(request){$j('#preview').fadeIn('slow')}, parameters:Form.serialize(this.form) + '&amp;authenticity_token=' + encodeURIComponent('V02XbuvmSXETv3UJxE3CkdaReqaCrOeYxAHCVBPWyME=')});" value="Preview" type="button">
<a href="/help/dtext" target="_blank">Formatting help</a>
| <a href="/wiki/show?title=howto%3Acomment">Commenting help</a><span class="blip-limit">
| <span id="blip-length" class="">0</span>/255 characters</span>
</td>
</tr>

There is some problem with the "Error: Body is too long (maximum is 255 characters)" appearing for a 255 or even 254 character message.

Lance_Armstrong said:
There is some problem with the "Error: Body is too long (maximum is 255 characters)" appearing for a 255 or even 254 character message.

I think unicode or line breaks might count for more than 1 character.

https://e621.net/blip/show/33111

Lance_Armstrong said:
I think unicode or line breaks might count for more than 1 character.

https://e621.net/blip/show/33111

If I remember right that was a Windows-specific thing.

https://e621.net/tag_subscription

Count number of tags in tag subscriptions edit box. Some assembly required.

<th></th>
<th width="15%">Name</th>
<th width="70%">Tags</th>
<th width="10%">Visible</th>

<th></th>
<th width="15%">Name</th>
<th width="65%">Tags</th>
<th width="5%">Count</th>
<th width="10%">Visible</th>

<tr id="tag-subscription-row-00000">
<td><input onclick=";" value="-" type="button"></td>
<td><input id="tag_subscription_00000_name" name="tag_subscription[00000][name]" size="20" value="Artists" type="text"></td>
<td><input id="tag_subscription_00000_tag_query" name="tag_subscription[00000][tag_query]" size="70" value="abluedeer" type="text"></td>
<td>
<select id="tag_subscription_00000_is_visible_on_profile" name="tag_subscription[00000][is_visible_on_profile]"><option value="true" selected="selected">Visible</option>
<option value="false">Hidden</option></select>
</td>
</tr>

<tr id="tag-subscription-row-00000">
<td><input onclick=";" value="-" type="button"></td>
<td><input id="tag_subscription_00000_name" name="tag_subscription[00000][name]" size="20" value="Artists" type="text"></td>
<td><input id="tag_subscription_00000_tag_query" name="tag_subscription[00000][tag_query]" size="70" value="abluedeer" type="text" onchange="document.getElementById('tag_subscription_00000_count').innerHTML=this.value.split(' ').length" onkeyup="document.getElementById('tag_subscription_00000_count').innerHTML=this.value.split(' ').length"></td>
<td id="tag_subscription_00000_count">0</td>
<td>
<select id="tag_subscription_00000_is_visible_on_profile" name="tag_subscription[00000][is_visible_on_profile]"><option value="true" selected="selected">Visible</option>
<option value="false">Hidden</option></select>
</td>
</tr>

Feature Request: Small pop-up window/ confirmation box when submitting a takedown, that points out, in easy words, to read the damn, red box on the next page.

Why? Because I get a huge influx of people who create a takedown without reading said red box, so they don't follow the instructions given in it.

Requested feature:
When you edit tags, submit only the differences

Why it would be useful:
You can accidentally overwrite someone else's tag changes. Example:

1) User A uploads an image of a wolf in a forest, and the only tag is:
tagme

2) User B edits the tags to:
unknown_species forest
(but doesn't save the tag changes yet)

3) User A edits the tags to:
wolf tree male solo cute
(and saves the tag changes => the tags are now: wolf tree male solo cute)

4) User B saves his tag changes
=> the tags are now: unknown_species forest
(because the tags from step 3 have been overwritten)

Suggestion:
When you save the tag changes, only the differences should be sent to e621.

Step 3 would send:
-tagme +wolf +tree +male +solo +cute

Step 4 would send:
-tagme +unknown_species +forest

The end result would be:
unknown_species forest wolf tree male solo cute

Descriptions and sources should probably be overwritten.

To add to Munkelzahn's, don't commit a tag edit if no changes are detected. That happens when you accidentally submit twice or too early

Request: Wiki count and average length for stats

stats on more under Reports

Request: Link on https://e621.net/wiki/add?title=text that takes you to https://e621.net/wiki/show?title=text

Faster to find alias/implications and posts for a blank wiki.

Lance_Armstrong said:
Request: Link on https://e621.net/wiki/add?title=text that takes you to https://e621.net/wiki/show?title=text

Faster to find alias/implications and posts for a blank wiki.

Everything about this.

I've actually considered writing a small script to automatically change the links but never got around to it.

Here's an idea.

For the FFD section, why hasn't "Irrelevant to site" been added yet. It seems awfully counterintuitive if you asked me.

...Unless other people would spam the hell out of it and flag whatever it is they see fit, such as those that despite Sega or MLP with a passion.

GameManiac said:
Here's an idea.

For the FFD section, why hasn't "Irrelevant to site" been added yet. It seems awfully counterintuitive if you asked me.

...Unless other people would spam the hell out of it and flag whatever it is they see fit, such as those that despite Sega or MLP with a passion.

Because "irrelevant to site" is not a valid flag reason. (Almost) all pics have to be approved by janitors/mods/admins even when not flagged. Flags are for objective things that could be missed by admins like DNP, repost etc.

Granberia said:
Because "irrelevant to site" is not a valid flag reason. (Almost) all pics have to be approved by janitors/mods/admins even when not flagged. Flags are for objective things that could be missed by admins like DNP, repost etc.

Ah, I see.

GameManiac said:

...Unless other people would spam the hell out of it and flag whatever it is they see fit, such as those that despite Sega or MLP with a passion.

Nah, if we went based on the FFD history it would mostly be old non-furry posts (human-only, aircraft art, humanoid aliens, whatever), which we aren't going to delete anyways.

parasprite said:
Nah, if we went based on the FFD history it would mostly be old non-furry posts (human-only, aircraft art, humanoid aliens, whatever), which we aren't going to delete anyways.

True. There are a lot of those, as I browse/work through specific tags (such as the dinosaur tag I recently went through from beginning to present).

I'm assuming they're there when this website had less standards, a period of time I wasn't there for.

It used to be impossible to submit images without tagging something first, but that stopped working some months back. And since then, some users have gotten into habit of uploading untagged images, and only tagging those later.

Which leads to the posts slipping through blacklists.

Could that possibly be changed back to how it used to be?

Not sure if this feature exists yet but here you go;
Requested feature:
Favorite artist
Why it would be useful:
Users will be able to favorite there artist and/or set them in the "My sets" tab. Similar to posts on e621.

badteacher4 said:
Not sure if this feature exists yet but here you go;
Requested feature:
Favorite artist

Tag subscriptions, if it's working for everybody.

See my profile page for examples.

Requested Feature:
For people with and without accounts, better overall blacklist coverage. Specifically, the removal of the ‘Blacklisted’ button under Mode on the Posts page, outright hiding white thumbnails labeled blacklisted in places like the Popular By Day page, and making avatars affected by blacklisting by default.

Why it would be useful:
I’m really picky about seeing the things I blacklist, so the places where they can still pop up can make my experience suffer; sometimes badly.

What really brings it down is that I’ve been trying to kick old habits with fetishes (because it’s no fun finishing too soon, you know?) so I blacklist them, but they can still pop up in avatars, the ‘Blacklisted’ button on the Posts page and in the white thumbnails; which can all tempt me if I get impatient or something. I enjoy being able to catch up on all the listings I missed since the last visit, but it would be so much easier (and more fun) to do that if I could run into less blacklisted stuff. Other sites I enjoy keep things ‘out of site, out of mind’ no problem for me, and no account needed to boot. Despite this, e6 is still my favorite and I wanna see it improve >:3

From a business standpoint, I think you would benefit adding those blacklist functions for people with and without accounts, because running into the things they blacklisted can turn them off from ever creating an account or coming back again. Not to mention odd cases like me, where it can be very frustrating trying to kick an old habit because you keep seeing it when you don’t want to.

And just from a reason standpoint, why would anyone ever want to see the things they blacklisted? Or know how many blacklisted things are on the page, AND be able to unhide them? Or see a white thumbnail taking up space; a space that could’ve just been filled with something they didn’t blacklist?

That’s my suggestion! Hope it made sense. Thanks for the site and keep up the good work! :]

Human-Shaped said:
Requested Feature:
For people with and without accounts, better overall blacklist coverage. Specifically, the removal of the ‘Blacklisted’ button under Mode on the Posts page, outright hiding white thumbnails labeled blacklisted in places like the Popular By Day page, and making avatars affected by blacklisting by default. (...)

Understandable standpoint, sound reasoning, but I think it'd be better to have this as an optional feature of the blacklist.

On the other hand, a "Blackhole Blacklisted Posts" option could be a nice addition to eSix Extend, so... @Xch3l: You up for the task?

EsalRider said:
@Xch3l: You up for the task?

I think I can give it a shot

Thank you both! :]

I didn't know about eSix Extend until now. If it's possible to make any of the things I suggested possible through that, I'd definitely use it!

I'd love to see them as official updates one day, but a script method would be useful.

Edit: When you say 'Blackhole,' does that mean completely hiding blacklisted things--as in 'even if you unhide them you'll see nothing' and 'you won't even see the white thumbnails with blacklisted on them?' Or would that just mean coding it so the 'Blacklisted' button doesn't appear?

Human-Shaped said:
Thank you both! :]

I didn't know about eSix Extend until now. If it's possible to make any of the things I suggested possible through that, I'd definitely use it!

I'd love to see them as official updates one day, but a script method would be useful.

IMO, eSix Extend is a great addition to the site. It changes a lot of things (including look-and-feel) and adds tons of useful features.

Edit: When you say 'Blackhole,' does that mean completely hiding blacklisted things--as in 'even if you unhide them you'll see nothing' and 'you won't even see the white thumbnails with blacklisted on them?' Or would that just mean coding it so the 'Blacklisted' button doesn't appear?

Depends on how it will be implemented. Simply hiding the "Blacklisted" button and the white Blacklisted thumbnails should be sufficient. I think. The tricky part will be to make sure it works properly on every page. Like, on the comments page, should only the thumbnail be hidden, or the entire block of the corresponding post?

Anyways, I think it'd be better to continue discussions regarding the script in forum #66904.

Could we have a new flag/deletion reason? Specifically 'Inappropriate Imagery'
To be used to flag images that either should not be uploaded do to a violation of the rules, or due it being posted specifically to troll.

Wolfiy_Dire-wolf said:
Could we have a new flag/deletion reason? Specifically 'Inappropriate Imagery'
To be used to flag images that either should not be uploaded do to a violation of the rules, or due it being posted specifically to troll.

That would open the FFD tool to a lot of abuse. The staff can find those kinds of images you mentioned through the approval/deletion process.

Yeah, posts that aren't approved yet rarely need to be flagged for that kind of thing. Troll posts can be a minor inconvenience, but they aren't actually malicious. Furthermore, flagging them won't actually bring them to the attention of the mods much faster than the approval process does as both are gone through multiple times a day. This is one of the reasons why we appreciate when users send us a dmail about it (malicious, RL porn, troll spamming) as it gets it taken care of sooner than it would through flagging.

parasprite said:
This is one of the reasons why we appreciate when users send us a dmail about it (malicious, RL porn, troll spamming) as it gets it taken care of sooner than it would through flagging.

I had wondered about that and almost added it to my post. Glad to hear that is an acceptable practice, and even more glad to hear it from an admin 'cause, well, I didn't want to sound like a total ass if I was wrong.
Is there a particular admin(s) that it is preferable to send such messages to?

edidaf said:
I had wondered about that and almost added it to my post. Glad to hear that is an acceptable practice, and even more glad to hear it from an admin 'cause, well, I didn't want to sound like a total ass if I was wrong.
Is there a particular admin(s) that it is preferable to send such messages to?

Probably NMNY , Parasprite , Husky , Ippiki or me would be my best guess. I've been a bit busy in RL atm so I might not see it right away though.

If it's something that is unlikely to be approved and still waiting in the moderation queue, it may just be handled that way and no dmail necessary. If it's linked to a bigger or more complicated pattern of behavior, or really is urgent then a dmail or a detailed ticket report are often the fastest ways to bring it to our attention and also let us know the full story of what's going on.

As a general rule of thumb, dmailing an admin works best when a situation is complicated or unusual and simply flagging it or writing up a detailed ticket report for it wouldn't really work. Or if you're unsure about it, have questions about something they did or whether something is actually reportable, etc.

If it's about suspected ban evasion though, probably pass it on to Ippiki since he really enjoys hunting those down, though reporting works equally well for that. And if it's about an artist's preferences or anything involving a takedown then NMNY would be in charge of that. Though sooner or later most things will probably have to involve filing an actual takedown form if it's because they want something deleted or their status changed.

Ratte tends to focus their time mainly on tickets, and some of the other admins are more behind the scenes. Spight and Tony are the site developers, though it's usually easier if any bug reports get added to the bug report thread that's in the forum instead of through a dmail. That way it's easier for them both to reference the reported information and they read that thread regularly. Other admins like dragonranger, ktkr, etc are more involved behind the scenes so they may or may not be as able to help with questions.

If you have a problem about an admin and want to have it looked into, you can Dmail EDFDarkAngel1 (the lead admin) about it and he will look into it if needed.

If you have a problem with EDFDarkAngel1 (the lead admin) and think something they did needs looked into or reconsidered, you can Dmail DasaDevil about it and they'll look into it if needed.

And the full list of admins is here.