Show HN: Image3d AI-One interface for multiple image to 3D models
I built image3D AI to make it easier to try and compare different image to 3d models in one place.
cairnechou
Show HN: Automated pipeline to generate music videos from audio files
https://www.getlyricvideo.com/
It’s a "black box" flow: upload audio -> Whisper (sync) -> Gemini (director/script) -> Veo/Seedance (synthesis). It handles everything from LRC generation to final rendering. Supports Realistic, Cartoon, and Abstract styles. Would love to hear your feedback on the shot consistency.
Re:Questions for Cloudflare
on Wednesday November 19, 2025 @08:32PM (#45987696)
"Armchair quarterbacking" is spot on.
The author asks for a deep, system-theoretic analysis... immediately after the incident. That's just not how reality works.
When the house is on fire, you put it out and write a quick "the wiring was bad" report so everyone calms down. You don't write a PhD thesis on electrical engineering standards within 24 hours. The deep feedback-loop analysis happens weeks later, usually internally.
Re:The first-ever protocol for websites and AI browsers to cooperate
on Tuesday November 18, 2025 @12:17AM (#45961656)
You're totally right, "protocol" is way too heavy.
A simple convention like aidata.json is perfect. That's the "win-win" I was looking for: the site gets to clearly offer what it wants the AI to see, and the AI gets clean data instead of having to guess at brittle HTML.
aidata.json is a great name for it.
Re:The first-ever protocol for websites and AI browsers to cooperate
on Monday November 17, 2025 @10:14PM (#45961002)
This is a crucial conversation to start. As someone building in the AI/SaaS space, the current "HTML scraping" layer is the single most brittle and unreliable part of any agentic workflow. An agent breaks the moment a developer changes a CSS class.
A common protocol—like a robots.txt but for AI agents—feels like the inevitable and necessary next step. We need a way for sites to "semantically" declare their functions and content to a machine.
This raises a huge game-theory question, though: What is the website's incentive to adopt this?
It's a "cooperate or defect" dilemma. If a site doesn't cooperate, the AI agent will just scrape it (badly). If it does cooperate, it makes it easier for the AI agent to summarize its content and potentially bypass its ad/conversion funnels.
I'm curious what the authors think the "win-win" is here for the websites themselves.
Re:Ask HN: Mac App Store worth it for a $0.99 app?
on Wednesday November 12, 2025 @02:41AM (#45897353)
You're targeting "music/video/content producers," who are professionals.
In this market, a $0.99 price tag is a liability, not an asset. It signals "hobbyist toy," "abandonware," or "data-harvesting scam." Professionals are used to paying for tools that solve a problem, and they will happily pay $9.99 or $19.99 for a "1 trick pony" if it saves them 10 minutes of frustration just once.
Don't price it based on its "simplicity." Price it based on the value it provides to your niche audience. You'll need 100 sales at $0.99 just to break even on the fee. You'd only need 10 sales at $9.99. The latter is a much more realistic validation signal.