Feature suggestions and discussion [READ THE FIRST POST]

Here is a suggestion maybe other people also would like.

I know the Desktop Ponies were just added as an April Fools joke,
but wouldn’t it be cool to keep them as an option in the settings after April Fools is over?

@JustMarvin123NL
I agree. For context, Fimfiction has a setting to release a Rainbow Dash on your screen.
_{Now I hope Fimfiction ups their game by populating your screen with ponies chosen from the story’s tags with RD as a default for when no tags match.}

@JustMarvin123NL
I’d also love for a setting to keep the Desktop Ponies on! They were so cuteeeeee

@Cerulean Draw
As a temporary solution, the script in the description of >>3334181 works well. You can also have as many ponies as you please.

@🐴
OH MY GOSH THANK YOU, this has improved my life significantly (at least on Derpibooru)

As someone who loves statistics, I’d really appreciate the possibility to export my user data (at least my upvotes/downvotes) to a file I can download. Using the API to get all my upvotes and downvotes is slow, annoying and puts load on the server, which could be avoided by having the option to simply download my upvotes/downvotes.

There’s already “A implies B” for tags. But how about “C implies not D” so you e.g. can’t tag a safe image “solo female”? Might avoid mistakes.

Suggesting for a friend.

@.
So basically a tag linter? It’s a very good idea. We could have both hard errors (so user can’t save tags if both “safe” and “grimdark” are tagged) and warnings (when there’s a combination that technically could be valid, but usually is a mistake).

@.
@Background Pony #2A5F
This “negative implications” system has been proposed in various forms many times over the years. Unfortunately, it has not been deemed important enough to be implemented.

It would be useful, though.

(Speaking of “tag linting”, I have a long list of things that could be done to clean up some common and uncommon mistakes.)

There is for ratings, but that’s about it.

@JP
Maybe it would be easier to create an external tool that periodically checks tags using the API?

Had this come up in the comments of some image, I think there should be a field to add next to a source that allows you to enter the “originally posted date”, or perhaps having this field global to the image and just having one chose the earliest date it was seen, rather than needing it per-source. This data could probably be auto-fetched too when using the image fetch from some source URL feature.

With this people would be able to sort images by “original upload date” rather than when they were uploaded to Derpi or search on such a range, which could help organize things chronologically better (for those who want to search the site like that). It’d also be useful just to see what timeperiod a piece of art was made in if in the future the original source is dead and the source page wasn’t archived anywhere.

I’d imagine the sorting/searching would use the originally posted date if available otherwise just fall back to the upload date, or something like that (since obviously most stuff is not going to have this metadata until people start adding it to existing uploads).

@LemonDrop
Might it be further possible, for when people post Twitter/FA/DA/etc… links to the upload box to extract the original post date with the scraper? We could even backfill data for images with the source field filled in this way.

@🐴
Probably, I mean Twitter is kinda lame these days so I am not sure how easy it is to get that data (maybe scraping it’s not so bad, but the API is kill). But yes it should be able to be automated to a degree to fill in the old info if that’s desired.

@LemonDrop
I agree with this

Ever thought “Oh dear, I’ve totally misunderstood how to use the xyz tag, and now there are 200 pages of tag changes on my account to look through to fix this mess?”

I’ve made a small change to add a search box to the tag change page of the profile to help with that.

Code available here: https://git.lacunae.de/philomena.git, branch tag-change-search (don’t try this link in a browser, you can only add it as a git remote.)

@.
someone give this person a medal

@.
Are you interested in having this change pulled?

@byte[]
Would be great to see it on the site, yes. There are a couple of tag changes I’d like to review.

Has anyone looked at the potential for CSS grid masonry for an alternate frontend CSS in a few years?

If you have Safari’s developer build or Firefox with the flag I linked above enabled, go check out this photo gallery demo. Especially check out the “wide images are wider” option.

Perhaps it could display the meta info (vote buttons & comment count) on mouseover on desktops but include it as part of the image’s box for touch-only environments.

Notifications

I want the first thing displayed to be the thread title instead of user names, having the titles pop up in one place on the screen will make them easier to find.

I want that option.

@byte[]
Your fixup commit made the code a bit nicer, but it now also leaves an empty “only_tag=” parameter that keeps getting generated in links on the page when it’s not needed because a search has been performed with an empty input box. Also the filter when constructing the pagination_params could be a bit simpler I believe. You’re always constructing a kw list with all the possible params which will either have a proper value or nil, then filter out the ones that didn’t have a key in the original map. So Keyword.filter(fn {_k, v} -> v end) should do the same here, right? Then add a && v != "" to it and we get rid of the useless “only_tag=”.

@.
https://github.com/philomena-dev/philomena/commit/ba87c1679e57ba28e91352b45574fab0141b0cbe

I’ve made another small change that adds the total number of affected images to the bottom of the profile tag change page. It’s again at https://git.lacunae.de/philomena.git, branch tag-change-image-count if you’re interested.

@.
This distinct count would probably be too slow to run for a lot of users.