Forum
>
Site Discussion
>
Thread
Log in |
Register
I think it would be a bad idea. One of the great things about GWM is that there are hardly any haters or trolls. That's because most of the users have more general tastes, we like Natalia Trukhina and Alessandra Alvez alike. Take a look at the high scores of the day. If you give people the option to only see what they like, you are fragmenting users into different groups of fanboys, who would probably start to become haters and trolls over time. Remember this is the internet...
I disagree. I don't think it would have an impact on scores. This site uses a +1 system, instead of a 1-10 rating, which I think promotes a much more positive environment.
For the most part, I don't see this site as a high discussion type of environment. Sure, there are some here and there, but for the most part, we just want to check out the hot pics.
If I'm looking for strawberry, I don't want to be bombarded with a bunch of lemons.
To exclude a person from anything by default isn‘t the way it should work. You wouldn‘t like to be excluded from beeing found by any kind of search just because your nose or your opinion as well. It‘s simply no way to treat people.
To exclude a person from anything by default isn‘t the way it should work. You wouldn‘t like to be excluded from beeing found by any kind of search just because your nose or your opinion as well. It‘s simply no way to treat people.
Nobody is proposing to exclude anyone by default. This is a per user private feature that wouldn't affect anyone else. Next to the subscribe button which appears for girls now there would be an ignore button. That's it.
This is a reasonable request. At first thought, from a technical point of view, I am somewhat worried about the performance implications, for example if every query to the database for a bunch of images also includes 20 names to filter out. I might be able to have a workaround though.
Thanks Chainer for considering this feature! Databases are great at this sort of thing, when properly designed and indexed.
One option might be a separate lookup table that is included in the search only when user is logged in. A search can outer join to that new table, and exclude any matches.
There are several ways to accomplish this, and the right solution obviously depends on how your data model is currently architected, but it's a solve-able problem. (My day job is as a DBA)
I don't think it would have an impact on scores.
It could have consequences on the score. Let's suppose that Natalia Trukhina gets 100 points and appears in the "Highest scores today", but there are 30 users who blocked. In the Highest Score grid, those users who blocked her will have an empty place, which will be occupied by another model. If that model has 80 points and the 30 users give it +1 or fav, then it would beat Natalia with 110.
That would be very unfair.
This that I have just explained is perfectly possible, following the thread of this forum it is quite clear that the most blocked ones are going to be the big models like Natalia.
It could have consequences on the score. Let's suppose that Natalia Trukhina gets 100 points and appears in the "Highest scores today", but there are 30 users who blocked. In the Highest Score grid, those users who blocked her will have an empty place, which will be occupied by another model. If that model has 80 points and the 30 users give it +1 or fav, then it would beat Natalia with 110.
That would be very unfair.
This that I have just explained is perfectly possible, following the thread of this forum it is quite clear that the most blocked ones are going to be the big models like Natalia.
Actually, I think that just makes it more fair for the other model.
What you see on your highest rated page, shouldn't necessarily be what I see on my highest rated page. Those that would block a certain model, were likely never going to rate that model anyway.
Unless you view this all as a competition. I do not. But if there is a page on the site that is a competition, then it's not very technically difficult to include ALL models on that page.
I'm just suggesting that the search have a checkbox to block the models on your ignore list from appearing in search results, and from there, the site already has nice ways to sort the results.
Why do you want to force me to look at models that kill my buzz?
Actually, I think that just makes it more fair for the other model.
The problem is that the highest score on the Home page has limited space (10 images or 50 expanded). It would be unfair because originally that model had 80 and Natalia would have 100 in my example. So those 30 extra points would be taking away Natalia's visibility and preventing her from going above 100. Once those 30 users log in Natalia would be stuck at 100.
The Home is very decisive in this aspect. The first thing I do is click on "highest scores" and "recently uploaded".
Anyway, if this blocking system only applies to custom searches (those on the Images page) there should be no problem.
What you see on your highest rated page, shouldn't necessarily be what I see on my highest rated page. Those that would block a certain model, were likely never going to rate that model anyway.
Completely agree. I'm almost always unable to properly use the sorting by highest score because of this problem. Being able to exclude what you're not interested in, would actually make the scores usable to find pictures. And it would improve the overall use of the site.
Then there can be an option to toggle off exclusions in the search, like there is now for "videos" or "hidden gems"
The problem is that the highest score on the Home page has limited space (10 images or 50 expanded). It would be unfair because originally that model had 80 and Natalia would have 100 in my example. So those 30 extra points would be taking away Natalia's visibility and preventing her from going above 100. Once those 30 users log in Natalia would be stuck at 100.
The Home is very decisive in this aspect. The first thing I do is click on "highest scores" and "recently uploaded".
Anyway, if this blocking system only applies to custom searches (those on the Images page) there should be no problem.
Basically you are just annoyed that some other girl than your favorite might get a bit more visibility, who otherwise would have got less attention. You give new meaning to the word selfish.
Besides those who are into Natalia can and would block slim and smaller girls, so the effect would even out in the top 10.
Besides those who are into Natalia can and would block slim and smaller girls
This is exactly what I mean. In other words, some users will block Natalia and Natalia's fans will block other "thinner" models. That's a perfect breeding ground for trolls and haters to emerge. And these haters could perfectly put an offensive comment and then block the girl. Or block some girls and reserve others for hating.
This phenomenon of loss of visibility of models with many blocks will occur. It is obvious that Natalia Trukhina is going to be the most blocked model. Since the new scoring system was introduced, she has obtained very good scores. It would be very unfair if her score was lowered by excessive blocking.
If this system is implemented it should not affect the Home.
A cheap implementation, which would avoid a database hit, would to be return a JSON to the front end with the filters and then have the 'offending' images greyed out.
The challenge with applying the filter on the server side is when there are many women in the exclude list. This may mean that there were would be a maximum number of women that can be on the exclude list. Having this limited to tags and limiting the number of tags you can filter out could be a compromise?
A cheap implementation, which would avoid a database hit, would to be return a JSON to the front end with the filters and then have the 'offending' images greyed out.
The challenge with applying the filter on the server side is when there are many women in the exclude list. This may mean that there were would be a maximum number of women that can be on the exclude list. Having this limited to tags and limiting the number of tags you can filter out could be a compromise?
Disagree. Filtering is exactly what relational databases are good at, assuming they are properly designed and optimized. Granted, I'm assuming there is a relational database powering this site. Serving content is a cost. Why not minimize the cost of sending irrelevant content?
Clearly the developer(s?) has solved some technical performance challenges on this site. Search runs fast, image and video thumbnails are quick, and there is a boatload of content storage and delivery. And yet some aspects of it seem fairly dated, by today's standards. Seems like a side-project that has grown to fit a niche demand.
I'm ignorant of the back end architecture, but this shouldn't be a technically challenging feature. I'd be happy to volunteer to help if time and effort are what's missing.
Funny enough, MySQL is my database specialty. If that's the case, like I said earlier, I'm open to helping out for free.
My time is limited, but I enjoy contributing to projects I have an interest in. Selfishly, it would improve my own experience with this site too.
I would love to be able to ignore the myriad of gender confused "girls" on this site. Paige Dumars most of all.
I use the search quite a bit to view a list of recently posted, or highest rated today, this week, etc...
Similar to "favorites", it would be great to have a "ignore" list for girls that just aren't your type, so that you can avoid having those come up in searches.
We all have individual preferences, this would help personalize the user experience a bit better.