Live data from Hacker News

Ask HN: What Are You Working On? (December 2025)

news.ycombinator.com

351–360 of 1001 posts

Re: Ask HN: What Are You Working On? (December 2025)

#351
I’m working on 2zuz, a product search engine that optimizes for the users rather than the advertizers.

The goal is simple: if you search for something specific, you shouldn’t have to scroll through ads, “inspired by your search”, or completely-irrelevant junk. You should just only see products that actually match exactly what you’re looking for.

Right now it searches across a few large stores and I’m iterating on the ranking and filtering. If you buy a lot of stuff online, I’d love feedback on where the results feel clearly better, and where they still fail compared to Amazon/etc.

Link: https://2zuz.com

Re: Ask HN: What Are You Working On? (December 2025)

#353
Working on a low cost email service. Ditched Gmail for my custom domains to avoid lock-in risks, and I believe devs really need stupid-cheap ($10/yr 5GB, unlimited mailboxes/domains/aliases/SMTP/IMAP/webmail) high-quality hosting that nails deliverability with zero spam tolerance. Bootstrapped this instead of pricier options like FastMail. Thoughts?

https://www.lowcostmail.com

Re: Ask HN: What Are You Working On? (December 2025)

#354
Computing entropies of high-dimensional random vectors for a theoretical neuroscience study. The journey is mostly a repetition of (1) almost giving up because it's completely hopeless, (2) taking a hot shower, (3) realizing there might actually be a path forward, (4) almost giving up because it's completely hopeless.

Re: Ask HN: What Are You Working On? (December 2025)

#355
https://fluxmail.ai

It's an AI-native email client. Launching soon!

My goal is to help people get done with email faster, so that they can get back to doing other stuff. A lot of the features are designed around this goal: unified inbox, AI summarization, AI email drafting, etc.

Some of these are table stakes but I think there's also an opportunity to significantly revamp how email is done in the AI age. Imagine having your own personal assistant that goes through your email and surfaces the highest priority things that you need to know automatically.

Re: Ask HN: What Are You Working On? (December 2025)

#356
Hyperclay: a way to package up HTML files as portable, editable apps that contain their own editable UI. I'm using these simple apps to plan, edit emails, write blog posts, and a lot more. I edit them on my mac and they sync to the web live.

It feels like being able to design my own document format on the fly and display it however I want. It's making it painfully obvious how many editable primitives the web is missing, however.

https://hyperclay.com/

Re: Ask HN: What Are You Working On? (December 2025)

#357
https://colocataires.dev/

Trying to build a small-scale ISP/hosting provider domiciled in Canada. We really want to be able to rent real rack space to enthusiasts who would like to benefit from having stuff in the datacenter but don't want to take on the opportunity cost to get started. It came out of my own desire to have a machine in a DC rack.

This week we've been writing a bunch of "reviews" of self-hostable software since a lot of our friends are curious about this space but don't have a good understanding of how to get started. https://blog.colocataires.dev.

Re: Ask HN: What Are You Working On? (December 2025)

#359
I’ve been working on a TLS proxy/TLS terminator that can handle 3000 TLS handshakes per second (basically an stunnel replacement, but stunnel crashes at under 100 handshakes per second) as a pet project, but I’ve realized that with some polishing this can be really useful.

https://github.com/novotimo/tlsproxy

This is still in development (todo are privilege dropping, in place config reloads, log burst suppression, multiple listen sockets (which paired with the Linux kernel gives free load balancing capabilities), and detailed TLS configurability), but it already matches both nginx and HAProxy’s speed (entirely bottlenecked by OpenSSL crypto by this point) at a tiny fraction of the attack surface and memory footprint (10-15kb per worker process last time I checked).

If anyone wants to take a look, please roast my code :)

Post reply on HN