Communicating about development

This is really about communication rather than development, but I need the input of you developers to help with my communication, so I'm placing this discussion here.

Prompted by Sean's thread asking 'What would you like Diaspora to be in a year's time?' after the release of v0.1.0.0, and the many comments, requests and suggestions made on that thread, I thought it would be a good idea to write about each of these requests, and other elements which are influencing the development of Diaspora now, and likely future development.

You can see Sean's thread here: https://www.joindiaspora.com/posts/2636466

My aim is to cover all the things about which people keep asking 'Why can't D* have x?' or 'Why doesn't D* have x?', in non-technical language to explain why things are as they are, and how they're likely to be in coming months.

For some of these, such as editing posts, this means explaining why the feature is unlikely to be implemented. For others, such as groups and calendars, it means explaining why it hasn't yet been implemented and why it might well be quite a while longer. But at least it people can understand a bit more about why their favourite feature hasn't yet come in, it might make them feel happier about the current state of affairs.
For others, it means saying that we'd love to do it as soon as possible.

However, where I really fall down is my technical knowledge. This is where I need your help. There are going to be lots of factual technical inaccuracies in this piece. I'd love it if you'd look it through and correct these.

In some cases, it'll be a simple case of changing a word or two (for example, where I say that Diaspora was created as bespoke software, using elements from other open-source projects, my understanding may be faulty there and can probably be corrected by a small edit). In other cases, my understanding may have led me to incorrectly say that we'd like to implement a feature as soon as possible, whereas in fact that feature would require a complete rewrite of Diaspora's protocols and therefore isn't desirable.
This might require a greater change.

In the first case, if you could correct what I've written in the draft, that would be great. In the second, if you could explain the reality to me here, I'll then write a revised section for that feature and add it to the piece, for your approval.

It would be good to have a link after each section, or at least most of them, to a place where people can go if they want to help out with that particular element. If you can think of good links for any of the sections, please add them.

There are a few items at the bottom that I either don't understand or am really not sure what to write about them. If you can think of anything to write about them, please do. If on the other hand, you think they'd be better deleted, please say so.

I've added the draft to the wiki. I don't know what markup the blog uses, so I haven't formatted anything yet, although I've used wiki headings to make it easier to navigate. I'll change these to the correct markup for the blog before it's published.

Here's the draft: http://wiki.diasporafoundation.org/Current_and_future_development

Hope this is a useful thing for me to have done, and hope it won't be too much work for you to edit it for me. My hope is that once this is published, it'll reduce your workload in the end, as people understand why certain features haven't been implemented and so don't keep suggesting them time and again. I also hope it'll help recruit some more developers, who can see what help is needed.

Thanks in advance.
Goob