Skip to content

Instantly share code, notes, and snippets.

@karlcow
Last active August 25, 2022 17:44
Show Gist options
  • Save karlcow/4691602 to your computer and use it in GitHub Desktop.
Save karlcow/4691602 to your computer and use it in GitHub Desktop.
Decentralized Commenting Systems or more exactly how do we interconnect blog posts.

Threading discussions in between blogs

A recurrent discussion is happening in the French Web community about comments and blogs and how to continue to publish on your own blogs and still aggregates the discussion into a thread in your own blog. So basically how the discussions can be decentralized and distributed with a notion of multiple copies.

Hashtag

Let's use #sudwebcmt for the hashtag. It will help avoid putting plenty of people in cc in the discussions.

References

Before putting forward any protocols or technical solutions, I want to be sure we are having a common understanding of the problem space and what we want to achieve at SudWeb 2013.

Editing this document

You are welcome to edit this document. There are revision history, so we do not lose anything, we just evolve it.

Comments or blog posts

There are issues to solve on what we want.

  • Do we want a thread of the discussions (aka following the inter-links in between blog posts)?
  • Do we want a copy of these articles locally in each original blog posts?
  • If yes where the aggregation starts and stops?
  • Do we want a system where a comment can be made outside of any blogging systems?
  • Do we want to have this comment being distributed on multiple blogs and in this case where and how?

Some issues around network social interactions.

There is a clear distinction between push and pull in social interactions.

  • Push systems (notifications, traditional comments, emails) are usually not working in an open distributed network, because they generate spam. The reason is that the flow of information in a push system is dependent on the power to generate that flow at a low cost. To avoid the spam, receivers of the pushed information have to put in place strategies a priori (login, authorization, captcha) or a posteriori (bayesan filtering, heuristic, manual removal).
  • Pull systems (RSS, click on a link, etc) are putting the burden on the information receivers. Their main issue is that it takes time and requires regular polling (bandwidth waste). Another issue is that it makes difficult to discover related discussions. We do not know what is out there. The benefit is that it completely avoid the spam. You get only what you want to get, but you do not get everything you might want to get.

Maybe a place to explore is the notion of "community of trust". We might want to give up entirely on the completely open network for discussions and put in place a system based on network of trust. Some communities have explored this such as Advogato. We might want to explore ideas.

@karlcow
Copy link
Author

karlcow commented Feb 1, 2013

See also the proposal

@naholyr
Copy link

naholyr commented Feb 3, 2013

Not sure my proposal will work with this decentralized idea, we need far more than my local system ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment