Log in | Register
Forum > Site Discussion > Thread

Feature requests related to building a favorites collection

Oct 15, 2021 - edited Oct 15, 2021 - permalink

Some of us are inexplicably obsessed with building up our favorites collection.

Having a way to filter out our existing favorites from advanced search results streamlines this process.

It should be a straightforward matter of adding a negated WHERE clause to a SELECT statement somewhere...πŸ‘“

It's a bit like a more general version of "recommended for you", possibly being equivalent to an advanced search in "recommended for you".

In fact, adding a checkbox for "recommended for you" into advanced search probably would achieve a similar outcome.

Maintainers: Please consider adding this enhancement to an already awesome site. Thanks

Oct 15, 2021 - edited Oct 15, 2021 - permalink

The above request is actually related to supporting users in maintaining their own personal view of liked vs disliked images&videos. Each image/video is actually in one of three states from a user's perspective: liked, disliked, or not yet seen.

So, a related request is: Is it possible to allow users to track this type of three-valued state per image/video?

I know there was a problem with "zero-bombing" with the old scoring system and hence it was removed.

So I am suggesting that likes continue to contribute to a publically accessible popularity score, but that dislikes are private and don't detract from it.

I suppose the +1 feature is a kind of third value of the state already. But it's the wrong kind for the purpose I'm expressing here. Why should my setting +1 on an image/video to track my private dislike of it contribute to its public popularity? That's perverse.

Chainerβ˜…
Oct 16, 2021 - permalink

Having a way to filter out our existing favorites from advanced search results streamlines this process. It should be a straightforward matter of adding a negated WHERE clause to a SELECT statement somewhere...πŸ‘“

You're right that implementing it is that simple, but this doesn't take performance into account. When you're trying to exclude a large number of images from the query, it can slow it down significanly.

I ran a test (in my dev environment) where I implemented this and tried to load a page of the image gallery using your account (filtering out your favorites), and I did not notice a significant slowdown. But then I tried the same thing using this guy's account, and it's been loading for about 5 minutes and it's still not done.

You have about 50,000 favorites and he has about 430,000. I don't know where the line is between "reasonable" and "completely disastrous". It seems it may not be a linear relationship.

So I am suggesting that likes continue to contribute to a publically accessible popularity score, but that dislikes are private and don't detract from it.

What would be the point of a dislike button if it doesn't detract from the score?

If it's meant to hide those images from view for you, it runs into the same performance problem once you have used it a lot (on hundreds of thousands of images).

Oct 16, 2021 - permalink

Would it be possible to implement a way to allow for mass favorite deletions? I.E. so I could select and delete a large number of pics from my favorites. After some 13 years here, I have a ton of pics in my favs that I would love to remove, but doing it one at a time is just too time consuming.

Oct 16, 2021 - edited Oct 16, 2021 - permalink

Thank you for taking the time to look into this, Chainer.

Regarding the "exclude my favorites" proposal: I didn't think about performance and although I am a dev myself (surprise! ☺), I don't know enough about databases to be able to comment in retrospect on whether your findings are to have been expected.

Regarding the "dislike" proposal: I presume that as the dev of this site, you will have eyes on the big picture (how do features affect the system as a whole?) but not necessarily so much on the user experience (how your design decisions affect us).

(user experience... heh! πŸ˜’)

So I wanted to offer that alternative perspective. Since I find myself passing judgment on a never-ending stream of content, it would be helpful to have an unbiased way of tracking what ground I've already covered, as opposed to the great ocean of beauty that still lies undiscovered before me. (with apologies to Sir Isaac)

As things stand, I can see what I have judged favorably in the past. But I recognize that I will also be inefficiently and unknowingly repeatedly revisiting content that I have judged unfavorably in the past.

It would be a better πŸ’‰userπŸ’‰ experience for me to be able to:

  • Focus on novel content - ideally being able to choose not to stumble across content that I've already decided I don't like.

  • Focus on building the collection of what I do like without rehashing it in the process - by excluding what I've already decided I do like.

  • Focus on appreciating my existing collection when I feel inclined to do so.

Currently, only the third option is fully available to me through the existing favorites functionality. And the first option is available in restricted, inflexible form through the "recommended for you" functionality.

Oct 16, 2021 - permalink

I posted a feature request related to organizing favourites into "Collections", but it didn't gain traction. Posting it here in case the mods missed it:

https://www.girlswithmuscle.com/forum/thread/...

Chainerβ˜…
Oct 16, 2021 - permalink

Yes, I am aware of the favorite grouping suggestion, it has been proposed several times. I could see myself implementing it but it's not terribly high on my list at the moment. I'd want to think about whether there is any overlap to be had between that and overhauling the tag system since both of these ideas have something to do with categorizing images. Regarding the tags specifically, I haven't made much progress on that front. It's the kind of large overhaul I would only get into once I was very sure that I had a great replacement, and I haven't been sold on anything that's been proposed nor ideas I've thought up myself.

But I recognize that I will also be inefficiently and unknowingly repeatedly revisiting content that I have judged unfavorably in the past.

With over a million pictures on the site, do you really stumble upon old pictures repeatedly that much? Actually, I am curious: what is your workflow for finding old images you like? Help me understand.

And the first option is available in restricted, inflexible form through the "recommended for you" functionality.

There is an improvement to the recommendations coming ideally in the next few months, so keep an eye out for that.

Oct 16, 2021 - permalink

I'd want to think about whether there is any overlap to be had between that and overhauling the tag system since both of these ideas have something to do with categorizing images.

I think the advantage of implementing the Favorites grouping is that it allows users to make groupings according to their own idiosyncratic likings/kinks, and additionally have the option to keep these groupings private (within their own account). I'm not sure how you plan to implement the tag system, but I would think that tags can only exist if enough users find them useful, and hence by definition be somewhat generic and public.

Oct 16, 2021 - permalink

With over a million pictures on the site, do you really stumble upon old pictures repeatedly that much? Actually, I am curious: what is your workflow for finding old images you like? Help me understand.

Well, quite often I'll begin by searching for a particular model, some of whose content I will have favorited before, and some of whose content I may not like, but will have been unable to mark as such.

At this point, it would be convenient to be able to refine the search to efficiently separate out what I have seen before (and liked or disliked) from content that has been added since I last searched for that model.

As things currently stand, I would have to revisit an image and redecide which category it falls into. As more content is added for the model in question, the set of images/videos that is new to me will eventually be small compared to what I have already seen for them.

So it feels to me like my procedure for judging their content ends up being quadratic over time in the total amount of their content on the site when it could be linear if the suggestions I'm talking about were in place. πŸ‘“

Bear in mind that I'll be following this process randomly across many models at once in a given session, so I have no way of tracking new content for a specific model in a working state that persists across sessions.

I am aware of the Subscribe functionality, but enabling it for all the models I'm interested in would result in an overwhelming number of notifications, and drown out the sort of notification signal I am perhaps more interested in - namely whether and how any site user has responded to the comments that I so enjoy posting.

There is an improvement to the recommendations coming ideally in the next few months, so keep an eye out for that.

I look forward to it. ☺

« first < prev Page 1 of 1 next > last »