allow managing non-diaspora xmpp contacts via diaspora aspects

added 7 more days for more discussions as its controversial

Here I see two different businesses.

1) Would you like to allow non-diaspora xmpp managing contacts via diaspora aspects?

If the answer to 1 is yes.

2) you think this is the time to implement "1" or think we should wait until the chat is more mature.

Let's go through some UX issues that we would have cope with if we would use aspects to manage non-diaspora XMPP contacts.

• Currently you can start a conversation with all contacts in an aspect. Since some could be diaspora* contacts without an XMPP account and some could be XMPP contacts without a diaspora* account we would either have to disable that feature or we would have to explain to the user that he/she can only start a conversation with some of the contacts.
• You can make contacts in an aspect visible to each other. AFAIK that doesn't work for XMPP contacts so again you would have to explain that to the user or disable the feature.
• On the contacts page you can click on a username to go to the profile page. That doesn't work for XMPP contacts so you would have to explain to the user why some usernames are links and some aren't.
• You can send a post to selected aspects. All contacts in those aspects can see the post except for XMPP contacts. Again you need to explain that to the user.
• What should happen when you try to add an XMPP-only contact to an aspect with disabled chat?
• What should happen when you have an XMPP-only contact in an aspect and disable the chat feature for that aspect afterwards?
• How do you add XMPP-only users to your contacts?

@steffenvanbergerem it can be named "XMPP only" and added at the end of list of aspects in contacts page. It can be managed separately.

@praveenarimbrathod Then those wouldn't be aspects but XMPP groups that we display on the contacts page. That is not what this proposal is about.

@steffenvanbergerem my requirement is a way of adding non-diaspora xmpp contacts from diaspora and adding them to aspects seemed like the most natural thing to do. But if that is too complex and confusing, then doing it separately would also do.

update: corrected

Proposal:

allow managing non-diaspora xmpp contacts via aspects

Your last comment:

adding non-xmpp contacts from diaspora and adding them to aspects

Now what is it? non-diaspora contacts or non-xmpp contacts?

@jasonrobinson I think Steffen outlined how this is also harmful to UX not only code complexity. Do you disagree with his points?

@jhass sorry for the confusion, I meant non-diaspora xmpp contacts only.

@jhass yeah, not through aspects. Thinking more specifically at this, changing my vote..