Contribution

[iamdey]

A clean list of features that will be welcome from contributors.

How to ?

1. Choose something in the list or write your own proposition
2. Create an issue and write down what you have chosen
3. Assign yourself

Then we will come back soon to you to help you to start to code.

---

Timeline

• [ ] delete one or more discussions (front: discussion selector, back: api for discussion deletion) (almost everything is done, it needs some refresh)
• [ ] archive discussions and messages (requires more specs and knowledge of the project)
• [ ] Mark discussion as read

Discussion

• [ ] Mark discussion as read
• [ ] delete/archive discussion (cf. above)
• [ ] archive message
• [ ] interactions on short messages (like twitter DMs)

View

• [ ] Improve View conception (a list of messages that meet conditions, a list of drafts will be available soon in a «View »)
• [ ] implement a view (one or n tags)
• [ ] create a view from a search

Client

• [ ] improve and fix UI on smartphone
• [x] implement PWA and take a look to google play https://medium.com/@firt/google-play-store-now-open-for-progressive-web-apps-ec6f3c6ff3cc

New protocol

• [ ] We defitely need an Instant Message protocol (encrypted of course).

Device

• [x] Validate a device using the backup email https://trello.com/c/Q6CJj2CR/167-validation-de-device-mail-backup

Tooling

• [ ] an add to qualify messages by a human https://trello.com/c/zRDnhYjf/174-outil-de-classification-de-messages#comment-5c5422e6a123f847bd348ec6

I18n

Weblate is ready to manage translations of the interface. Go to https://weblate.caliopen.org/, create an account and suggest new translations or languages.

[llebout]

We defitely need an Instant Message protocol (encrypted of course).

It is not possible to provide secure end to end encryption on the web because the web server has full control over the code being delivered to a client and can insert backdoors silentely and selectively. It makes it not suitable for such a use case.

Some solutions exist to solve this problem but none has an ideal implementation or is standardized:

• https://github.com/w3c/webappsec/issues/538 (Native browser checks or WebWorker SRI)
• https://github.com/tasn/webext-signed-pages