Thank you for sharing, Eric. It’s been a few years now for me since we lost our son before I ever had the chance to meet him and I’m not sure it’s any easier. Stories like yours and that of others help us all know we’re not alone in our grief though so I encourage you to keep sharing and telling your story.
Nice post! I’m curious how the SQLite-per-instance model works for rate-limiting in the scale-out scenario. I took a cursory glance at the docs but nothing jumped out at me about how it works.
Post author and Wafris co-founder here. Conceptually "rate limiting to prevent abuse" (what we're doing here) and "rate limiting for API throttling" have different levels for tolerance.
With that in mind, it's setting higher levels of limiting and doing the math to push that out over many machines/instances/dynos. That helps for things like scraping prevention, etc.
For issues like credential stuffing attacks, you'd want a lower limit but also coupled with mitigations like IP bans, IP reputation, etc. to deal with underlying issue.
Thanks for sharing, and creating! This is great - solves a real problem we have at home, too.
First impression was great, worked as advertised and delighted with the auto-categorisation. Handled a ‘not a tangible item scenario’ (snacks for a share plate at a party) smartly.
I can see a want for multiple lists in our household over time (seemed like I could only have one locally but didn’t try too hard to find if I could).
Love that it is native, lightning quick UI and launch.
Thanks for the feedback! Delighted to hear it's working well for you. Currently, HoneyDo supports one list to keep the initial release simple, but multiple lists are on the roadmap.