I also created and maintain a Russian "newspeak" dictionary: https://github.com/alamzin/az/
Ask HN: What Are You Working On? (Nov 2025)
641–650 of 1001 posts
Re: Ask HN: What Are You Working On? (Nov 2025)
#642Re: Ask HN: What Are You Working On? (Nov 2025)
#643As a second-time founder, I've watched the SaaS boom create an ocean of best-of-breed tools. Each solving one slice of the problem. One solving it end-to-end.
Now every company runs on a patchwork of apps, APIs, and workflow hacks just to keep customer context alive. It's insane how normalized that's become.
RootCX starts from the opposite premise: the customer is the core, not the app. Everything: CRM, support, billing, workflows, AI, ... plugs into one shared customer base. Less juggling tools, more actually running the business.
Re: Ask HN: What Are You Working On? (Nov 2025)
#644Idea came from one of my clients, where they wanted to use AI agents throughout the organization but at that moment there was no centralized governance or security concepts. This pulls everything at one place and tries to solve the security concept with per-user credentials, which can be provided out-of-band through the MCP protocol (generated a one-time link end-user can use to sign in to the underlying MCP server with OAuth or provide API key)
Re: Ask HN: What Are You Working On? (Nov 2025)
#645[1] - https://highlights.email
Re: Ask HN: What Are You Working On? (Nov 2025)
#646I was tired of repeat, sponsored, and "safe" music suggestions from Spotify, so I built a discovery engine that puts the control back in the user's hands.
The core idea is simple: You define a "Discovery Model" with explicit constraints (specific genres, release years, track popularity, etc.). The app then uses this blueprint to source tracks.
The results are fresh for two reasons:
- "Known" Track filtering: Excludes all songs saved in your library and recent listening history.
- Active Curation: Uses your custom model, not a vague, opaque algorithm.
It’s built with a local-first mentality and a focus on privacy. No black-box AI "vibe" mixes, just pure, objective discovery based on your criteria.
Hope ya'll find some new gems!
Re: Ask HN: What Are You Working On? (Nov 2025)
#647Re: Ask HN: What Are You Working On? (Nov 2025)
#648Why? For learning and fun.
The next step is to debug kernel logs with uart.
Re: Ask HN: What Are You Working On? (Nov 2025)
#649Recently it hit v2.0 spec conformance. 3.0 is next on the roadmap. (I'm executing it against the upstream spec test suite.)
My aim is probably not for it to become a highly-performant decoder for use in production environments, but rather one that can be used for educational purposes and/or debugging issues with existing modules. That's why I decided not to offer a streaming API, and why I'll be focusing on things like good errors, good code docs etc.
P.S. I'm new to the language so any feedback is more than welcome.