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

Implement DB schema to support todo lists and tasks #264

Open
elimisteve opened this issue Feb 12, 2023 · 0 comments
Open

Implement DB schema to support todo lists and tasks #264

elimisteve opened this issue Feb 12, 2023 · 0 comments
Assignees

Comments

@elimisteve
Copy link
Member

Some considerations:

It would be nice to be able to hide from the DB...:

  • Whether or not a task is done
  • Who has been assigned a task

Task titles tend to be small, and thus encrypted tasks will be small (if there are no task descriptions), so maybe just re-encrypt a task every time its assignee or done status changes? Because then the assignee and done status can be stored as metadata stuffed into the filename field, which is where chat messages store who they're from.

Or the status and assignee of a task could simply be stored encryptedly in other blobs, but then tasks wouldn't be as self-contained; there'd be multiple columns per task. That isn't the end of the world, but... it's less elegant. Plus decrypting 3+ small blobs per task will be a lot slower than decrypting 1 slightly larger blob per task that simply contains all the fields. That means that doing what I described above would likely lead to faster app startup times, which is an important thing to optimize for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant