1.14 is probably the last official hubzilla release prior to 2.0, which will be released sometime in December in the absence of significant roadblocks.

Any developers (real or aspiring) who wish to see any features or documentation or translation improvements in 2.0 are advised to start working on them soon and give us a chance to review them. Tick, tock.

Most of the v4 (hubzilla 2.0) roadmap has been completed. I've been working on v5 for the last month or two (in between the typical distractions). There are probably a few more surprises before Xmas because that's just the way we roll, but otherwise I'll see you all on the other side. If you know of something you really think would be important in 2.0, now is probably the time to #makeithappen.

For welcoming new people, there is a plugin an admin can activate for a "hubzilla tour"I also recommend having users make /apps be their homepage for hubzilla. This is a familiar interface and a reminder of all the tools you have.

In 1.14 I've created the infrastructure so you can have directories of help information with table of contents indexes in each. The table of contents (if present) is loaded into the sidebar. You can see an example in the doc/project directory - which shows sort of how to extend this organisation to the rest of the documentation. Most of the existing documentation is all currently crammed into the top level folder. It would be most useful to start organising it all into folders. All of the roadmap and todo stuff belongs in its own folder, (perhaps called 'planning' or something like that) with an index file.

I think that might be possible (it's now called shredda or shredder - it turns out "shred" is the name of a tool which writes random bullshit to disk devices and we don't want you invoking the wrong one by mistake.). Anyway, so we use OAuth to log you into your hub. Then 'curl with cookies' to get at other zot sites from there and magic-auth to them. I once wrote a little C program to provide a "cd" and "ls" ability for navigating the file-lists of archival tapes as if they were a filesystem and it doesn't really require much overhead. You just store the current working directory and make an api call to list the files or cd somewhere else. It's all perfectly do-able.