Decentralized networks - Revision history

Guaka at 22:42, 10 December 2018

2018-12-10T22:42:30Z

← Older revision		Revision as of 22:42, 10 December 2018
Line 34:		Line 34:

	=== Services for Moderation and Conflict Handling ===		=== Services for Moderation and Conflict Handling ===
	Similar to the Couchsurfing MDST, there could be services that can filter out inappropriate ~~references~~, or decide which profiles are relevant to you or not. Sounds quite abstract and unclear, needs to be fleshed out. Somewhere else I used the term "reference realms".		Similar to the Couchsurfing MDST, there could be services that can filter out inappropriate [[reference]]s, or decide which profiles are relevant to you or not. Sounds quite abstract and unclear, needs to be fleshed out. Somewhere else I used the term "reference realms".

	=== Aggregation Services ===		=== Aggregation Services ===

Lemon-head: /* Examples */

2009-11-01T16:49:57Z

Examples

← Older revision		Revision as of 16:49, 1 November 2009
Line 91:		Line 91:
	* Noserub		* Noserub
	*: Q: How does Noserub solve the above "problems" ?		*: Q: How does Noserub solve the above "problems" ?
			* OpenSocial? Shindig?

	[[Category:P2P Hospitality]]		[[Category:P2P Hospitality]]

Lemon-head: /* Services for Moderation and Conflict Handling */

2009-10-24T20:17:07Z

Services for Moderation and Conflict Handling

← Older revision		Revision as of 20:17, 24 October 2009
Line 35:		Line 35:
	=== Services for Moderation and Conflict Handling ===		=== Services for Moderation and Conflict Handling ===
	Similar to the Couchsurfing MDST, there could be services that can filter out inappropriate references, or decide which profiles are relevant to you or not. Sounds quite abstract and unclear, needs to be fleshed out. Somewhere else I used the term "reference realms".		Similar to the Couchsurfing MDST, there could be services that can filter out inappropriate references, or decide which profiles are relevant to you or not. Sounds quite abstract and unclear, needs to be fleshed out. Somewhere else I used the term "reference realms".


	=== Aggregation Services ===		=== Aggregation Services ===

Lemon-head: /* How this can work */

2009-10-24T20:16:56Z

How this can work

← Older revision		Revision as of 20:16, 24 October 2009
Line 13:		Line 13:


	== How ~~this~~ can work ==		== Pieces of the Puzzle ==

			=== Local computers with normal browsers ===
			You can find them at home, at friends' places, at school, in Internet Cafés. They can be used for surfing the web, but we can't expect any special software on these machines.

			=== Local computers with special P2P software ===

			=== (Small) social networks with user profiles ===
			This is where you would upload your pictures, write about your hobbies, etc. You could even use different sites for that: Have your photos on flickr, but your profile information somewhere else.

			One of these networks can store your friend links, another your messages..

			=== Meeting places (groups, forums) ===
			If user profiles are distributed on different networks, we still want groups and forums that connect people from different networks. The most simple example is: A and B each have a blog, that are technically independent of each other. A leaves a comment on blog B, with a link pointing to blog A.

			The problem is that B can't be sure if A is really A, or if it C who claims to be A to spread all kinds of libel and nonsense. So, the advanced version would provide a possibility for A to prove that it is truly A (the person with blog A), and not someone else.

			=== Dedicated systems for friend links, messages, different kinds of interaction ===
			Honestly, I have no idea how this would look like :)

			=== Services for Moderation and Conflict Handling ===
			Similar to the Couchsurfing MDST, there could be services that can filter out inappropriate references, or decide which profiles are relevant to you or not. Sounds quite abstract and unclear, needs to be fleshed out. Somewhere else I used the term "reference realms".


			=== Aggregation Services ===
			This can be bigger players (google, whatever) that scan user profiles on different sites and offer this information for searching or to deliver pages with information mashed up from different sources.

			We can want this or not, we can fight these aggregation services or use them. In any case, they are part of the picture, and can't be ignored.

			== How it can work ==
	A lot can be said about decentralized networks, but in the context of [[hospitality exchange]] the most important is user profiles, (location-based) member search, messages between members, and [[trust]] / [[friend]] connections. All of this has to work across different networks, otherwise it won't be really useful.		A lot can be said about decentralized networks, but in the context of [[hospitality exchange]] the most important is user profiles, (location-based) member search, messages between members, and [[trust]] / [[friend]] connections. All of this has to work across different networks, otherwise it won't be really useful.

Matrixpoint at 11:44, 17 October 2009

2009-10-17T11:44:41Z

← Older revision		Revision as of 11:44, 17 October 2009
Line 64:		Line 64:
	*: Q: How does Noserub solve the above "problems" ?		*: Q: How does Noserub solve the above "problems" ?

	[[Category:~~Philosophy~~]]		[[Category:P2P Hospitality]]

Flapic at 10:20, 16 October 2009

2009-10-16T10:20:34Z

← Older revision		Revision as of 10:20, 16 October 2009
Line 62:		Line 62:
	* Crash at Mine (?)		* Crash at Mine (?)
	* Noserub		* Noserub
	*: Q: How does ~~noserup~~ solve the above "problems" ?		*: Q: How does Noserub solve the above "problems" ?

	[[Category:Philosophy]]		[[Category:Philosophy]]

Guaka at 21:38, 15 October 2009

2009-10-15T21:38:44Z

← Older revision		Revision as of 21:38, 15 October 2009
Line 14:		Line 14:

	== How this can work ==		== How this can work ==
	A lot can be said about decentralized networks, but in the context of hospitality exchange the most important is user profiles, (location-based) member search, messages between members, and trust / friend connections. All of this has to work across different networks, otherwise it won't be really useful.		A lot can be said about decentralized networks, but in the context of [[hospitality exchange]] the most important is user profiles, (location-based) member search, messages between members, and [[trust]] / [[friend]] connections. All of this has to work across different networks, otherwise it won't be really useful.

	The biggest challenges here are privacy an proof of identity: How can one restrict the visibility of information that is shared across different networks? And how can I prove that I am the owner of profile A on network X, when interacting with members form network Y?		The biggest challenges here are [[privacy]] and proof of [[identity]]: How can one restrict the visibility of information that is shared across different networks? And how can I prove that I am the owner of profile A on network X, when interacting with members form network Y?

	=== User accounts / profiles ===		=== User accounts / profiles ===

Lemon-head: /* How this can work */

2009-10-15T17:45:33Z

How this can work

← Older revision		Revision as of 17:45, 15 October 2009
Line 14:		Line 14:

	== How this can work ==		== How this can work ==
			A lot can be said about decentralized networks, but in the context of hospitality exchange the most important is user profiles, (location-based) member search, messages between members, and trust / friend connections. All of this has to work across different networks, otherwise it won't be really useful.

	=== User accounts ===		The biggest challenges here are privacy an proof of identity: How can one restrict the visibility of information that is shared across different networks? And how can I prove that I am the owner of profile A on network X, when interacting with members form network Y?

			=== User accounts / profiles ===
	The idea would mean that there is not one big network where you create a user account, but instead you would choose one or more networks where you want to create an account and have the information you define stored in the database.		The idea would mean that there is not one big network where you create a user account, but instead you would choose one or more networks where you want to create an account and have the information you define stored in the database.

Line 54:		Line 57:
	=== [[Trust]] links between networks ===		=== [[Trust]] links between networks ===
	Just like there can be a trust network of people, there can also be a trust network of networks..		Just like there can be a trust network of people, there can also be a trust network of networks..


	== Examples ==		== Examples ==

Lemon-head: /* Trust/Friend links between members */

2009-10-15T17:41:03Z

Trust/Friend links between members

← Older revision		Revision as of 17:41, 15 October 2009
Line 47:		Line 47:
	Just like the references or friend links in couchsurfing, you could create a trust link from profile A in network X to profile B in network Y.		Just like the references or friend links in couchsurfing, you could create a trust link from profile A in network X to profile B in network Y.

	This can only work if there is a way to prove that your friend link does in fact come from profile A in network X, and not from somewhere else. This is ~~similar to~~ the messages.		This can only work if there is a way to prove that your friend link does in fact come from profile A in network X, and not from somewhere else. This is the same problem as with messages.

	=== Profile data visibility constraints ===		=== Profile data visibility constraints ===

Lemon-head: /* Messages from one user to another */

2009-10-15T17:40:34Z

Messages from one user to another

← Older revision		Revision as of 17:40, 15 October 2009
Line 42:		Line 42:

	Solutions:		Solutions:
			* OpenID? Does that allow to identify you as a member of a different network?

	=== Trust/Friend links between members ===		=== Trust/Friend links between members ===