Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable group chats in release build #6882

Closed
lukaszfryc opened this issue Nov 26, 2018 · 22 comments
Closed

Enable group chats in release build #6882

lukaszfryc opened this issue Nov 26, 2018 · 22 comments
Assignees
Projects

Comments

@lukaszfryc
Copy link
Contributor

lukaszfryc commented Nov 26, 2018

Enable group chats and pairing in release builds and cherry pick it into release/0.9.32 branch. Both features should remain under development mode.

Please update release changelog afterwards https://notes.status.im/mobile-release-notes?both

@lukaszfryc
Copy link
Contributor Author

@cammellos could you share your thoughts on what's needed to release the group chats? Is the core work already done?

@lukaszfryc lukaszfryc added this to In progress in Core Chat Nov 26, 2018
@cammellos
Copy link
Member

@lukaszfryc if no blocker have been reported, I would just want to push out a couple of commits to fortify the implementation but otherwise we are good to go.
I would release them in development mode at first & then after a couple of weeks of feedback enable them.

What do you reckon?

@chadyj
Copy link
Contributor

chadyj commented Nov 27, 2018

@cammellos Whilst on the topic can you outline the PFS release plan too?

@cammellos
Copy link
Member

cammellos commented Nov 27, 2018

So, if no issues have been reported on group chats & pairing, I think we can start thinking about releasing PFS and getting things ready.

  1. Pairing as it is released is already fully pfs, so no work to be done.

  2. 1-to-1 we need to handle a few cases https://discuss.status.im/t/pfs-and-missing-contact-information/362/24 & https://discuss.status.im/t/pfs-and-wallet-recovery/335 which will require some UI work.

  3. Group chats to be fully PFS will also require some ux changes (probably in the form of having to accept the chat invitation), but this will be done after 2 as 2 is easier to handle.

Enabling PFS for 1-to-1 will be a breaking change, but if we release group chats (or pairing, or both ) next week, those clients will be already compatible, so it will give us a bit more time for users to upgrade, making the upgrade less painful.

Status.im
Thanks again @cammellos for going through all the explanations. So it sounds like we will always have this use case for when Alice tries to contact Bob using a public key? Sorry if I misunderstood this point. I’m all for the approach and thanks as well to @denis and @maciej for putting together designs so quickly. To follow up on Hester’s question: what does Chad see as long as the contact request has not been accepted? Do we allow Chad to continue the conversation with a clear icon/visual ...
Status.im
Hello everyone, as you know we are working on PFS. The main idea is that we will exchange an x3dh bundle and encrypt message using the double ratchet algorithm. https://signal.org/docs/specifications/x3dh/ https://signal.org/docs/specifications/doubleratchet/ A problem that we need to solve is wallet recovery and how to handle this. When a user recover their wallet they will lose all the contacts and messages. Currently if a contact sends a message to a user who has just recovered their ac...

@lukaszfryc
Copy link
Contributor Author

if no blocker have been reported, I would just want to push out a couple of commits to fortify the implementation but otherwise we are good to go.

@cammellos there are no blockers. Only issues we already discussed that can be fixed later.

Re releasing group chats in dev mode, I don't think anyone will use them this way. So, we will not learn anything besides just having the code enabled in the release build. I'd suggest to enable them in normal mode for nightlies and include in the next release. @cammellos?

@cammellos
Copy link
Member

@lukaszfryc I am ok with that, the only reason to have them in dev mode would be to warn users that is a beta-feature.

So as long as we warn users that is a beta feature, I am ok in having them always on, in order to manage expectations.

@cammellos
Copy link
Member

What about pairing, should we do the same? release it I mean? The only thing I would want to add is a way for the user to name its device, but other than that if no issues/blockers I'd be happy to release

@chadyj
Copy link
Contributor

chadyj commented Nov 27, 2018

+1 for rolling this out. We can be sure to communicate to users this is an early feature and testing and feedback is appreciated.

@lukaszfryc
Copy link
Contributor Author

If we still consider it a beta-feature, it makes sense to put it under dev mode. I think it's the best way to indicate (inside the app) that something is a beta feature.

@cammellos
Copy link
Member

@lukaszfryc what about something like:
Start group chat (Beta)? We can also add a Beta tag somewhere in the actual group chat, it feels that way it's clear

@chadyj
Copy link
Contributor

chadyj commented Nov 27, 2018

Note, the whole app is in beta! Every feature is a beta :)

But it won't hurt doing Start group chat (Beta). :-)

@lukaszfryc
Copy link
Contributor Author

Start group chat (Beta)? We can also add a Beta tag somewhere in the actual group chat, it feels that way it's clear

Hm, I first thought that "dev mode" is for beta-features. But, we can actually differentiate between "options for developers" (dev mode) and beta features.

Note, the whole app is in beta! Every feature is a beta :)

Yeah. I'd say that if there is no major issue that we want to warn about, I'd not bother users with "Beta" word in yet another place.

@lukaszfryc
Copy link
Contributor Author

What about pairing, should we do the same? release it I mean? The only thing I would want to add is a way for the user to name its device, but other than that if no issues/blockers I'd be happy to release

@churik I see we have some "pairing" issues that are leftovers after #6697. Is any of them a blocker for releasing the pairing in current state?

@cammellos
Copy link
Member

ok, in any cases, we are all in agreement about releasing next week, when are we cutting the release branch these days? sometimes early next week? just to get things organized

@lukaszfryc
Copy link
Contributor Author

ok, in any cases, we are all in agreement about releasing next week, when are we cutting the release branch these days? sometimes early next week? just to get things organized

@cammellos let's discuss it in #6891

@churik
Copy link
Member

churik commented Nov 27, 2018

@lukaszfryc

@churik I see we have some "pairing" issues that are leftovers after #6697. Is any of them a blocker for releasing the pairing in current state?

I don't think so if both Group chats and syncing were under development mode.

@lukaszfryc
Copy link
Contributor Author

@churik so you mean we can release pairing? Btw, for group chats, we are planning to use "Start group chat (Beta)" to indicate that it is a beta-feature. Do you think we should do the same for "Devices (Beta)"?

@lukaszfryc
Copy link
Contributor Author

According to #6891, the release branch will be created today. @cammellos could you go ahead and enable group chats in release builds?

As for pairing, I still think we should improve on UX there (see #6898 (comment)). At least update copies. But if we do not have time, we may include it in the release and see if someone will use it.

@churik
Copy link
Member

churik commented Nov 28, 2018

@lukaszfryc I think it should be under development mode, as this feature is still WIP.

@lukaszfryc
Copy link
Contributor Author

@cammellos I updated description of this issue and assigned it to you.

@lukaszfryc
Copy link
Contributor Author

group chats and pairing were enabled in dd21f6a

Core Chat automation moved this from In progress to Done Nov 29, 2018
@chadyj
Copy link
Contributor

chadyj commented Nov 29, 2018

Awesome!
Release notes updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Core Chat
  
Done
Development

No branches or pull requests

4 participants