[US-27] As a user, I want my contacts list to show channels I can reach a person through (ELFA DM, Matrix, XMPP, Signal, email, WhatsApp), so I can pick how to respond without leaving ELFA. #4
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ELFA/rfd#4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A fully unified inbox is flagged as technically hard (email threading fragments easily). Citing @jeremiah Embedding all of those into ELFA seems unnecessary.
[US-27]to [US-27] As a user, I want my contacts list to show channels I can reach a person through (ELFA DM, Matrix, XMPP, Signal, email, WhatsApp), so I can pick how to respond without leaving ELFA.having interop with all those external messengers is clearly out of scope of this grant. It has been mentioned here as an example.. for future iterations.
Still, the concept that from the same contacts entry, I can interact with that person via different channels/protocols, is interesting. For now we will only implement DMs within NG. And the question of email integration arises. Also we do have the collaboration with ActivityPods that is going on and will be ready soon, so DMs exchanged in mastodon could also be unifed here.
So, the main question here about unifying the inbox between emails and DMs. It would be important to clarify this very soon, as the work on the messenger (by Jeremiah) and the email inbox (by Ani) is about to start.
Perhaps it's best to first provide the UX people are accustomed to and later iterate on a unified concept. However, aligning now on the data model for messages will help future unified UX exploration.