[rarrrrrr]

SpiderOak might be interested in running a Roughtime service / participating in a Roughtime community to support Semaphor.

As it is, Semaphor clients include a local timestamp among the signed content of most actions, and the server rejects actions that aren't within some tolerance (strict ordering however is accomplished via hash chain.) Roughtime would allow improving this situation from several angles.

One of the logistical challenges is client network traffic footprint. Enterprises that deploy a collaboration solution often want to have a strict definition of which upstream servers it can be expected to talk to. Would it be possible for a single Roughtime service to incorporate verifiable information from a larger Roughtime community, such that end user clients don't have to communicate with additional addresses?

[sargun]

At the bottom of the page, they mention to get in touch, either via the mailing list (https://groups.google.com/a/chromium.org/forum/#!forum/proto...), or directly.