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.

# 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!

Comments URL: https://news.ycombinator.com/item?id=41943931

Points: 12

# Comments: 7

[0]: https://jacobian.org/2021/apr/7/embrace-the-grind/

i.e. what activities, what is the relationship between them, what leads where, what are the interactions, etc?

Is there a tool you use? Or do you just write it out in text?

Comments URL: https://news.ycombinator.com/item?id=17592617

Points: 1

# Comments: 0

[0]: https://github.com/shrayasr/GlobalAirports.Net [1]: https://www.nuget.org/packages/GlobalAirports.Net

Comments URL: https://news.ycombinator.com/item?id=15727716

Points: 16

# Comments: 3

Not sure if it takes from /r/todayilearned though?

Comments URL: https://news.ycombinator.com/item?id=14794752

Points: 5

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=14488343

Points: 4

# Comments: 2

Comments URL: https://news.ycombinator.com/item?id=14443333

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=13077240

Points: 29

# Comments: 3

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.

    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 :)

Footnotes: [0]: http://logicsoft.co.in [1]: https://www.techempower.com/blog/2016/11/16/framework-benchm... [2]: https://github.com/aspnet/KestrelHttpServer/pull/1138 [3]: https://blogs.msdn.microsoft.com/dotnet/2016/05/23/changes-t... [4]: http://ivanz.com/2016/05/17/farewell-project-json-hello-msbu...

The one i've been using for a while now is Marp [0]. Found it to be fast, straightforward and quite powerful :)

[0]: https://yhatt.github.io/marp/