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

show unread mail count on folders #234

Open
mpfau opened this Issue Jan 3, 2018 · 8 comments

Comments

5 participants
@mpfau
Contributor

mpfau commented Jan 3, 2018

No description provided.

@mpfau mpfau added this to the Roadmap milestone Jan 3, 2018

@armhub armhub added the new feature label Jan 4, 2018

@armhub armhub added this to Planned in Roadmap Project Jan 4, 2018

@x80486

This comment has been minimized.

x80486 commented Aug 8, 2018

Hello there! Are there any updates on this one?

@charlag

This comment has been minimized.

Contributor

charlag commented Aug 9, 2018

@x80486 not yet, sorry, we really want them but we're quite busy with other things now. We will mention this once we start working on it. Thanks for the patience.

@vladimiry

This comment has been minimized.

vladimiry commented Sep 6, 2018

email-securely-app desktop app is going to get this feature supported, see work in progress demo here.

@charlag

This comment has been minimized.

Contributor

charlag commented Sep 7, 2018

@vladimiry this looks very interesting! Any chance of merging parts of it to the Tutatnota itself?

@vladimiry

This comment has been minimized.

vladimiry commented Sep 7, 2018

@charlag that's a desktop app which keeps all the messages/folders/contacts in a local database (in-memory first, with dumping to the encrypted file), fetching is done in an incremental way consuming an event batch updates, similar to how for example mails indexer does it in this project. And that's why app is capable to get the unread counters for all the folders, it basically derives the counters form the local database. So that app works side by side with and in background of a web client enhancing user experience on the desktop. I don't think this would be an exact way to go for the web client, since it's intended to be used just in a browser, ie without Electron/Node.js backup. But technically it's, of course, doable for example to consume the even batch updates in web client, but store only the unread values per folder not overflowing a limited in-browser storage space.

@charlag

This comment has been minimized.

Contributor

charlag commented Sep 7, 2018

@vladimiry thanks for validating my assumptions
Browser storage is not a problem in most cases, you can store GBs of data. Storing whole database in browser is not very secure and that's a real concern. Your proposal with counters makes sense but it will not be accurate unless for the new log-ins, is that correct?
We had an idea of storing counters on the server side and updating them on the client

@vladimiry

This comment has been minimized.

vladimiry commented Sep 7, 2018

Your proposal with counters makes sense but it will not be accurate unless for the new log-ins, is that correct?

Not sure I got this question right. When a user gets logged in app makes sure that missed event batches got handled, see this iteration. Plus there is a logic that listens on the batch updates stream and reacts accordingly, so app could get live updates, see this observable.

We had an idea of storing counters on the server side and updating them on the client

In my opinion, this is how it's supposed to work in most of the cases. Would be great if you go this way, so there will be no need in workarounds/hacks, but simply listening for new values on the stream. Currently used even batch like scenario also works. So desktop/web client gets an "unread"-like EventUpdate, then reacts to it getting the corresponding entity which contains the unread values for all the folders.

@vladimiry

This comment has been minimized.

vladimiry commented Sep 25, 2018

If someone wants to try it in action, I just published the first beta of a desktop app with the enabled feature of showing unread count on each folder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment