How do we enable more positive serendipity & discovery via our websites, between both existing friends & family, and new positive interactions. And how do we raise barriers to spam, harassment, and other unpleasant social media interactions.
It's not just "fixing comments", it's much more than that.
Respectful responses include even simple interactions like likes, bookmarks, and reposts, as well as indirect comments like quote tweets.
A broader user-centric conversation about the problem that Vouch is designed to solve one or some parts thereof.
While writing things out loud to no audience can be helpful and useful on an individual level, it’s often even more helpful to have some sort of productive and constructive feedback. While a handful of likes or positive seeming responses can be useful, I always prefer the ones that make me think more broadly, deeply, or force me to consider other pieces I hadn’t envisioned before. To me this is the real value of these open and often very public thought spaces.
For those interested in the general idea, I’ve been [bookmarking/tagging things around the idea of thought spaces I’ve read on my own website](https://boffosocko.com/tag/thought-spaces/). Hopefully this collection helps others better understand the spectrum of these ideas for themselves.
With respect to the vulnerability piece, I’m reminded of an episode of The Human Current I listened to a few weeks back. There was an excellent section that touched on building up trust with students or even a class when it comes to providing feedback and criticism. Having a bank of trust makes it easier to give feedback as well as to receive it. Here’s a link to the audio portion and a copy of the relevant text.
Listening to the students talk about feeling unsure and vulnerable when they first encountered open educational practices made me think about my own learning. As a mid-career academic who has changed jobs and even disciplines, I am a confident learner. I have received lots of praise and other kinds of positive reinforcement for my ability to learn new things. If you have read previous posts on my blog, you might know that I am really interested in developments in the IndieWeb movement and am trying to write about some of my experiences with using IndieWeb tools to build my own web site. I’ve been building my own sites for years and so I have a lot of confidence in my ability there as well. Working on the IndieWeb stuff has been challenging because there’s a lot of new language and new concepts as well as some aspects of web development that I have not engaged with before. I often feel vulnerable when I write my posts about the IndieWeb because my understanding of how everything works is emerging. In other words, I don’t get it all yet but I’m still writing publicly about my work.
Feeling courageous? Click the [repost] symbol next to this post. #
Which movies from your youth would be impossible to make today due to political correctness?
You can see that we are focused lately on the social stuff. Why? Because it was always there in front of you, but there were many obstacles that made it not very usable or friendly. Comment has improved, but one thing with them remained. Many people don’t know that comments in InoReader are actually public …
I remotely attended the Displaying Responses session of IndieWebCamp Berlin 2018. It was very interesting and they made some good progress thinking though how to deal with how and when to display responses received to posts on your website. They came to the conclusion that there are four groups of people that you want to treat their responses differently: Accepted / Immediate Connections 2nd level connections Everyone Mute or Blocked Accepted / Immediate Connections These are essentially your friends on Facebook or your follow list on Twitter. These are people that you have chosen to connect with in some way and this logical conclusions can be drawn around the level of interactions you're willing to have. My plan is to display these responses completely (name, photo and content of response). This list will be generated for me by adding anyone I follow, as well as anyone I have sent a reply to. This will NOT add people to whom I have liked, emoji reacted, quoted, or bookmarked. Those are lower level responses that do not indicate a deeper level of a desire to connect with that person. 2nd Level Connections These are "friends of friends". You can assume they won't do anything TOO bad, but you might not want them posting all over your site. There is a deeper level of trust here because of mutual connection but still some care should be taken. This can be determined through different ways. One way that has been brainstormed in the IndieWeb is Vouch. I don't currently track 2nd level connections but I liked how Tantek thought this through, so my plan is for replies to display their photo and name as "other people that have responded to this post", but not display the content of their reply. I also think if they send a like, emoji reaction or quote, I'll display it just like I would an Immediate Connection. Everyone This is the World Wide Web, and anyone could send anything to my website via webmention. So this is a category you likely want to moderate. My initial thought is I will accept likes, quotes and emoji reactions from them but I won't list attribution of who did it while moderated, just the reaction itself. For replies I am considering potentially listing the url of the author of the post under "other people who have replied" but no name, photo or content while moderated. Mute or Blocked These are people who you do not trust for whatever reasons have happened for you. You don't want to associate with them in any way. Responses are not displayed from these people and they are not listed in the moderation queue. Some thoughts on moderation This means I'll need a moderation queue. Anything from a 2nd level connection or from the Everyone group will enter the moderation queue. Responses from 2nd level connections should appear higher in the queue than responses from the Everyone group. From there I can choose to: approve a response (display it like an immediate connection) approve response and accept author (makes this author an immediate connection so they aren't moderated anymore) ignore response (this leaves the response as is, it leaves the queue but doesn't display additional details) remove response (this removes the response from my storage) remove response and block author (this both removes the response from my storage and makes sure I don't receive responses from them in the future) All in all, it was a great session that I really enjoyed and I'm looking forward to actually working on implementing some of these features into my site.