a thoughtful web.
Good ideas and conversation. No ads, no tracking.   Login or Take a Tour!
comment by rinx
rinx  ·  3172 days ago  ·  link  ·    ·  parent  ·  post: What freedom of speech isn't

I think the problem is the hubski bar analogy falls apart when people are pushing an agenda. He isnt here to participate, he never comments unless its to argue about his hate topics. The problem is, in a bar, everyone would notice that he's in a dark corner of the room, smelling a bit off, with no one talking to him. No one goes up to that guy. On hubski, it just looks like no one is commenting on his posts. Normal users don't see whats wrong with him until he has a toxic day, and even then they might miss it. So how do we show people his stink waves? It seems like there should be some way to let the community know "yes this person is talking, but our silence is not agreement".

On way would be to show how many people have muted someone for a particular topic. I don't want to be hurtful though, or create a negative experience for controversial tags.

Another way would be letting people untag his posts, kicking him out of the room so to speak. Either a hubwheel of "offensive" or "controversial" gives users a warning when viewing content, or deletes the tag entirely. Yes we can filter "spam" or "trolling", but I think it would be better if this was baked into the site itself. If a new users checks out hubski and sees a skull and crossbones next to a post, it sets expectations pretty effectively. It also lets normal users know "hey, this guy is a controversial figure, silence is not agreement".

I feel a little weird proposing suggestions, I know I'm a hubski rookie. But I don't want to be negative and just whine about things I don't like without offering suggestions. So I'm very open to criticism or disagreement on this one.





user-inactivated  ·  3172 days ago  ·  link  ·  

    a hubwheel of "offensive" or "controversial"

My first idea as I read this thread further was the red hubwheel, but it came to me soon after that it can, too, be abused. Perhaps not as heavily, since I haven't noticed trolling in such quantities on Hubski, but still, it's the opportunity I'm uncomfortable with. Test run, perhaps, with saving the data if it proceeds to a feature state?