Loomio

allow managing non-diaspora xmpp contacts via diaspora aspects

PP
Pirate Praveen Public Seen by 281
PP

Pirate Praveen started a proposal Tue 9 Jun 2015

allow managing non-diaspora xmpp contacts via aspects Closed Mon 22 Jun 2015

Outcome
by Pirate Praveen Tue 25 Apr 2017

Considering all the good comments, withdrawing this proposal.

As many people already have a non-diaspora xmpp accounts they use, allowing seamless integration would make the chat experience in diaspora better. Since contacts are primarily handled by diaspora aspects, having ability to modify them via aspects is natural.

Agree - 11
Abstain - 2
Disagree - 9
Block - 0
22 people have voted (14%)
PP

Pirate Praveen
Agree
Tue 9 Jun 2015

this would make chat experience smoother

JS

Juan Santiago
Agree
Tue 9 Jun 2015

SVB

Steffen van Bergerem
Disagree
Tue 9 Jun 2015

This makes aspects more complex and I'd like to avoid that (currently).

RD

Raju Devidas
Agree
Tue 9 Jun 2015

JH

Jonne Haß
Disagree
Tue 9 Jun 2015

XMPP contact management should stay as much inside JSXC and the XMPP server as possible.

RF

Rasmus Fuhse
Agree
Tue 9 Jun 2015

DS

Dennis Schubert
Disagree
Tue 9 Jun 2015

Aspects are an important part of generating the streams as well as posting contents as we use them as a source to JOIN all the recipients together. Adding non-diaspora contacts creates an insanely large amount of complexity in the whole code base.

C

CodeHero
Disagree
Tue 9 Jun 2015

Maybe add a separate grouping mechanism for xmpp contacts.

JR

Jason Robinson
Agree
Thu 11 Jun 2015

I do agree user experience comes first here.

I'm not saying this can or should be done, I'm just voting regarding the user experience "want". How is a different story.

N

Nicolas
Abstain
Sat 13 Jun 2015

V

ventos
Disagree
Sun 14 Jun 2015

DU

[deactivated account]
Abstain
Sun 14 Jun 2015

A

aj
Disagree
Sun 14 Jun 2015

seems a tad early to tangle these things up :)

AS

Anish Sheela
Agree
Tue 16 Jun 2015

BC

Balasankar C
Agree
Tue 16 Jun 2015

As we are presenting chat a major feature, I think it is sensible to have a provision to manage all the contacts - both diaspora and non-diaspora alike - too.

S

StultuS
Agree
Tue 16 Jun 2015

KS

Kent Shikama
Disagree
Wed 17 Jun 2015

I would rather have our developer resources put toward enabling group chats, improving the chat design, and stabilizing the chat in general.

AA

Alberto Aru
Disagree
Fri 19 Jun 2015

AA

Alberto Aru
Agree
Fri 19 Jun 2015

F

Faldrian
Disagree
Fri 19 Jun 2015

XMPP Contacts are manageable by tje XMPP-Client... the diaspora-code is challenging to read as it is, no need to add complexity in aspect management.

F

Faldrian
Disagree
Fri 19 Jun 2015

XMPP Contacts are manageable by the XMPP-Client... the diaspora-code is challenging to read as it is, no need to add complexity in aspect management.

T

thomas
Agree
Fri 19 Jun 2015

FF

Fayad Fami
Agree
Sat 20 Jun 2015

I think this feature will help to organize chat experience and most importantly help people who prefer to use diaspora as their main and only account for xmpp.

JR

Jason Robinson
Disagree
Sat 20 Jun 2015

If servers offer XMPP functionality, they should allow managing contacts too. But as highlighted by several good comments, not through aspects.

AL

Alex L.
Agree
Mon 22 Jun 2015

G

Globulle Tue 9 Jun 2015

Since I haven't experienced the XMPP chat on diaspora*, it is not clear for me. So far, here is what I've understood:
non-diasporian contacts are already accessible from the chat on diaspora*, the present proposal would push it a step further by managing these non-diasporian contacts. Am I right?

RF

Rasmus Fuhse Tue 9 Jun 2015

Technically it might be correct to separate XMPP- and diaspora-contacts. But for the user it will be hell to have two different mechanisms to handle his/her contacts. Especially when you think that 99% of all XMPP-contacts will be diaspora-contacts. I just want to have one area to manage my contacts not two.

Aspects are an important part of generating the streams as well as posting contents as we use them as a source to JOIN all the recipients together. Adding non-diaspora contacts creates an insanely large amount of complexity in the whole code base.

Note that this proposal is not about how this is implemented in the database. It is about the user-experience.

PP

Pirate Praveen Wed 10 Jun 2015

I would like to echo what @rasmusfuhse said, it could be implemented as a different backend and we only need to be able to manage these contracts from the main contacts page. It could be shown as a separate aspect altogether.

PP

Pirate Praveen Thu 18 Jun 2015

@theworldbright you have misunderstood this vote. The outcome of this vote will not affect project priority or force anyone to work on it. All it does is to allow anyone to interested in this issue to work on it and get it accepted in the main code base. If you feel those issues are more important for you, then you can add bounties for those issues.

KS

Kent Shikama Thu 18 Jun 2015

@praveenarimbrathod Maybe I should have stated I do not want this feature until the chat is stable, the chat design is polished, and group chats are enabled. If someone tries to add this feature in before the features I mentioned above are implemented, it would complicate the implementation of those features. Do you think I should still switch my vote from disagree to abstain based on my argument?

AA

Alberto Aru Fri 19 Jun 2015

What if the allowed us to add another xmpp account?

PP

Pirate Praveen Fri 19 Jun 2015

added 7 more days for more discussions as its controversial

JS

Juan Santiago Sat 20 Jun 2015

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.

SVB

Steffen van Bergerem Sat 20 Jun 2015

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?
PP

Pirate Praveen Sat 20 Jun 2015

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

SVB

Steffen van Bergerem Sat 20 Jun 2015

@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.

PP

Pirate Praveen Sat 20 Jun 2015

@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

JH

Jonne Haß Sat 20 Jun 2015

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?

JH

Jonne Haß Sat 20 Jun 2015

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

PP

Pirate Praveen Sat 20 Jun 2015

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

JR

Jason Robinson Sat 20 Jun 2015

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

PP

Pirate Praveen started a proposal Mon 22 Jun 2015

allow managing non-diaspora xmpp contacts via contacts page Closed Sat 25 Jul 2015

Outcome
by Pirate Praveen Tue 25 Apr 2017

It is too early, we'll revisit it when chat is stable

We need a way to add, remove or edit xmpp only contacts from diaspora web interface. It can be separately handled from aspects.

Agree - 5
Abstain - 2
Disagree - 9
Block - 0
16 people have voted (10%)
JR

Jason Robinson
Agree
Mon 22 Jun 2015

PP

Pirate Praveen
Agree
Mon 22 Jun 2015

This avoids complexity of earlier proposal

JH

Jonne Haß
Disagree
Mon 22 Jun 2015

I'd like to see how our JSXC fork develops and how our UI redesign goes before committing to something like this.

JS

Juan Santiago
Agree
Mon 22 Jun 2015

F

Faldrian
Disagree
Mon 22 Jun 2015

CS

Corvus Schwarzfeder
Disagree
Mon 22 Jun 2015

As long as there is no stable chat, it´s too early for this.

BC

Balasankar C
Agree
Wed 24 Jun 2015

This proposal is simpler and states what is needed properly.

AS

Anish Sheela
Abstain
Wed 24 Jun 2015

T

theradialactive
Agree
Wed 24 Jun 2015

R

Ravenbird
Agree
Wed 24 Jun 2015

R

Ravenbird
Disagree
Wed 24 Jun 2015

S

SuperTux88
Disagree
Wed 24 Jun 2015

M

Milan*
Disagree
Fri 26 Jun 2015

AF

Alexander Finkhäuser
Disagree
Fri 26 Jun 2015

FG

Frederic Guilbault
Disagree
Fri 26 Jun 2015

I will agree with the proposition once the chat will work propely

Q

Quetschwalze
Disagree
Wed 1 Jul 2015

I think the Chat is still in an early phase. Also only few pods have it enabled at the moment due to it not working too good at the moment. Therefore I think there are more urgent things to do - however as soon as it's fixed I would agree!

F

Flaburgan
Abstain
Fri 24 Jul 2015

JR

Jason Robinson Wed 24 Jun 2015

@praveenarimbrathod can you extend the proposal please? 3 days is way too short :) A few weeks at least imho.

PP

Pirate Praveen Wed 1 Jul 2015

@fredericguilbault @quetschwalze this needs to be active only on pods were chat is already enabled.