Difference between revisions of "Decentralized Mailing List"

From Bitmessage Wiki
Jump to navigation Jump to search
m (AyrA moved page Subscriptions to Decentralized Mailing List: This page has nothing to with SUbscriptions in general.)
(Made this a real wiki entry)
Line 1: Line 1:
* De-centralized General Broadcast Chan
+
== Issues with Mailing Lists ==
 +
Even if Bitmessage is a decentralized [[p2p]] network, mailing lists require the client who operates the list to be online, creating a [http://en.wikipedia.org/wiki/Single_point_of_failure Single Point of Failure]. Decentralized lists circumvent this issue with everyone having the private keys to the Address, on the cost of signing. In a centralized list, it is known, who sent a mesage, in a decentralized, this is only possible with additional measurements (Hash tagging, PGP). Decentralized lists however cannot be clogged up with large messages because [[POW]] is only done by the sending client.
  
We now have an alternative to the centralized "General" Chan.  
+
== Creation ==
 +
Creating a decentralized mailing list required the user to generate a key, he may either generate a random address and share the Address block from keys.dat or create a deterministic address and share the settings he made with other users.
 +
A client then subscribes to his own address.
  
It is the "general" broadcast address and has no central client that has to re-work the PoW. Instead of sending a message to an address and it broadcasting it out to all subscribers (Which is great and serves a purpose) you broadcast from an address and everyone subscribed will get a copy.
+
== Usage ==
 +
Decentralized lists are reached by broadcasting a message from the decentralized address itself, having the disadvantage of not getting own messages in the inbox, only replies to it, since clients ignore messages they sent themselves.
  
To join/participate please do the following
+
== Example Address ==
 +
It is created by regenerating a deterministic address with the passphrase "general" (without quotes). Address Version is 3 and sthe stream Number is 1. The field "Do extra work" must not be checked, resulting in the Address: BM-2DAV89w336ovy6BUJnfVRD5B9qipFbRgmr. This address has to be added to the subscription list and is now ready to use. Messages are broadcasted from the address, not sent to it. When replying to a message, the reply has to be made as a broadcast itself.
  
File > Regenerate Deterministic Address
+
The [[Address Block]] should look like this:
  
Passphrase: general
+
[BM-2DAV89w336ovy6BUJnfVRD5B9qipFbRgmr]
  
Number of addresses to make:
+
label = general
  
Address version number: 3
+
enabled = false
  
Stream Number: 1
+
decoy = false
  
Spend several minutes of extra computing time... : No/Unchecked
+
privsigningkey = 5Jnbdwc4u4DG9ipJxYLznXSvemkRFueQJNHujAQamtDDoX3N1eQ
  
It should generate this address:BM-2DAV89w336ovy6BUJnfVRD5B9qipFbRgmr
+
privencryptionkey = 5JrDcFtQDv5ydcHRW6dfGUEvThoxCCLNEUaxQfy8LXXgTJzVAcq
  
Now subscribe to the address and you are set  Remember, when you reply or send a new message you must check "Broadcast to everyone who is subscribed to your address".
+
== Address List ==
 
+
A list of addresses can be found at [https://bitmessage.org/forum/index.php/topic,1420.0.html the forum].
* Other Chans
 
 
 
Dig through this forum post to find more:
 
 
 
https://bitmessage.org/forum/index.php/topic,1420.0.html
 

Revision as of 07:35, 6 June 2013

Issues with Mailing Lists

Even if Bitmessage is a decentralized p2p network, mailing lists require the client who operates the list to be online, creating a Single Point of Failure. Decentralized lists circumvent this issue with everyone having the private keys to the Address, on the cost of signing. In a centralized list, it is known, who sent a mesage, in a decentralized, this is only possible with additional measurements (Hash tagging, PGP). Decentralized lists however cannot be clogged up with large messages because POW is only done by the sending client.

Creation

Creating a decentralized mailing list required the user to generate a key, he may either generate a random address and share the Address block from keys.dat or create a deterministic address and share the settings he made with other users. A client then subscribes to his own address.

Usage

Decentralized lists are reached by broadcasting a message from the decentralized address itself, having the disadvantage of not getting own messages in the inbox, only replies to it, since clients ignore messages they sent themselves.

Example Address

It is created by regenerating a deterministic address with the passphrase "general" (without quotes). Address Version is 3 and sthe stream Number is 1. The field "Do extra work" must not be checked, resulting in the Address: BM-2DAV89w336ovy6BUJnfVRD5B9qipFbRgmr. This address has to be added to the subscription list and is now ready to use. Messages are broadcasted from the address, not sent to it. When replying to a message, the reply has to be made as a broadcast itself.

The Address Block should look like this:

[BM-2DAV89w336ovy6BUJnfVRD5B9qipFbRgmr]

label = general

enabled = false

decoy = false

privsigningkey = 5Jnbdwc4u4DG9ipJxYLznXSvemkRFueQJNHujAQamtDDoX3N1eQ

privencryptionkey = 5JrDcFtQDv5ydcHRW6dfGUEvThoxCCLNEUaxQfy8LXXgTJzVAcq

Address List

A list of addresses can be found at the forum.