Like many I joined WikiTribune, the new social network for news. The service quickly overtook Aacademia.edu as the primary spam engine of my inbox.
Got me thinking that Nuzzel, an app that algorithimically surfaces stuff to read by what your followers share on Twitter, already adds a layer of trust. I don't know the 1,000s of people I follow but I know I felt their work deserved the h/t of a follow.
I have also used Twitter lists, not my own who has time for that, but those made by other people. People I trust.
Still both of these services rely on a third party silo that monetizes and gets value from my trusted network. So this got me thinking about an #IndieWeb Version.
Curating Read Posts
Chris Aldrich recently explored the possibilities and demonstrated how folks can follow interesting things he reads using RSS. Not so much a community effort.
For #clmooc, a community that grew out of a MOOC run by the National Writing Project on Connected Learning, we utilize a web ring. I then made a Public RSS feed using inoreader. Most people in the community blog enough to tag their posts which I use for specific feeds or they have blogs dedicated to just the clmooc community. Have mroe community but still requires one to visit the sie and subscribe to the feeds.
WikiTribune set out to create a collective community of trusted news. From an #IndieWeb perspective trust begins with your own domain. I fully believe people will not spray paint their own front door with bullshit the way we do on social media.
I also believe the use of web rings as an indircator of trust and membership can also provide indicators of credibility.
I spend a lot of time looking at metadata, trust, claims, and evidence....but I always return to people. Trust begins and ends with people.
How Could an IndieWeb "What to Read" Tool Work?
Chris's post and my recent experience with WikiTribune got me thinking about an IndieWeb version. The presmise would have to be publishing what you read or is worthwile reading from your own site. Some folks may use a bookmark, like, or even experimental post types such as a "read" post.
You would then opt-in to "what to read" using your domain. Then you would be asked to enter the url to your feed. Microcast.club work like this already.
All of your posts in the feed would be parsed and then added to a firehose chronological feed. There would also be one generated using th frequency of links and webmentions. So if an article gets shared by n+1 people it gets a bump, if a post getsd a webmention it gets a bump. The feed could then refresh at specific times of the days.
We could also use tags and p-categories to help with topic discovery.
I guess there could be email notifications. I would be fine without them as I would subscribe to "What to Read" in my social reader.
Featured Image: READ flickr photo by adamsaul shared under a Creative Commons (BY-NC-ND) license ;
Also on IndieNews