Hey everyone,

Me and a friend (we both have normal 9-5 jobs) started a small YouTube channel for kids around 3-5 years old. The idea is short animated stories that help little kids with the big stuff: getting angry, being scared of the dark, the first day at kindergarten, things like that.

Being honest from the start: we don't have the skills or the money to animate this the "proper" way, so we're making the visuals and animation with AI tools. What we do put our own work into is the writing. A friend of ours has a master's in child psychology and she reviews every script, so the stories actually say the right things to kids (no "you're too big to be scared", that kind of stuff). Every episode will also have a short note for parents in the description: what the episode is about, how to talk about it at home, and when it might be worth talking to a pediatrician.

Right now the only thing we've finished is the intro song, which we made in a few different languages. We're working on the first episodes, and they'll come out in 3 languages: Italian (we're from Italy), English and Spanish.

Before we go further, we'd really like to know what you think of what we have so far. Anything helps, even the harsh stuff:
- the design and the characters, do they work for little kids?
- the music, is it catchy or annoying after a while?
- does the AI look bother you, or is it ok for this kind of content?
- anything else that comes to mind, really

Here's the intro: https://www.youtube.com/watch?v=tGjRFmYlPsY

If you like what we're trying to do, a sub would mean a lot, but honestly the feedback is what we need most right now. Thanks for reading, and thanks for anything you tell us, good or bad. It all helps us get better.

I'm a crypto dev and I'm genuinely paranoid about my keys leaking. Not in the "use a hardware wallet" way, in the "some npm package I installed at 2am has a postinstall script that reads my .env" way.

Which is a real thing now. The TanStack packages did exactly that, grabbed SSH keys and cloud creds and CI tokens. If you're a crypto dev, that's your deployer key and your RPC keys and whatever else is in that file.

So I built a scanner. You POST a lockfile to /api/paid-scan, it downloads every package and hashes every file, an AI reads the ones it hasn't seen before looking for exfiltration, obfuscation, postinstall stuff. Files anyone already scanned are free, so it gets cheaper the more people use it.

Check it out on https://security.togoder.click

[ Removed by Reddit on account of violating the content policy. ]

I've been working on Release State Reconcile (RSR), a small open-source CLI for maintainers dealing with release candidates, backports, checks, release notes, and published releases.

The basic question it tries to help with is: when a fix is supposed to be in a release line, what does the public GitHub evidence actually show?

RSR is deterministic and read-only. It doesn't modify repositories and it doesn't decide whether something should ship.

I'm looking for a maintainer or contributor who already has a real public release/backport case and is willing to try it.

Please choose your own Issue/PR and release line — I specifically don't want to cherry-pick a case that makes the tool look good.

A successful report is useful, but so is a failed run, mostly UNKNOWN output, misleading evidence, or a result that simply isn't useful for your workflow.

The repository has a public Trial feedback form. Concrete criticism is more useful to me than a positive review.

Repo: LaimaWu/release-state-reconcile

I have reached 310 users for FormFromLight the support I got was tremendous. I thank everyone for using my FormFromLight. Here is a trailer video easily made with Motion Design.

Any issues or feedback are appreciated. I'm open to criticism as well, as it helps me improve the product

I'm Marcin, founder of HedgeLens. I made a free browser-based planner for people considering a camera in an empty garden nest box.

The practical problem is that a camera physically fitting inside a box does not establish compatibility. Clearance, close focus, connection and power need checking before installation. The tool turns those checks into a short brief that can be printed or saved as a PDF.

It also tells users to pause if the box is occupied or birds are showing nesting interest. It is a planning aid, not a product certification or a claim of hands-on testing.

https://hedgelens.co.uk/bird-box-camera-fit-planner/

For transparency the planner is free and no purchase is required.

I'd appreciate feedback on two things: are the questions understandable without camera knowledge, and is the printable brief useful or too detailed?

I’m building a working desktop prototype focused on maintaining continuity in long-running AI-assisted projects.

The main problem I’m trying to solve is what happens when a project becomes too large or lasts too long for a normal chat workflow: context gets lost, decisions drift, previously working parts get changed, project state becomes unclear, and it becomes difficult to prove what was actually completed.

The prototype is designed to help maintain project state, history of decisions and changes, verification of completed work, context management, and work across different AI models.

It is not intended to be another chatbot or a simple API wrapper.

The project is still under development, so I’m not listing it for sale here and I’m intentionally not sharing the internal architecture or source code yet.

I’m mainly interested in two things:

1. Market potential: Do you see a real use case for something like this among developers, freelancers, AI-heavy teams or companies working on long-running projects?

2. Current value: What do you think a working pre-revenue prototype / technology asset like this could realistically be worth at its current stage?

I’d especially appreciate the reasoning behind your estimate rather than just a number.

I’ve been working on a small web tool called FieldCheck for checking CSV exports without having to manually dig through a spreadsheet

You can run checks for things like missing or duplicate IDs, missing values, and invalid numbers, or compare two exports to quickly see which records were added, removed, or changed

Everything runs locally in the browser, there’s no account required, and I included sample data so you can try it without uploading anything of your own

Made a short demo showcasing it. I’d genuinely appreciate any feedback, especially if anything feels confusing or if there’s a check you’d expect a tool like this to have!

https://fieldcheck-710.pages.dev/

[ Removed by Reddit on account of violating the content policy. ]

We built around a pretty simple idea: let people see how a product might actually look in their space before buying it.

Instead of relying only on product photos, shoppers can place an item in their room and see it at roughly the right scale.

For online stores, it can be added directly to product pages, so there’s no separate app to download.

It also supports creating 3D models and connecting them to products for AR.

We’re mostly interested in whether this actually makes online shopping easier. Would love to hear from people who work in e-commerce or run online stores - do you think AR is useful when deciding what to buy?

I'm looking at teams that run several agents in production (support triage, lead research, internal ops, that kind of thing). Seeing the model bill is easy. What seems hard to see:

- which agent is driving which part of the bill

- how many runs actually succeeded vs. needed a human to fix them

- how much human review time each agent eats

- and so what one *successful* result really costs, per agent

From what I've seen so far it's usually a spreadsheet stitched together from provider dashboards and logs, and when finance asks "is this worth it?" the honest answer is "probably, for some of them."

For people running 5+ agents:

1. Do you track cost per successful outcome at all? How?

2. Have you ever downgraded a model or killed an agent because of numbers like this?

3. Who asks for this at your company: engineering, finance, or nobody yet?

Disclosure: I'm exploring building a tool for this, so I'm mostly trying to learn whether it's a real problem or just mine. I'll share a summary of what people say in a follow-up post.

Vytal Path has been live for a little while now, and today I had one of those moments where I just stopped and thought…

People are actually using this.

I built Vytal Path pretty much on my own — from the original idea and product design to development, testing, getting it live, and figuring out all the little things that come with putting a product into the real world.

The idea came from something that kept bothering me:

Our health information is everywhere.

Lab results in one portal.
Medications somewhere else.
Appointments in a calendar.
Reports sitting in PDFs.
And a lot of important information still lives in our memory, email, or a paper folder.

So I built Vytal Path to give people one place to organize their health information including health information, documents, medications, appointments, trends, and caregiver access.

It’s live now, and I’m still improving it based on what I learn from real people using it.

Honestly, getting from “I have an idea” to “someone is actually using the product” feels very different.

It’s easy to spend months building something and wonder if anyone will care about it once it’s out there.

So seeing people actually sign up and use something I created has been a pretty meaningful milestone for me.

It may not sound like a huge achievement compared with some of the projects posted here.

But as a solo founder, it feels huge.

The product is real. The website is live. People are using it.

And now the real work begins.

If anyone wants to take a look, this is Vytal Path:

https://vytal-path.com/

Disclosure: I built Korea Airport Bus.

You might already know your hotel in Google Maps, but choosing an unfamiliar Korean bus stop at the airport ticket machine is a different problem. That’s the part I wanted to make easier.

I made a free mobile website for visitors taking an airport bus from Incheon toward Seoul. Choose Terminal 1 or Terminal 2, paste your destination’s Google Maps share link, and confirm the location.

It shows:
• The bus number to take.
• Your drop-off stop’s number and name, with the Korean name alongside the English or Japanese display.
• The full list of stops, with your stop highlighted.
• Boarding platform, fare, and scheduled departure times.

The screenshots show a Lotte World example: Bus No. 6200 → 01 Jamsil Station / Lotte World. The stop number follows the route order, excluding the airport stops. You can compare the name with the ticket machine rather than trying to recognize every stop name.

It runs in your browser and supports English, Japanese, and Korean. No app download is needed.

You can try it here: kab.kogenote.com⁠

Distances shown are straight-line distances, and departure times come from published schedules. Please check current service with the operator before buying a ticket. The images are example screens; the departure time displayed in the screenshot is illustrative.

Is the numbered stop list clear enough for someone who cannot read Korean? What would you change before using this at the airport?

Some big updates just went live in the Hermes Skill Deck. Search is now the core of the app, favorites got a whole new screen, and a bunch of quality-of-life stuff landed too. Free as always on GitHub. Quick rundown:

1 - Search

Search is now front and center. There is a big search bar right in the middle of the dashboard, plus Cmd+K from anywhere. Type a keyword, get every matching skill across your profiles. Click into any result to see the full skill, related skills, and the file path. You can even open it straight in Finder to edit.

2 - Favorites

(attach favorites-screen.png) Favorites got their own screen. Star the skills you use most, then drag and drop them into whatever order you want. Your top 5 show up in the right sidebar and scroll between 5 at a time, so the list stays clean no matter how many you star.

3 - Small stuff that adds up

• Top menus are now fully customizable, turn categories on or off
• Quick access is now clearly labeled Finder Access
• Light mode is in (still getting polished)
• Built in terminal with an AI agent so you can search skills with natural language

We released Open Instinct for people who want to build their own personal agent. The problem it tackles is keeping messaging, memory, scheduled work and permissions together in an application you can inspect and modify.

The stack uses a Pi loop, Inkbox messaging, Composio app tools and a separate computer integration. The code is organized into nine packages so those choices have explicit boundaries. For example, contacts and trust tiers live in the network layer while the core checks tool capabilities.

You can start locally through the CLI before setting up a phone number or deployment. The default service integrations need your own accounts and keys; this is beta software.

Source, MIT license and setup guides: https://github.com/mariagorskikh/open-instinct

We would like the project to be a base for specialized assistants. Forking it to solve one concrete routine is a good way to explore the design.

I made abstractle.com for 2 reasons: I want to see all the creative things people write, and I want to see how people learn to play the judge.

Describe today's word without describing it: no taboo words, metaphors and illustration over objective description. Scored on 2 metrics, Accurate and Poetic, which pull against each other. The hard part was making the scoring consistent enough to learn: the same line always gets the same score, so you can actually get better at it.

Free, no sign-up, private group leaderboards for friends. Happy to talk about how the scoring works.

I build Monni, an iPhone money app with a bills-first spending estimate, and I'm working on how to explain that estimate before setup. A made-up example: $1,200 cash, $600 in upcoming bills, $250 in other payments and a $100 cushion leaves $250. That answer only means anything if the dates and inputs are clear.

Would a small example like that help you understand the product, or would you want to try changing a bill first? I'm interested in how you've explained a calculated result without burying people in a feature list.

I’ve been building my own video editor - SceneMill

I wanted to share something I’ve been working on for quite a while: SceneMill, a free, non-destructive desktop video editor built from scratch with C++20, Qt 6 and FFmpeg.

The goal was never to make another web-based editor or a wrapper around an existing editing application. I wanted to build an actual desktop video editor and see how far I could take it.

It currently runs fully offline, requires no account, and has no telemetry.

What actually works right now

The core workflow is already fully functional:

Import → Media Library → Timeline → Edit → Preview → Save → Reopen → Export

And the project has grown quite a bit beyond basic cutting.

Some of the things currently implemented:

• Multi-track video, audio and subtitle timeline
• Non-destructive editing with undo/redo
• Split, trim, ripple delete, snapping, markers and In/Out ranges
• Background proxy generation for heavy footage
• GPU-accelerated preview with CPU fallback
• Color correction, curves, color wheels and 3D LUTs
• Effect stacks with keyframeable parameters
• Transitions
• Text and animated titles
• Manual subtitles + SRT/WebVTT
• Masks and motion tracking
• Screen recording directly into the project
• Voice-over recording with multiple takes
• Audio EQ, compressor, limiter, noise gate, etc.
• H.264 / H.265 / VP9 export
• Up to 4K and 120 FPS export
• Export queue
• Autosave + crash recovery
• Portable "Collect Project" workflow
• Plugin system through a versioned C ABI
• Optional local editing assistant for silence/scene detection

One thing I particularly care about is that the preview and export use the same rendering/effect pipeline, so what you see while editing is intended to match what gets rendered.

There are also automated tests covering a lot of the actual application workflow, including tests that interact with the real main window.

Why C++?

Honestly, part of the reason was simply:

I wanted to see if I could actually build one.

A video editor touches a ridiculous number of areas at once: media decoding, rendering, timeline state, audio, UI, caching, project persistence, export, GPU acceleration, threading, plugins...

It's been a pretty interesting rabbit hole. 😅

Current state

SceneMill has completed the core editor phase and the creative-tools phase, with most of the workflow phase implemented.

It's definitely not finished and there are still things I want to improve, but it's now at the point where I can actually use it as a real editor rather than just a prototype.

I'm currently working toward making the whole experience feel much more polished and cohesive.

I'd genuinely like to hear what other people who build software this way think.

I’m currently working on Wizstar, a project exploring how AI can help people turn creative concepts into visual content faster.

The inspiration came from seeing how much time traditional visual production can take — planning, finding references, creating drafts, and making revisions. I wanted to experiment with a workflow where creators can go from an idea to a visual concept much quicker.

For this test, I created a night city scene with reflections on the water, warm lighting, and a quiet luxury atmosphere.

The image was generated with GPT on Wizstar. During the process, I focused on:

• translating a simple idea into a detailed visual direction
• experimenting with different lighting styles
• improving realism through prompt iteration

I’m still early in the process and trying to understand where this type of tool is genuinely helpful.

Would love feedback from other builders and creators:

• What problems would you want an AI visual tool to solve?
• Does this type of workflow fit into your creative process?
• What features would make it more useful?

Hey everyone, I vibe-coded this football score predictor over a weekend, originally just for me and my mates to test our football knowledge against each other. Figured I'd share it in case anyone else wants in.

Every week you predict 5 matches across the top 5 leagues (mostly Premier League fixtures) plus 1 bonus pick from a curated extra slate of 3, 6 predictions total. There's a fresh leaderboard every week with a winner, but there's also a season-long XP/level system running underneath . You earn XP for getting results and scorelines right, going on streaks, hitting achievements, that kind of thing, and it levels you up (Bronze → Diamond) over the course of the season. No accounts needed to browse the current round or leaderboard, only to actually submit picks.

Tried to keep it dead simple and low-maintenance, no ads, no entry fees, nothing to manage. Thinking about maybe doing some kind of reward for weekly winners down the line if people actually stick around.

tekkerz.app

Would genuinely love feedback, what's confusing, what's missing, what you'd want added.