Dist.ribut.us lite - Revision history

Adamcolton at 17:06, 9 August 2018

2018-08-09T17:06:25Z

← Older revision		Revision as of 17:06, 9 August 2018
Line 7:		Line 7:

	=== Gateway ===		=== Gateway ===
	A gateway is a service that talks to many servers to make sure the system is honest. Gateway software should be light weight and simple enough that a moderately sophisticated user can setup their own gateway.		A gateway is a service that talks to many servers to make sure the system is honest. Gateway software should be light weight and simple enough that a moderately sophisticated user can setup their own gateway. It handles the eigentrust calculation (or maybe just validates it) and handles the web-of-trust issues.

	=== Server ===		=== Server ===
Line 13:		Line 13:

	=== Storage ===		=== Storage ===
	Data is a simple Key/Value store ~~backed by Bolt~~. Though it's a little more than that because the key needs to have enough data to locate a server, a database and a bucket.		Data is a simple Key/Value store. Though it's a little more than that because the key needs to have enough data to locate a server, a database and a bucket.

			I need a way to swap out the backing medium. In some cases Bolt will be easiest, in others, blob services like S3 will be better.

	==== Static ====		==== Static ====
Line 31:		Line 33:
	=== Users ===		=== Users ===
	A user is a signing key at it's heart. Finding a usability pattern for this is going to be tricky.		A user is a signing key at it's heart. Finding a usability pattern for this is going to be tricky.

			=== Communication Security ===
			TLS isn't going to fully cover this because many users will be running small personal servers off non-fixed IP addresses.

	== Community ==		== Community ==
Line 47:		Line 52:

	Better would be for users to pay for access to federated servers. This is a divergence from the norm, but perhaps with mom-and-pop servers where the users actually know the administrators, this could be established.		Better would be for users to pay for access to federated servers. This is a divergence from the norm, but perhaps with mom-and-pop servers where the users actually know the administrators, this could be established.

			=== Personal Setup ===

			==== RasPi ====
			I should get a version built that can be setup on a RasPi easily. A 1TB external drive is cheap.

			==== AWS ====
			I should offer an image

	== Target Applications ==		== Target Applications ==
Line 68:		Line 81:
	* Direct Messaging		* Direct Messaging
	* Media uploads		* Media uploads

			=== Media Player ===

			Designed for personal use. User puts their media files on something like a RasPi drive and they can stream the media. A per-user record

	[[Category:dist.ribut.us]]		[[Category:dist.ribut.us]]

Adamcolton at 14:50, 9 August 2018

2018-08-09T14:50:08Z

← Older revision		Revision as of 14:50, 9 August 2018
Line 1:		Line 1:
	Rather than full p2p, a system for distributing trust between federated servers		Rather than full p2p, a system for distributing trust between federated servers. It fails many of the goals of the full dist.ribut.us design, most notably meta-data protection via onion routing. But it is much easier to build and could provide the necessary foundation to build the full system.

	== Federation Problem ==		== Federation Problem ==

Adamcolton at 14:47, 9 August 2018

2018-08-09T14:47:25Z

← Older revision		Revision as of 14:47, 9 August 2018
Line 56:		Line 56:

	It may make sense to write the block in 2 parts, a header and the data. The header contains the 'next' link, time span and a bloom filter for words in the text.		It may make sense to write the block in 2 parts, a header and the data. The header contains the 'next' link, time span and a bloom filter for words in the text.

			Chat can also do a direct file send over webRTC.

	=== File Sync ===		=== File Sync ===

Adamcolton at 14:45, 9 August 2018

2018-08-09T14:45:28Z

← Older revision		Revision as of 14:45, 9 August 2018
Line 19:		Line 19:

	==== Permissions ====		==== Permissions ====
	~~The~~ key ~~is some sort of guid~~. ~~The record has Read/Write/Admin permissions~~ with a ~~list of signing keys for each permission~~.		Permissions are placed on a bucket. UserIDs are written to the bucket with a permissions level. Data is written key/val. Both are prefixed with a header byte.

	=== Services and Applications ===		=== Services and Applications ===
Line 58:		Line 58:

	=== File Sync ===		=== File Sync ===
	Allow users to sync their files between devices. This is a bit more complex and requires a client binary.		Allow users to sync their files between devices. This is a bit more complex and requires the client binary.

			=== Speakeasy ===
			A basic social network.

			* Posts
			* Direct Messaging
			* Media uploads

	[[Category:dist.ribut.us]]		[[Category:dist.ribut.us]]

Adamcolton at 14:38, 9 August 2018

2018-08-09T14:38:50Z

← Older revision		Revision as of 14:38, 9 August 2018
Line 53:		Line 53:
	This is the 'hello world' of distributed applications. Establish a chat log and allow users to append to it based on cryptographic permissions.		This is the 'hello world' of distributed applications. Establish a chat log and allow users to append to it based on cryptographic permissions.

	Ha! this is actually a good use for a sort-of-blockchain. The head of a chat		Ha! this is actually a good use for a sort-of-blockchain. The head of a chat contains the most recent additions and a block reference. When the chat gets too long, the history is written to a static block.

			It may make sense to write the block in 2 parts, a header and the data. The header contains the 'next' link, time span and a bloom filter for words in the text.

	=== File Sync ===		=== File Sync ===

Adamcolton at 14:35, 9 August 2018

2018-08-09T14:35:17Z

@@ Line 14: / Line 14: @@
 === Storage ===
 Data is a simple Key/Value store backed by Bolt. Though it's a little more than that because the key needs to have enough data to locate a server, a database and a bucket.
 === Services and Applications ===
 A service run on a server, an application runs on a client. As much logic should be pushed to the application level as possible. Services and applications must be open source.
 == Community ==
@@ Line 33: / Line 47: @@
 Better would be for users to pay for access to federated servers. This is a divergence from the norm, but perhaps with mom-and-pop servers where the users actually know the administrators, this could be established.
 [[Category:dist.ribut.us]]

Adamcolton at 14:22, 9 August 2018

2018-08-09T14:22:10Z

@@ Line 14: / Line 14: @@
 === Storage ===
 Data is a simple Key/Value store backed by Bolt. Though it's a little more than that because the key needs to have enough data to locate a server, a database and a bucket.
 [[Category:dist.ribut.us]]

Adamcolton at 13:59, 9 August 2018

2018-08-09T13:59:32Z

← Older revision		Revision as of 13:59, 9 August 2018
Line 10:		Line 10:

	=== Server ===		=== Server ===
	The servers hold data and facilitate connections. Most communication is user-to-user over WebRTC.		The servers hold data and facilitate connections. Most communication is user-to-user over WebRTC.

			=== Storage ===
			Data is a simple Key/Value store backed by Bolt. Though it's a little more than that because the key needs to have enough data to locate a server, a database and a bucket.

	[[Category:dist.ribut.us]]		[[Category:dist.ribut.us]]

Adamcolton: /* Federation Problem */

2018-08-09T13:57:48Z

Federation Problem

← Older revision		Revision as of 13:57, 9 August 2018
Line 2:		Line 2:

	== Federation Problem ==		== Federation Problem ==
			In a federated server system, individual servers can gain power over the whole system. To prevent this, the rules need to be enforced and users should not be associated with an individual server.

			== Design ==

			=== Gateway ===
			A gateway is a service that talks to many servers to make sure the system is honest. Gateway software should be light weight and simple enough that a moderately sophisticated user can setup their own gateway.

			=== Server ===
			The servers hold data and facilitate connections. Most communication is user-to-user over WebRTC.

	[[Category:dist.ribut.us]]		[[Category:dist.ribut.us]]

Adamcolton at 13:47, 9 August 2018

2018-08-09T13:47:37Z

← Older revision		Revision as of 13:47, 9 August 2018
Line 1:		Line 1:
			Rather than full p2p, a system for distributing trust between federated servers

			== Federation Problem ==


	[[Category:dist.ribut.us]]		[[Category:dist.ribut.us]]