Notes

keys needs to be decoupled before integrating javacard (for the release; we can continue development though)

PFS update

follow the process described on discuss

Go part is implemented

there are still some cases when a bundle cannot be exchanged and the UX solution is required

docs must be finished yetStatus Desktop must-haves

figure out crucial features that needs to be implemented

objective: use it as a replacement for Slack

list of features to have the green light to consider replacing Slack:

reliable messaging for 1-1 and public chats

mentioning users

multiple chats open

we still need feedback and input from people what is crucial; at the same time we don’t want to include features that are hard to implement but not 100% necessary (especially features that touch the library)

Pedro: auto-updater is important due to planned frequent changes

Pedro: URLs are not clickable

Oskar: replacing Slack might not be the best wording; we aim for unblocking usage of Status Desktop first

Pedro: switching between chat windows is slooow

Jacek: a few features that are not necessary related to secure messaging but some improvements for good UX for developers and contributors to open source projects

Oskar: these features are not available in the “traditional” tools like IRC

Jacek: do we optimize the UX and available features for the right people?

Vitaliy: the main objective it’s to make it usable internally; phase 2 could be to make it more efficient and appeal to other group of people

Jacek: developers might have pretty different requirements than other groups of people

Jacek: a bridge between Status Desktop and Riot might be a good feature

Oskar: suggested “themes/modes” in the future where one is optimal for developers and another one for another group

Oskar: images can also be a limitation (requires IPFS/swarm integration)