• 6 Posts
  • 26 Comments
Joined 2 months ago
cake
Cake day: October 21st, 2025

help-circle
  • Hi! These are all very valid questions!

    The protection boils down to your level of comfort, really, the way I built this is very modular, you can

    • Simply generate a key pair by clicking on a simple button (for non power users)
    • Import your own keys (if you feel comfortable enough to do it)
    • Or simply encrypt with a public key and use your private key when prompted for decryption, this way keys are never stored on the server and all operations happen offline on the browser :)

    When exporting notes, if one is encrypted it’ll stay encrypted, of course.

    Lastly, the simple answer is because I know the tech fairly well and understand it enough to comfortably implement it, I wouldn’t want to half ass something, PGP is an extremely valid form of encryption anyway, and can be very user friendly when implemented properly (as explained above there’s various levels of complexity in place)

    Very valid feedback, makes me wonder if I should give people multiple choices of encryption algorithms in future updates ♥️








  • Hey! Thank you for testing it out, I think in my head, even the most verbose of dev wouldn’t leave >20% of comments in their codebase. The percentage works on a ratio of (commentsCount / linesOfCode) * 100 so it doesn’t just flag “a lot of comments”, it mostly checks for “too many comments”, that said, the “use common sense” at the top needs to be taken quite seriously, for example if there’s a majority of comments but none of the comments feel like written by AI, it’s clearly just the developer being verbose :)

    p.s. I find AI is pretty damn good at making docker compose files, it’s probably gonna work just fine <3







  • Hey thanks, I was properly looking into WebDAV yesterday, should be simple enough to implement, just making sure I don’t add features for the sake of it, once I’m certain it’s the right way to go I’ll implement it properly, for now my biggest aim is to get the tool as stable as possible ♥️




  • Oh wow, that definitely threw me off lol anyhow, I don’t think I am more knowledgeable than you at all, I just know the tool I built more, so I can help figure out the nuances of it…

    I have a feeling nsenter is not liking your nas for some reason, I wanna try a workaround and if it works for you I’ll go through the code and sort it out so we can use a proper env variable for this

    add this env variable for now and tell me if it sorts you out <3

    environment:
      - PATH=/usr/bin:/bin:/usr/local/bin:/usr/sbin:/sbin:$PATH
    


  • Hi, I went through your logs and it seems like crontab is not installed on the host machine?

    stderr: 'sh: 1: crontab: not found'
    

    The tool uses the host crontab command via nsenter to manage cronjobs, so it only works if ran from hosts that leverage crontab to run cron jobs.

    If that’s not the issue let me know and we can try and debug it together further, but looking at the logs it really seems like crontab is just not installed on your nas (guessing it’s a nas looking at the volume1 path)

    p.s.

    Thank you for the screenshots acknowledgment, I absolutely hate not having a visual aid on repositories when I want to try a new tool, I like to see what I am getting into before I get into it, and I absolutely judge a book by its cover, I am a frontend tech lead, UI is extremely important to me, if an app doesn’t have a somewhat clean UI I kinda refuse to even try using it hahah






  • Oh yeah, that’s not a feature yet. There’s an open feature request for this and I’ll definitely implement it, may take a bit of time to do.

    Would you be able to give me a couple of screenshots on what the context looks like? I just had a simple “mentioned 2 times” with links on where it was mentioned in mind, but full on context sounds way better, I’m curious to see how that works (totally not copying :P)