FAQ - Revision history

Erkan Yilmaz: /* I have not received a reply from the Echo Server */ new echo server

2017-06-11T08:32:09Z

I have not received a reply from the Echo Server: new echo server

2016-06-16T12:39:20Z

sockshostname now resolves when checking for incoming connections

2016-06-08T12:52:19Z

How do I setup Bitmessage as a hidden service on Tor

2016-06-08T10:19:47Z

Minor clarification

2016-06-08T10:13:23Z

Tor hidden service

2015-08-09T11:59:02Z

2015-01-23T05:42:35Z

I2P-Bote hides receiver according to it's user guide: "address of the recipient will only be known to sender and recipient(s)."

2015-01-23T04:24:56Z

Bitmessage has an Android version (Bitseal) in beta which requires a server to communicate with the Bitmessage network.

2015-01-23T04:13:52Z

Added note that messages on I2P-Bote network live up to 100 days.

2015-01-23T04:12:05Z

I2P-Bot now has an Android port https://geti2p.net/en/blog/post/2014/08/23/Android-test-release-on-Google-Play-in-Norway

@@ Line 466: / Line 466: @@
 *On average it should take 8 minutes from the time you click the send button to the time you receive a response.
 *Be sure to allow extra time in the event that the server is under heavy traffic (Example: An article about Bitmessage was posted on a popular website).
-*You can always send a message to another echo server. Here are two echo addresses:
+*You can always send a message to another echo server. Here are echo addresses:
-** BM-orkCbppXWSqPpAxnz6jnfTZ2djb5pJKDb
+** BM-2cWoG7fKafmVbfeMh8U2mRgix6eTuGSQCK
-** BM-omXeTjutKWmYgQJjmoZjAG3u3NmaLEdZK
+** these seem to not work anymore: BM-orkCbppXWSqPpAxnz6jnfTZ2djb5pJKDb / BM-omXeTjutKWmYgQJjmoZjAG3u3NmaLEdZK
 *You may subscribe to the [[Timeservice Broadcast]] to receive network heartbeats.
 *You can send messages to a [[Mailing List]] in case it still does not works

@@ Line 80: / Line 80: @@
 <code>sockslisten = true</code>
 |}
 ==Usage==

@@ Line 52: / Line 52: @@
 <code>onionport = 8444</code>
 || <code>socksproxytype = none</code>
 <code>onionhostname = abcdefgh.onion</code>
@@ Line 69: / Line 71: @@
 <code>onionport = 8444</code>
 || <code>socksproxytype = SOCKS5</code>
 <code>onionhostname = abcdefgh.onion</code>

@@ Line 37: / Line 37: @@
 ===How do I setup Bitmessage as a hidden service on Tor===
-Bitmessage can accept incoming connections as a Tor hidden service. This feature is supported since https://github.com/Bitmessage/PyBitmessage/commit/1a40c29d221f036e82a87444ace331afbb8e80c6. In order to use it you have to manually add a new hidden service in your tor configuration. The following table explains the settings combination (IP addresses and port number are just examples, adjust them if you have a different setup):
+Bitmessage can accept incoming connections as a Tor hidden service. This feature is supported since https://github.com/Bitmessage/PyBitmessage/commit/1a40c29d221f036e82a87444ace331afbb8e80c6. In order to use it you have to manually add a new hidden service in your tor configuration. The following table explains the settings combination for Bitmessage's keys.dat. IP addresses and port number are just examples, adjust them if you have a different setup:
 {| class="wikitable"
@@ Line 76: / Line 76: @@
 <code>sockslisten = true</code>
 |}
 ==Usage==

@@ Line 34: / Line 34: @@
 *Select ok.
 *Restart Bitmessage.
 ==Usage==

@@ Line 108: / Line 108: @@
 | {{Yes|Beta, requires server}}
 | Application
-| {{Yes|180 MB}}
+| {{Yes|220KB}}
 | {{Yes}}
 | {{Yes}}
@@ Line 114: / Line 114: @@
 | {{No}}
 | {{No}}
-| {{Partial|Up to 2 days}}
+| {{Yes|Up to 28 days}}
 |-
 ! Standard Email
@@ Line 215: / Line 215: @@
 | {{Yes}}
 | {{Yes}}
-| {{Partial|Not yet implemented}}
+| {{Yes}}
 | {{Partial|Queued}}
 |-
@@ Line 403: / Line 403: @@
 |  {{No}}
 |  {{No}}
-|  {{Partial|Up to 30 days}}
+|  {{Yes|Up to 30 days}}
 |}