Feature suggestions and discussion [READ THE FIRST POST]

@Background Pony #F1  
When did two character background pony IDs become a thing?

@Joey  
They’re a bug and only exist in the rails backend. It’s because the hash is computed as an int, masked off to a short, and then converted to a string using ruby’s to_s, which doesn’t (can’t) pad it to the correct width.
 
I could fix it but I honestly cba at this point

PM only works between two users

If someone goes to upload something from another artist that is on the DNP list, they should get a warning before they do it.
 
artist:x + edit + DNP (no edits):  

 
artist:x + DNP (artist upload only):  

 
artist:x + DNP (with permission only):  

@Starry Mind  
Afaik, you already cannot upload an image, if artist is on DNP

StSyaN  
Oh, I never knew. I keep seeing a bunch of people making posts regardless.

@Starry Mind  
You still can upload an image without artist tag and add it afterwards. And there is no adequate ways to fix that.

@Starry Mind  
Wen you see that, please report the image.

@Badheart  
That’s intentional.

When a gallery is opened, could the gallery ID be displayed in the search bar? Something similar to how opening a tag adds the tag to the search bars. I search my galleries a lot, and right now I need to click on an image in the gallery to get the gallery ID in the search bar, so this change would be handy.
 
Edit: Looks like the Philomena beta has this feature, so ignore.

@Starry Mind  

You did it. Thanks for adding this! :3

Updating the site seems to have re-enabled subscribing to an image when commenting on it. How do I disable it again? Can’t find the option
 
Edit: Speaking of subscribing, does it no longer show how many people are subscribed to a gallery? That’s kinda disappointing

@Raritybro  
Subscriber counts seem to no longer be a thing… And what’s “Relevance”?

It would be nice to have auto-complete/auto-suggestion in the search bar too. It would especially help with writing artist or OC names, because I might not be fully sure about the spelling of their name or if they have a comma or a space or something else in their artist name. Auto-complete would make this a breeze.
 
Additionally, it would be nice if the search bar expanded on larger screens to fill the empty space between it and the notification bell. It would make it easier to use and write more complex search queries that are too big to fit in the current search bar. Of course, you can already write them, but if you later want to edit them, then it can be a bit of a pain. Or you can lose track of everything you have written already in it because right now, the search bar is pretty small.

Arranging tags in the tag edit field by the order in which they appear when grouped by color is a terrible idea, and should be changed back to alphabetical order.

@TexasUberAlles Alternatively, that could be a setting that everyone could toggle so they can pick whichever fits them best. Personally I like how it is now and I imagine many other people do too.

@Lynn Heart  
A toggle for people who want it is fine, but it is still a terrible idea.

@Lynn Heart  
for the former, you can just use a wildcard and the first few letters like artist:chee* (for example) if you aren’t sure of the tag’s spelling.

@Background Pony #FA41  
Whoops, posted anon.

Hey, posting pictures from external sources is not working for me.
 
Example 1:
 
Example 2:
 
I know I’m doing something wrong. I need detailed instructions. Please and thank you. Haha. I’m embarrassed.

@WinterFlower154  
Those aren’t image links, those are links to webpages.
 
The image link generally ends with an image file extension, like .jpg, .png, or .gif (though it doesn’t necessarily have to). Your browser will inform you when you are directly viewing an image, as it will show information about the image in the page title.

@byte[]  
Okay! Thank you!

So this is more of a comment than an actual feature request. If nothing happens, then I don’t think anyone other than I will ever actually notice or care.
 
Booru-on-Rails had a version string in the footer that included the active version’s branch and commit hash (“1.4.0-a525c3 (master)”), while Philomena lacks one, and simply says “Powered by the Philomena Project”. This means that there’s no immediately obvious way to tell which commit is currently the “live” version.
 
This is mostly a curiosity thing. But it was still nice to know sometimes if there were staged commits that haven’t been deployed yet.
 
I could take a stab at adding this too, if preferred. Or if it was intentionally omitted for a reason, then it’s not a big deal (and I can just login to the server to look if I’m that curious)

@Joey  
I wanted to add it but there is a bunch of compile time nastiness with Mix that needs to be sorted out before I think this will be practical.

Feature request: removed comments should also remove the notifications
 
If the only comment(s) made since your last visit to a post have been removed, the notification should be deleted. It’s silly to get a notification for “new comment! Removed for rule 1”
 
I have no idea if this would screw over database performance, though.