Such a thing already exists. It's called 'not clicking on thumbnails of pix which don't interest you'.
Precisely. It's like people who complain about programmes on TV. Why would you watch them!
No but i do think we need a dislike button for videos that are just slide shows. or water melon crush videos that have dubstep as background music. and video with filters that make it look like vhs .despite being a modern video .or when they have seasure enducing effects.
If a video is just a slideshow, with static images or rapid fire scenes, then please do report them. For melon crush videos, if the muscle isn’t easily visible, then you can let us know too.
Such a thing already exists. It's called 'not clicking on thumbnails of pix which don't interest you'.
This is pretty much what I said when people were upset about Eunhee being on the site. If you don't like her, don't click it. Yet here we are.
This is why a block feature would be a good idea. Let people decide for themselves who should and shouldn't be in their feed instead of one person deciding for everyone.
It's just another filter that's already being used in different ways across the site. A filter that would only be run if a user is logged in and has blocks.
Its more that the building a database query to exclude certain entries can become very computationally expensive. It is not that it can't be done, just that implementing it is not straight forward. Also, consider developing and improving GWM is still very much a hobby project, so Chainer's day job and life will take priority. We may see this in the future, but I doubt there is any urgency in implementing this?
BTW there are probably less elegant ways to achieve this, like someone writing a piece of Javavscript in the front-end just to hide entries, but they you'll simply find yourself with empty blocks on the page. Something like Tampermonkey, but you'll need to code it yourself.
Its more that the building a database query to exclude certain entries can become very computationally expensive. It is not that it can't be done, just that implementing it is not straight forward. Also, consider developing and improving GWM is still very much a hobby project, so Chainer's day job and life will take priority. We may see this in the future, but I doubt there is any urgency in implementing this?
BTW there are probably less elegant ways to achieve this, like someone writing a piece of Javavscript in the front-end just to hide entries, but they you'll simply find yourself with empty blocks on the page. Something like Tampermonkey, but you'll need to code it yourself.
What's the site written in? I suspect it's built with Django, but I could be entirely wrong on that. If it is Django, I wonder if the following could work, roughly:
if request.user.is_authenticated:
blocked_list = request.user.blocked_list # There are various ways of accomplishing this part
DatabaseObjects.exclude(name__in=blocked_list) # then pass to context and you have your filter
Of course, it's hard to say exactly without knowing the backend. It's fun to theorize though. Conceptually, something along those lines could work (again assuming Django's ORM is at play here). A new field would have to be added to the User model to store a list of blocked names. Then the filter would operate off of that list. An additional conditional can be input to ensure a user has blocks first.
All this stuff about blocking things reminds me of the standard Timorous Tim Debacle.
I don’t think it’s a bad idea, it would be a sort of personal filter that would not affect other users view experiences. Not even disrespectful, just fine tuning each member personal preferences.
I also think this feature would be super nice
Can we block models we don’t want to see?