This month's theme is supposed to be fixing up whatever might prevent users from using the assistant. To that end, I've posted an open-ended poll, what is preventing me from using git-annex assistant. Please go fill it out so I can get an idea of how many people are using the assistant, and what needs to be done to get the rest of you, and your friends and family able to use it.
In the meantime, today I fixed several bugs that were recently reported in the webapp and assistant. Getting it working as widely as possible, even on strange IPv6 only systems, and with browsers that didn't like my generated javascript code is important, and fits right into this month's theme. I'm happy to see lots of bugs being filed, since it means more users are trying the assistant out.
Also continued work on making direct mode transfers safe. All transfers to local git remotes (wish I had a better phrase!) are now safe in direct mode. Only uploading from a direct mode repository over ssh to another git repository is still potentially unsafe.
I suggest using the term "repository" not "remote". Two reasons: 1: it's a noun in *English. 2: it works for both local and remote repositories.
Both get +1 because they match git terminology. (I have a secret dream that the assistant might bring people to git, maybe that's silly.)
* OK, so "remote" is also a noun in English, but it means the widget with buttons that controls the tv/whatever.
I am not quite sure how git-annex works and I do not know what a "local git remote" functionality is.
How about this: call a "git remote" a "git-annex store" or just "store". Then instead of a remote git remote it would be a remote git-annex store or just remote store.