Feature suggestions and discussion [READ THE FIRST POST]

@Background Pony #2A5F  
Thanks m8

One suggestion that would be very helpful for me if implemented would be to either get rid of the minimum limit of images per page in Display Settings, or lower it to 12. I usually browse Derpibooru on my smaller, side monitor, and 12 is the optimal amount of images for that (two rows of six images).
 
I set it to 12 before the minimum limit of 15 was added, so I still have it as 12, but I can’t change any other settings since it says I have to change it to be no less than 15 when I try to save my settings.

@Awkward Segway  
89d3ecc

A pretty minor suggestion but could inline code get some better styling? Just a slightly lighter background or something. Right now, it’s hard to tell what's code and what’s not, since the only difference is monospace font.

@Angius  
This

@Marker  
I will third the motion.

Any way of saving comments? Kind of like what you do when you upvote images (It gets saved on a upvotes folder), it would be nice if you could save an explanation of a mod, a headcanon of someone or anything you wish to save and don’t want it to be lost in the endless stream of messages that keep coming (Especially on threads). It would also be helpful if you want to save a comment that you can’t report due to the report limit thingy. (Something I’ve heard a lot)
 
By the way, I have to say I’m interested on the 12h free ban chance; my friend would surely love to participate xD.

@Background Pony #8601  
I agree and also forum posts too. It would be nice to even be able to organize them into galleries of sorts so can organize them later.

@Background Pony #8601  
@Cosmas-the-Explorer  
Why not simply bookmark them? Every image comment and forum post has a “Link” button in the bottom right corner that points to that comment/post; you can copy/bookmark the URL from it directly.

@JP  
And if you afraid about tons of bookmarks, you can start DM with yourself here to store all needed stuff

A suggestion i have is to make it so that spoiling/hiding one tag automatically spoils/hides anything implied by that tag.
 
Like, if you spoiled the “applecest” tag, it should auto-spoil the “incest” tag.
 
Or if you hid the “gore” tag, then it should auto-hide the “grotesque” tag.

@LeaveTheBronx  
That would probably cause more trouble than it would save.
 
You would filter out a shipping that grinds your gears particularly bad, and would end up also filtering out each involved character, and the orientation tag too. Or filter out “hyper breasts”, and also “impossibly large”, “huge”, and “big breasts”.

It’d be great if you could change the spoiler image behaviour on mobile (doesn’t even show up when requesting the desktop version), or better yet if it switched to a local setting so you could have one behaviour on mobile and another on desktop.

@saby  
i went back to the drawing board and came up with this: how bout we make it a drop-down setting? ^{i’m going to use the flutterdash tag as an example}  
“Yes” = auto-spoils/auto-hides the tags implied by ‘flutterdash’  
“Prompt me” = ‘Do you want to also hide/spoil the tags implied (female, fluttershy, rainbow dash, lesbian, shipping)?’ with buttons saying ‘yes’ and ‘no’  
“No” = doesn’t auto-spoil/auto-hide the tags implied by ‘flutterdash’
 
The default would be “no”

@LeaveTheBronx  
I really can’t see why you’d ever want to turn on that functionality. It goes directly against the definition of implication and is basically unusable outside of some edge cases.
 
If you want to stay with the Flutterdash example (or any other ship involving a female character, for that matter), hiding/spoilering the implied female alone would affect over 1.3 million images featuring a female character regardless of context. That’s over half of the images on the booru. Because of a single ship between two specific characters.
 
If you want to use a feature like that only for tags that imply a single, small(-ish) tag, then just manually hide/spoiler that tag and you’re done. Like, going back to your original post, just hide/spoiler incest and you don’t even have to do anything about applecest anymore, since all the images with it are hidden/spoilered due to the implication anyway.

The Do Not Post list has too many pages to quickly find names. I request that all DNP artists be listed on a single page to allow for both quick browsing and a CTRL F search.

@kleptomage  
Also add searching by date.

(yay another stupid suggestion from yours truly)  
You know how Archive Of Our Own gives you the ability to orphan a work, i.e. making a work dissociated from you?
 
How about something similar? We can make it so that, if a person is really sure that they don’t want an artwork associated with them, but don’t want it gone from the site entirely, they can orphan it.
 
Orphaning an artwork makes it so that the original poster (herein referred to as OP) is changed to Background Pony (anon) and the comments made by the OP are changed to appear anon as well. If the OP of the picture was the artist, then orphaning it removes the artist tag. It will also remove the source, unless it was Derpibooru exclusive. Only the OP can request an upload to be orphaned, so as to prevent abuse.

Artists can already do that by contacting a mod and asking for an image to be deleted, then re-up it as a BP later if they want. Uploaders who aren’t the artist seem unlikely to get such consideration.

@TexasUberAlles  
Sure, though it’d be nice for it to be integrated into the code.

@TexasUberAlles  
It’d make it so that if the OP wasn’t the artist, they’d at least have a way to distance themselves from the art if, say, the OP accidentally started a war in the comments. Plus it’d eliminate the whole process (i’m not saying it’s a hassle, though it might be) of having to contact a mod to take it down, then re-up it later.

@LeaveTheBronx  
A long time ago it used to be possible for users to anon or deanon the uploader field on their images but the feature was removed. Not sure if it’s possible for the mods to switch the uploader anonymity on the current engine.

@LeaveTheBronx
 
@TexasUberAlles
 
@byte[]
 
I thought the current solution was the artist could contact a mod and have their artist tag converted to a generic artist:PHP tag.

I’ve asked for this before, but might as well try one more time.
 
Could we have the option to hide an upload from appearing on the front page? When one goes to post a particularly squicky fetish pic, it’s always luck of the draw how long it sticks around on the front page and how many people are going to see it. And no, filters aren’t the answer since people don’t. It sucks an incredible fat one when you post something you know 99% of people are going to hate, but you have no option other than to force it on the world.
 
With the way it currently works, I have to tiptoe around posting certain things, hoping someone will flood the front page with EQG screencaps or some other crap so it gets flushed away before too many people have the chance to see it. You know, the reverse of what one would usually want.