Difference between revisions of "Timeservice Broadcast"

From Bitmessage Wiki
Jump to navigation Jump to search
Line 20: Line 20:
  
 
== Comparison to echo servers ==
 
== Comparison to echo servers ==
An [[echo service]] will reply to your message. Like a mailing list, an echo service has to compute proof of work for the messages it receives. If it is under load, such as a large influx in echo service users, your reply may be further delayed. Broadcasts can support unlimited users without causing any additional load on the network, but it does not allow the user to check if he can send messages to the network.
+
An [[echo service]] will reply to your message. Like a mailing list, an [[echo service]] has to compute proof of work for the messages it receives. If it is under load, such as a large influx in [[echo service]] users, your reply may be further delayed. Broadcasts can support unlimited users without causing any additional load on the network, but it does not allow the user to check if he can send messages to the network.
  
 
== Current Message ==
 
== Current Message ==

Revision as of 12:49, 11 July 2013

The Timeservice Broadcast sends network heartbeats in regular intervals, currently every 10 minutes.

Usage

Subscribtion to the Address BM-BcbRqcFFSQUUmXFKsPJgVQPSiFA3Xash is required. After subscribing, the client will receive a message every 10 minutes if he is connected to the core network. The subscription can be disabled or deleted any time to stop the messages from clogging up the inbox.

This is not an echo service, it will not automatically reply to messages sent to it, however, the admin sometimes does manually reply.

Usage scenarios

The time service can be used for multiple purposes

Randomnes

The time service puts some randomnes to the network and ensures that it has always something to do.

Connectivity check.

If users subscribe to the time service they can verify, they are connected to the core network, in case they think something in their connection is wrong.

Actual time telling.

The time service tells the accurate time (it is maximum 2 minutes behind the actual time if you receive the message). In case users want to hide even the time zone they are in, they can always add the note, that the time and date they use in messages are timeservice based, this requires setting the computer clock to UTC.

Impact

The service has no impact on the network, it causes 144 messages every 24 hours.

Comparison to echo servers

An echo service will reply to your message. Like a mailing list, an echo service has to compute proof of work for the messages it receives. If it is under load, such as a large influx in echo service users, your reply may be further delayed. Broadcasts can support unlimited users without causing any additional load on the network, but it does not allow the user to check if he can send messages to the network.

Current Message

The current message is the UTC time it was generated (The entry below is an actual message):

Bitmessage Time Service
Network alive @ 11.07.2013 11:57:40 UTC
This represents the Time when the Message was generated, not when the processing finished.
Do not set this time as your computer time.

bitmessage.ch - Free Bitmessage <-> E-Mail Gateway
Bitmessage E-Mail Application - https://bitmessage.org/forum/index.php/topic,1587.0.html
24x7 Mailing List -  BM-GuRLKDhQA5hAhE6PDQpkcvbtt1AuXAdQ



========================================
Values below are for programmatic access


[PROG-ACCESS]
DATE=11.07.2013
TIME=11:57:40
UNIX=1373543860.082