dashboard / amolith/lune / listing real name of tasks #126 rss

closed · opened on 2026-04-26T20:09:33Z by blocked
Help
checkout latest patchset:
ssh pr.pico.sh print pr-126 | git am -3
checkout any patchset in a patch request:
ssh pr.pico.sh print ps-X | git am -3
add changes to patch request:
git format-patch main --stdout | ssh pr.pico.sh pr add 126
add review to patch request:
git format-patch main --stdout | ssh pr.pico.sh pr add --review 126
accept PR:
ssh pr.pico.sh pr accept 126
close PR:
ssh pr.pico.sh pr close 126
Timeline Patchsets
blocked created pr with ps-218 on 2026-04-26T20:09:34Z
amolith changed status to closed on 2026-06-21T17:01:31Z
Hello, and thanks for the interest in lune! There are some interesting ideas in here, like sorting, status colors, and the interactive update approach, but I definitely don't want to scrape Lunatask's local DB or store the master password in plaintext because especially the latter weakens Lunatask's security model. Storing it in the system keyring might be an interesting approach, but I'm generally inclined only to read content intentionally exposed by Lunatask. The creator has said he's considering something like an API/MCP server built into the desktop app and I'd happily integrate with that! Scraping the Electron db and storing the master password on disk are going a bit far for my taste and the majority of this patch request is in support of those afaict, so I'm closing it. However, you're welcome to submit the other things—storing, colours, more TUI—separately, or of course keep everything in your own fork! :)