maxking / maxking/hyperkitty.el
Offline support
Nobody has claimed this yet.
- Dominant language
- Emacs Lisp
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the entire functionality of the system relies on online API calls to Hyperkitty. This can cause un-necessary load on servers for re-reading same threads/emails and not to mention. Ofcourse, it removes the ability to use this package to read archives when offline.
In order to support offline support, we need to accomplish the following things:
- Define some local storage method, it can be files or sqlite databases. Files might be easier to manage.
- Write responses from API to local storage
- Render all views based on local storage.
Each of the above will also have some sub-tasks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by mapping the package's Hyperkitty API calls and the views that consume their responses; the issue does not name files or tests. Define a local file or SQLite storage approach, persist API responses, and update every view to read from that storage. Done means archive threads and emails remain readable without network access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- emacs-lisp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100