Configure the monitor to respond to the shutdown string.

Easiest restart policy would be to schedule a timer, then give up after a dozen retries. For now, a dozen retires is all the plugin has, but in the future it can reset its retries if enough time has passed.

For now, I'm going to simply visit www.prettyrobots.com/synapse with a query string that indicates the release version. This wlll let me know if early people are updating Synapse, what version the laggards are one.

In order to do ranged searches, Synapse will need more than a distributed hash table, it will need a distributed b-tree. Built on top of any database engine, each client node can act as tier in the tree, with multiple nodes in the network acting as a distributed root. Those roots would direct traffic through the tree to the client nodes that contained the specific records sought by a query.

Create a listener that will find a way to keep a port open through NAT.

Unlink Safari, Chrome floods the plugin with events which implies a busy loop or else the plugin is supposed to do something to clear a dirty state.

Keep a change log to track progress.

https://gist.github.com/3288316

So long as it's universal.

Removed it without updating CMake.

Find an existing micro-sharing client and add an option to change the endpoint. Any client that already supports both idendi.ca and Twitter ought to already be configurable. This would give the network a full client to start, before the browser plugin offers a client of its own.

Create a minimal Node.js server to launch from NPAPI instead of cubby.

Bump version and see if the Chrome Web Store will update the plugin without user intervention.

Automatically update the Chrome extension using the Google store or your own server.

A bare minimum. All it needs to be able to do is install itself somehow.

Create a peer-to-peer micro-sharing network.

• Statuses and timelines.
• Authenticating statuses with digital signatures.
• Reasonably easy setup and automatic updates.

Synapse 0.2.0 will support OS X, Linux and Windows peers when run from Google Chrome.

Create a plugin for existing web browsers that will launch a peer node. The simple rule for a user would be that if their browser is running, Synapse is running. Initially, it would be easiest to support Google Chrome, Safari and Firefox, on Windows, Linux and OS X, but eventually to also support Internet Explorer. Internet Explorer has it's own plugin architecture, while all other browsers share a plugin architecture.

I'd imagine that it would be not that difficult to get friends to install a browser plugin.