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.

Sign up for GitHub

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

Jump to bottom

Contribution #1195

Open
2 of 15 tasks
iamdey opened this issue Feb 1, 2019 · 1 comment
Open
2 of 15 tasks

Contribution #1195

iamdey opened this issue Feb 1, 2019 · 1 comment
Labels
good first issue

Comments

@iamdey
Copy link
Member

iamdey commented Feb 1, 2019 •
edited

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

New protocol

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

Device

Tooling

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.
@iamdey iamdey pinned this issue Feb 1, 2019
@iamdey iamdey mentioned this issue May 29, 2019
Closed
@llebout
Copy link

llebout commented Aug 5, 2019 •
edited

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:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@iamdey @llebout