We spent three months building an open-source, local-first AI work journal that captures daily activity and turns it into clear timelines, worklogs, and updates. Yesterday, the Product Hunt community helped it reach the top position.
Thank you to everyone who supported the launch, shared their experience, left a comment, or recommended Meridian to someone else. The launch is over, but the work continues. We are reviewing what people shared and improving the onboarding, activity timeline, and drafted updates.
If you have tried Meridian, we would value hearing honestly what worked well and what still feels unclear. GitHub: https://github.com/Meridiona/mer...
I noticed a lot of gamers struggle figuring out their real mouse feel when switching between games, or just don't have an easy way to check things without digging through manufacturer software. So I built a simple tool to help with that.
It lets you check your current settings, get a comparable number to match your setup across different games, and convert your feel when switching titles all in one simple place.
It's free to use, no complicated setup needed. Feel free to try it out and let me know what you'd like added I'll be listening to all feedback!
Hey everyone we've been building Kumoo, an AI retouching + batch editing tool for photographers and studios, and wanted to share the feature we're most excited about: AI Color Transfer.
The idea: you find a photo a movie still, someone else's edit, a Pinterest mood board pic, whatever and Kumoo lets you "steal" its color grading and apply it straight to your own RAW photos. No manual curve-matching, no guessing at LUTs. A few clicks and your photo has that vibe.
Beyond that, Kumoo also does:
Auto Portrait retouching for different skin tones(Dodge&burn, remove blemishes & wrinkles, body reshape, remove glasses glare, add makeups, teeth whitening, tattoo removal etc.)
AI auto-grading for fast first-passes
Tethered shooting (shoot + review live)
Batch editing for high-volume studio work
Background clean-up
Most of the standard retouching toolkit, but built to be faster than the usual workflow
I've been thinking about something that doesn't get discussed enough in gaming:
Blind gamers don't just need accessible games. They need accessible communities.
A lot of gaming communities are built around platforms that can be difficult to navigate with screen readers or aren't designed with blind and visually impaired users in mind.
And even when someone finds an accessible game, there's another question:
Do you actually enjoy shopping for clothes, or do you mostly find it overwhelming? Too many options hamper your creativity?So I built Ellise which is an AI shopping app for style-conscious and cost-conscious people.You can create a complete outfit, try it on virtually, and then shop the pieces across brands.You can also upload your wardrobe and create new outfits from clothes you already own.Would you use something like this?If yes, then check it out App Store and Play StoreAlso checkout the website at ellise.ai
I rebuilt Code Factory 0.40 around a simple concern: AI-generated tests can look convincing without proving much.
This 45-second walkthrough shows the current flow: take an outcome, fuzzy PRD, or risky diff; make the gap in evidence visible; decide what a human should check next.
It stays local. It does not upload source, call a model, or make release decisions.
One thing I've been thinking about while working on FixerFlip is that investors probably spend too much time analyzing opportunities they should have rejected earlier.
Sometimes it's not about finding the perfect deal.
We usually discover extraordinary people after we already know how the story ends.
Steve Jobs is the guy who launched the Macintosh, returned to Apple, introduced the iPod, pulled an iPhone out of his pocket, and helped change technology forever.
I've been noticing a pattern in dev communities lately. Someone builds their first LLM-powered app, ships it, and a week later they're asking why their OpenAI bill spiked or why their key stopped working. Nine times out of ten it's because the key was sitting in the codebase or a committed .env file.
Nobody warns new builders about this especially people coming in through Vibecoding who are moving fast and just want to ship.
I built API Locker (apilocker.app) to solve this. You store your keys in the vault, get a proxy token back, and your code only ever touches the token. You can rotate it anytime without changing your codebase. It's completely free, unlimited usage, and works via web, CLI, IDE extensions for VS Code and Cursor, and MCP tools for AI-native workflows.
Curious have you ever had a key exposed? How are you currently handling secrets management in your projects?
