noah- / ramble Goto Github PK

We can say apache gossip is being used to bootstrap clients and public keys

for fanout c, find c random clients and send them messages
on receive message, if not previously broadcasted, send out to c random clients
commit to db after gossip

Need a front end that can show messages with replies. Can be built recursively. Should display sorted by timestamp.

apache-gossip has a Replicable interface that defines if a given message should be replicated from a src node to a dest node. We should be able to use this interface to implement blacklists.

API: getDigests -> returns set of digests

index by timestamp, message digest, add parent to schema

For every gossip peer to peer message, nodes must verify a merkle tree of last committed time block span, merkle tree can be based on timestamps with period of 1 min (all messages digests of a time period are sorted in a block, hash of block is compared, if not the same, exchange digests and reconcile messages. If a failure occurs, work up the merkle tree until a block match is found. This allows eventual consistency. Reject messages with timestamp (delayed messages for example) after some period of time (basically require originator to rebroadcast with new timestamp).

api: isSpam(Message m) -> boolean
Spam Filter: log fingerprint:count, threshold value, write to database