cc @cryptix

have you folks seen %l38IKP+...

cc @mix and @cryptix

for future image search reference

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.

I'm really interested in attending just to listen, but I'll be inside a car, I'll try to attend, let's see!

Likewise I'd love to come to this, but am not going to be able! Hope it goes well, looking forward to hearing back all nerdings

@realisation The time you see is adapted to your timezone. The ui doesn't tell you think.

somebody should fix that so I don't have to say this every time!

e.g. I see 10pm July 13. If you're somewhere else you'll see something else

@mix in the new patchwork:

All thanks to @squicc aka @stripedpajamas!

NICE!
I still wish we could figure out a way to share components. I'm sad that our best approach is copy pasting. Maybe it's ok, but patch-gatherings and patchbay-gatherings have me feeling sad when I look at them...

@mix @cryptix and @Matt McKegg, I am running some minutes late as I am walking to a starbucks.

okay @SoapDog!

I'm alread mumbling ( celehner.com / default port ) and created a hackpad for notes.

Hey guys, I'm trying to connect to listen but mumble keeps timing out (celehner.com, port 64738). Am I doing it right?

huh... those should be the right details, @Luandro

Try the IP rather than celehner.com? ( celehner.com )

woops, I pasted it wrong :P

104.236.22.57

That was the lovliest call. Thank you all, I really enjoyed it and am very excited

sorry you had connection troubles @Luandro

NOTES here

Got it working, great to hear yall voices.

Also enjoyed it very much!

Here are my two bits from the blockers to make milestone 0 a thing. The rest is just TODO..

• I cleaned up the systrayhelper a lot and it can be fetched from gh:ssbc/systrayhelper releases now.
  I'm fairly certain in the macOS (uses native travis env) and windows (just bundles a DLL, no windows env to compile required) versions.
  I'm not sure about the linux version, travis uses some recent ubuntu but I think it will fail to work on other system. These have to use go get github.com/ssbc/systrayhelper && sudo mv $HOME/go/bin/systrayhelper /usr/local/bin until we can supply native dist packages for debian/archlinux/fedora etc.

• I only hacked node-systray, which starts the above helper, to look for the binary in $PATH. What is needed for a published version is some kind of postinstall script that fetches the correct binary for the target system from releases above and puts it in a place where it can be started. I'm not really confident using the forked version of node-systray before we figured this out somehow. The current approach works more albeit being dirty.

ps: I dumpted the call notes.md just in case.

Friends, as discussed in our meeting today I've added tentative support for custom plugins to #scuttleshell. There is more info in this thread. Be aware that so far there is no conflict checking or anything like that, all you can do is pass an array with stuff that will be mapped to individual .use(require(...)).

Great call notes.md! Most of the topics I was interested in discussing or hearing were there, e.g. how to manage plugins, how to support all the current apps, etc. The milestones look good :)