Next

Goals

• Merge group conversations into existing messenger layout (front#1467)
• Enable conversations at the channel level and merge into existing messenger layout
• Streamline notifications and navigation for better UX and accessibility
• Implement optional E2E encryption where possible

Mockups

Web (Expanded Contact List)

Web (Minimized Contact List)

Web (Settings Open)

Web (New Tab Pop-out)

Mobile App

Mobile Web App

Notifications

Messenger (Web)

• Should work similar to how current Messenger notifications work
• Mimic Wire/Slack notifications
• Enable desktop notifications
• Show most recent message from each group or channel in list
• Put most recent messages at top of list in real-time

Messenger (Mobile App)

• Mimic Wire/Slack notifications
  • “Minds Team: Jack: Hey guys check out the new notifications…”
• Navigation must take you directly to correct spot in open message thread

Controls

• Allow users complete granular control over every notification type: email, web, push (on/off toggles)

added scoped labels

added 1 deleted label

changed title from Messenger groups and attachments to Messenger groups and attachments

changed title from Messenger to Messenger

added issue minds#317 (closed) from epic &54

mentioned in merge request front!293 (closed)

changed the description

changed the description

mentioned in epic &44 (closed)

Why not using the Signal Protocol for the messenger APP?

I have no idea if this is a feasible change to the system, it'd require a more senior devs eyes, but I can certainly say we will make sure to consider it as we approach this epic, and thank you for taking the time to comment.

As long that there is encryption during transit and at rest so that no one can snoop the messages even Minds, that is all that matters!

@benhayward.ben,
Out of interest, when specifying E2E encryption (which I am guessing is an abbreviation for "End to End" encryption) what method is being considered an implemented?

Will the facility be based on some form of certificate authority / public key (ie. PGP or self-signed X.509 styled) methodology or using some other principle?

Are there any further Gitlab entries that corresponds to the E2E encryption functionality?

removed issue minds#317 (closed)

added issue engine#577

changed the description

added issue front#1467

changed title from Messenger 2.0 to Messenger 2.0

added scoped label

@ottman I just realized that there is no mention of message attachments in this. Is that still part of the plan?

Yes!

@medworthy check out https://gitlab.com/minds/engine/blob/master/Helpers/OpenSSL.php#L14 for the current implementation.

I'm unsure what the plans are moving forward though, somebody else may be able to clarify. I believe the current implementation restricts us into not having attachments in messenger, which is less than ideal, but perhaps there is a work-around for that that I'm unaware of.

@benhayward.ben,
So currently the messaging does use self-signed SSL (x.509) certificates (using the RSA algorithm).

@benhayward.ben & @ottman,
Will there be any restrictions on the types of file formats (mime types) and / or file size that will be allowed to be transferred?

I mean yes most likely but in an ideal scenario, no. We will have a more fleshed out epic soon

Just wanted to highlight @onecrazychief 's comments here: engine#696 (comment 198353622)

Sometimes I just want to log in quick and check my notifications or my wallet balance. I would prefer to not have people see me as being "online". Maybe let the user set the status as: online, offline, or invisible and also be able to set an away message?

mentioned in issue engine#696

mentioned in epic &84

added epic &84 as parent epic

@ottman & @benhayward.ben,
I am wondering if there has been any progress regarding the development / implementation of the messenger 2.0 facility.

It has been 3 months since I last looked at this epic and there seems to be no new milestone due date (and also noticed that the E2E encryption roadmap entry / epic#13 was closed at the beginning of October).