Compound Structures: Difference between revisions
Adamcolton (talk | contribs) No edit summary |
Adamcolton (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
== Braid == | == Braid == | ||
Two users that wish to communicate but remain anonymous can create a braid. Users can establish communication via a signal. | Two users that wish to communicate but remain anonymous can create a braid. Users can establish communication via a signal. | ||
| Line 8: | Line 6: | ||
There will be a defined protocol for using the channels. Something that uses the channels mostly evenly, but in a way that there is always enough redundancy left over to patch cut lines. If Bob is not following protocol, Alice can cut the communication because he may be trying to locate her. | There will be a defined protocol for using the channels. Something that uses the channels mostly evenly, but in a way that there is always enough redundancy left over to patch cut lines. If Bob is not following protocol, Alice can cut the communication because he may be trying to locate her. | ||
== | == Swarm Server == | ||
A group of peers can form a virtual server. A | A group of peers can form a swarm server. | ||
Every peer within a virtual server knows every other peer and has a trust rating. With [[TrustGraph]] this allows us to know the trustworthiness of every other peer. | |||
A Swarm allows for broadcasting. I haven't worked out the best method for this, but a message will be delivered to every node in the network at least once, preferably with as little overhead as possible. A swarm can limit the size of broadcast messages. They can limit if a message has to come from a member, and they can ration messages is they do need to come from a member. | |||
A swarm also maintains a DHT. Resources can be placed in the DHT, depending on configuration, put commands may be limited to trusted members. | |||
=== Anonymous Swarm Server === | |||
Each node creates an ID just for use with the swarm. All communication is done through [[Beeds]]. | |||
[[Category:Waxnet]] | [[Category:Waxnet]] | ||
Latest revision as of 17:08, 2 March 2016
Braid
Two users that wish to communicate but remain anonymous can create a braid. Users can establish communication via a signal.
Alice sees that Bob has posted a signal and would like to open communication. She creates a few (say, 6) return routes, each with a limited number of uses (say 10). Bob can now send up to 60 messages to Alice. Bob uses one of these to send Alice a similar package. Alice knows the 18 nodes she used in her routes. When one of those nodes goes offline, she can send Bob a new route to replace it.
There will be a defined protocol for using the channels. Something that uses the channels mostly evenly, but in a way that there is always enough redundancy left over to patch cut lines. If Bob is not following protocol, Alice can cut the communication because he may be trying to locate her.
Swarm Server
A group of peers can form a swarm server.
Every peer within a virtual server knows every other peer and has a trust rating. With TrustGraph this allows us to know the trustworthiness of every other peer.
A Swarm allows for broadcasting. I haven't worked out the best method for this, but a message will be delivered to every node in the network at least once, preferably with as little overhead as possible. A swarm can limit the size of broadcast messages. They can limit if a message has to come from a member, and they can ration messages is they do need to come from a member.
A swarm also maintains a DHT. Resources can be placed in the DHT, depending on configuration, put commands may be limited to trusted members.
Anonymous Swarm Server
Each node creates an ID just for use with the swarm. All communication is done through Beeds.