Thanks so much for engaging :) I understand your point, here's sort of the philosophy behind the decisions we took regarding it:
The purpose of the app was to be as _hands off_ as possible. And because an LLM is involved in the mix, it might misclassify some emails and delete them.
For this reason, we label each email that we delete and it is possible to navigate to the email from the Run Status screen also, thereby allowing us to recover that email (if it was wrongly deleted). There is also a filter on the run status page to show all those emails marked for deletion.
In all our test runs, we found misclassification to be a minimum and hence we felt confident to go with this approach.
The "Schedule new cleanup" does indeed schedule a background task that does the actual inference + deletion.
Hey HN! We’re a small team of friends who built an app to help you clean up your Gmail inbox — privately and locally.
# The Problem
We all get bombarded with emails, making inbox management overwhelming. Many tools can help, but they often require cloud access, risking your data privacy.
# Our Solution
Our app uses local large language models (LLMs) to smartly organize your emails, highlighting what’s important and filtering out the noise — without sending data to the cloud.
# Why It’s Different
- Private: Runs entirely on your device; no data leaves your machine.
- Open Source: You can review everything before using it.
# Why It Matters
In a world where data privacy is crucial, our app provides AI-powered inbox decluttering without sacrificing control of your information.
We’d love to hear your feedback and ideas to help us improve. Thanks for checking us out!
Kiran addressed a very similar (if not the same) topic at the PyCon India 2013 keynote: https://www.youtube.com/watch?v=_stsJlNgGfA (40 mins). I was there at the keynote and it really helped set my basics very strongly. Highly recommended.
The thing that most surprises me is that the highest searched tag in Bangalore, India is JSP. Looks like offshore development is still a big thing in the city that is widely regarded as the "silicon valley of India"
Full disclosure: We [0] have been a .NET/Windows house since the product was
launched 8 years ago.
When RC1 of .NET core was announced, we jumped on it (in spite of all the
limitations that it came with) and haven't been disappointed. We've been
working on a product whose pilot version handled to the tune of 40K requests in
a day on a 1GB/1Core Linode box
---
As far as choice of platform goes, it all comes down to a few factors for me
1. What the team is comfortable with:
This is *crucial* and in retrospect it is the biggest contributing factor
that helped us take our next product to production -- fast. If you have a
team that is comfortable with .NET then just go for it. Everything else can
be figured out later.
2. What the ecosystem is like:
If you have a fair idea of what you're building out, scout the ecosystem
and see if it offers everything that you need. We more or less found
everything that we needed except a good Excel wrangling library.
---
Also I feel the .NET core VS Node question is skewed because comparatively,
Node is a platform that has been around for much longer and has much bigger
adoption.
Keeping this in mind, there will definitely be problems with .NET Core. Eg: If
you're looking to reference a class library that is running with the full
framework then you'll be hitting a few hurdles and stoppers.
The good part however is that it is constantly under work and we're able to
actually see the performance improvements. [1][2]
The bad part however is that it is constantly under work so expect flux. [3][4]
---
Experience wise, its been great working with .NET Core. Projects like VS Code
make it a breeze. To me, C# has always been a well architected, beautiful
language and now I'm able to write it in the way I want to -- without using a
bloated IDE like Visual Studio and run it where I want to -- On cheap linux
boxes without worrying about licensing costing.
For us at Logic Soft, .NET core really was a lifesaver when our next logical
transition was the web and we were a .NET house shipping software on windows :)
The presentations look wonderful. Zach has constantly been my inspiration to make better slides. Almost ALL my slides[0] incorporate some of his teachings :)
For someone who is on windows, this is a godsend. The Mac guys all have Deckset[0] which is amazing. Was searching for something like this to make quick slides. Thanks much :)