You are reading content from Scuttlebutt
@cryptix %TI6VNvA8hY9IhBuamkY7guCT9fxQbON+SaNq/Xi9DZ8=.sha256
Re: %gGzTm8OyS

YEY! really looking forward to what you folks have on your mind for this!

Previous progress reports: nixos packaging unearthing the helper and the binary bloat, cel building it on arm with my update and new repos in the same thread.

tl;dr: systrayhelpers built through travis-ci for all kinds of platforms (at least linux, darwin and windows) on the horizon. Need to figure out the helper install story through npm for node-systray, maybe post-install based?

Food for thought:

  • What kind of actions through the systray might be nice to have? Apart form Quit
    • Open Statuslog? let's not loose sbots stdout. Maybe in a small gtk window, or spawn some terminal with tail -f .ssb/logfile.
    • Gossip status? Number of open connetions, feed DL in progress, index in progress, etc. could all be done through update-menu messages
  • Plugin selection
    Not that we have one shell to rule them all might want to revisit plugin needs of the clients again? Just so that patchfoo, -bay, tictac and others work out of the box until we can start to testbed out-of-process plugins.

~~~

@Connor: Heh.. Sorry about coordinating across the globe like this didn't leave us with many options.

Join Scuttlebutt now