clearskies_core icon indicating copy to clipboard operation
clearskies_core copied to clipboard

Open source, distributed, secure data synchronization using the clearskies protocol

Results 11 clearskies_core issues
Sort by recently updated
recently updated
newest added

If ClearSkies can generate and accept something like a magnet link, the side channel transmission of the share key can be made much easier for the end user. This is...

The scanner should be triggered on file changes using the platforms file notification mechanism

Using a binary encoding should be more cpu friendly than json.

Change message encoding according to https://github.com/larroy/clearskies/commit/82985ab806527099070bf8f642b6c8a0c2cb598b Encode sizes in binary as uint32 in network order.

The scanner should be triggered on file changes using the platforms file notification mechanism

A peer discovery based on DHT should be implemented. There are good implementations in rtorrent and retroshare that we can reuse / adapt.

The tracker daemon should be implemented according to the protocol description for peer and share discovery

Implement the get updates mechanism as discussed in https://groups.google.com/forum/#!topic/clearskies-dev/UM7Qb3oHZlQ So the peer can get the files that changed since the previous iteration

The scanner should be triggered on file changes using the platforms file notification mechanism

SSL should be plug in in the protocol / message logic in a matter that is as isolated as possible, so we are able to easily choose SSL implementation.