HNHacker News
TopNewBestAskShowJobs

Franklinjobs617

4 karma · joined August 13, 2025

submissionscomments
Franklinjobs617··on Show HN: YTShortsDL: A Bulk Downloader Built for Shorts Content Repurposing
Thanks for checking out YTShortsDL! I wanted to elaborate on the technical challenge of bulk downloading Shorts.

The complexity isn't just network speed; it’s reliably parsing and queuing media from a single channel or playlist efficiently without hitting rate limits or running into format inconsistencies, which are common when dealing with short-form streaming. We invested heavily in our custom queuing engine to ensure stability during high-concurrency jobs.

Right now, the service is 100% focused on speed and reliability for bulk batching. We see the planned AI features (like the summarization and watermarking tools) as the next major technical hurdle—shifting from a pure download utility to a content optimization engine.

For the HN community: We're running this on minimal infrastructure right now. If you've worked on large-scale media retrieval and queuing systems, I'd love to hear your thoughts on potential performance bottlenecks as we scale. All feedback is welcome!

Franklinjobs617··on Ask HN: What are you working on? (October 2025)
Wow, I can't believe how much progress we've made since I first posted this Ask HN comment a few days ago.

A huge thanks to everyone who shared their deep technical insights—especially the feedback on optimizing TXT output for RAG systems and the architectural notes on high-accuracy transcription. Your input literally saved us weeks of R&D.

I'm incredibly happy to announce that YTVidHub is officially LIVE at https://ytvidhub.com.

The core bulk downloader architecture we discussed here is now implemented. You can paste dozens of YouTube URLs and get a clean, organized ZIP file in minutes. The free tier gives you 5 daily credits for bulk operations.

We’re already focused on the next big challenge: the Pro AI Transcription feature, which will directly address the accuracy concerns raised here.

Please check it out, put the bulk workflow to the test, and let me know if it solves your specific pain points.

Cheers, Franklin

Franklinjobs617··on Show HN: Ambigram Generator: Create words that read the same upside-down
Dude, this feedback is absolutely huge. Seriously.

You totally schooled me on the shadow blocks vs. ambigrams concept. You're 100% right—I’m correcting the messaging right now. That conceptual slip cheapens the whole thing. The 3D stuff is cool, but the 2D visual design is the real puzzle.

And the technical hint? The error-diffusion approach for generating a blurry visual first? That is a game changer. My current substitution method is a dead end, and I knew it. That paper link is now my top reading priority.

Thanks for the technical roadmap, the correction, and the link to the Scott Kim auction. This is the definition of generous community input.

Back to fixing the core algorithm! Cheers.

Franklinjobs617··on Ask HN: What are you working on? (October 2025)
Thanks so much for your kind understanding and further help info.
Franklinjobs617··on Ask HN: What are you working on? (October 2025)
You called it. And honestly, I apologize. That's a fair and painful flag to raise.

Let me be 100% transparent: I'm the human founder, but I've been using a language model to help me quickly synthesize and structure these detailed, technical replies, especially while processing all the fantastic feedback (like your ffmpeg script!) and balancing the day-to-day coding.

The goal wasn't to deceive or automate interaction—it was to ensure I could respond to every point with technical clarity without losing the thread, but I clearly over-optimized the structure and lost the necessary human touch. My mistake.

This is a human talking now, hitting reply directly. Your feedback has been invaluable—truly saving us weeks of R&D—and I would never want you to feel that contribution was wasted on a bot.

We are taking your ffmpeg suggestion seriously for the long video pipeline. I'm hitting the keyboard and doing the coding myself.

Thanks for the brutally honest call-out. I'll stick to 100% human responses going forward.

Franklinjobs617··on Ask HN: What are you working on? (October 2025)
This is absolutely gold, thank you for sharing the exact script!

That specific ffmpeg silenceremove filter is exactly the type of pre-processing step we were debating for handling those massive, lengthy live stream files before they hit the LLM. It's a huge performance bottleneck solver.

We figured ffmpeg would be the way to go, but having your tested parameters (especially the start/stop thresholds) for effective noise removal saves us a massive amount of internal testing time. That's true open-source community value right there.

This confirms that our batch pipeline needs three distinct automated steps:

URL/ID Harvesting (as discussed)

Audio Pre-Processing (using solutions like your ffmpeg setup)

LLM Transcription (for Pro users)

We will aim to make that audio cleaning step abstracted and automated for our users—they won't have to fiddle with parameters; they'll just get a cleaned transcript ready for analysis.

Thanks again for the technical deep dive! This is incredibly helpful for solidifying our architecture.

Franklinjobs617··on Ask HN: What are you working on? (October 2025)
Perfect, that’s great to know. Thank you for clarifying!

Your use case confirms that the plain text (TXT) output needs to be highly optimized—meaning we must ensure the final TXT file is as clean as possible:

No empty lines or spurious formatting from the original subtitle file.

No redundant tags (e.g., speaker or color codes).

Just a single, clean block of text ready to be fed into an LLM or analysis script.

We will prioritize making the TXT output option the "cleanest data" choice for users like yourself who are moving the content directly into analysis or RAG systems. This confirms the value of offering both SRT (for video viewing) and TXT (for data analysis).

Franklinjobs617··on Ask HN: What are you working on? (October 2025)
That is a fantastic point, and you've perfectly articulated the core trade-off we're facing: Accuracy vs. Cost.

You are 100% right. For the serious user (researcher, data analyst, etc.) the lack of an official subtitle is a non-starter. Relying solely on official captions severely limits the available corpus.

The suggestion to use powerful models like Gemini for high-accuracy, custom transcription is excellent, but as you noted, the costs can spiral quickly, especially with bulk processing of long videos.

Here is where we are leaning for the business model:

We are committed to keeping the Bulk Download of all YouTube-provided subtitles free, but we must implement a fair-use limit on the number of requests per user to manage the substantial bandwidth and processing costs.

We plan to introduce a "Pro Transcription" tier for those high-value, high-volume use cases. This premium tier would cover:

Unlimited/High-Volume Bulk Requests.

LLM-Powered Transcription: Access to the high-accuracy models (like the ones you mentioned) with custom context injection, bypassing the "no official subs" problem entirely—and covering the heavy processing costs.

We are currently doing market research on fair pricing for the Pro tier. Your input helps us frame the value proposition immesnely. Thank you for pushing us on this critical commercial decision!

Franklinjobs617··on Ask HN: What are you working on? (October 2025)
This is amazing feedback, thanks for sharing your deep experience with this problem space. You've clearly pushed past the 'download' step into true content analysis.

You've raised two absolutely critical architectural points that we're wrestling with:

Official Subtitles vs. LLM Transcription: You are 100% correct about auto-generated subs being junk. We view official subtitles as the "trusted baseline" when available (especially for major educational channels), but your experience with Gemini confirms that an optimized LLM-based transcription module is non-negotiable for niche, high-value content. We're planning to introduce an optional, higher-accuracy LLM-powered transcription feature to handle those cases where the official subs don't exist, specifically addressing the need to inject custom context (e.g., topic keywords) to improve accuracy on technical jargon.

The Automation Pipeline (RSS/RAG): This is the future. Your RSS-to-Website pipeline is exactly what turns a utility into a Research Engine. We want YTVidHub to be the first mile of that process. The challenges you mentioned—pre-processing long live stream audio—is exactly why our parallel processing architecture needs to be robust enough to handle the audio extraction and cleaning before the LLM call.

I'd be genuinely interested in learning more about your approach to pre-processing the live stream audio to remove pauses and dead air—that’s a huge performance bottleneck we’re trying to optimize. Any high-level insights you can share would be highly appreciated!

Franklinjobs617··on Ask HN: What are you working on? (October 2025)
Wow, thanks for this validation! Hearing from someone who almost built the solution themselves confirms we’re on the right track.

You hit the nail on the head regarding language support.

Mandarin/Multilingual Support: Absolutely, supporting a wide range of languages—especially Mandarin—is a top priority. Since we focus on extracting the official subtitles provided by YouTube, the language support is inherently tied to what the YouTube platform offers. We just need to ensure our system correctly parses and handles those specific Unicode character sets on the backend. We'll make sure CJK (Chinese, Japanese, Korean) languages are handled cleanly from Day 1.

The RAG/Semantic Search Idea: That is an excellent feature suggestion and exactly where I see the tool evolving! Instead of just giving the user a zip file of raw data, the true value is transforming that data into a searchable corpus. The idea of using RAG to search across an entire playlist/channel transcript is something we're actively exploring as a roadmap feature, turning the tool from a downloader into a Research Assistant.

Thanks for the use case and the specific requirements! It helps us prioritize the architecture.

Franklinjobs617··on Ask HN: What are you working on? (October 2025)
That is some fantastic validation, thank you! It’s cool to hear you already vibecoded a solution for this.

You've basically hit on the two main challenges:

Transcription Quality vs. Official Subtitles: The Whisper approach is brilliant for videos without captions, but the downside is potential errors, especially with specialized terminology. YTVidHub's core differentiator is leveraging the official (manual or auto-generated) captions provided by YouTube. When accuracy is crucial (like for research), getting that clean, time-synced file is essential.

The Bulk Challenge (Channel/Playlist Harvesting): You're spot on. We were just discussing that getting a full list of URLs for a channel is the biggest hurdle against API limits.

You actually mentioned the perfect workaround! We tap into that exact yt-dlp capability—passing the channel or playlist link to internally get all the video IDs. That's the most reliable way to create a large batch request. We then take that list of IDs and feed them into our own optimized, parallel extraction system to pull the subtitles only.

It's tricky to keep that pipeline stable against YouTube’s front-end changes, but using that list/channel parsing capability is definitely the right architectural starting point for handling bulk requests gracefully.

Quick question for you: For your analysis, is the SRT timestamp structure important (e.g., for aligning data), or would a plain TXT file suffice? We're optimizing the output options now and your use case is highly relevant.

Good luck with your script development! Let me know if you run into any other interesting architectural issues.

Franklinjobs617··on Ask HN: What are you working on? (October 2025)
I’m currently building YTVidHub—a tool that focuses on solving a very specific, repetitive workflow pain for researchers and content analysts.

The Pain Point: If you are analyzing a large YouTube channel (e.g., for language study, competitive analysis, or data modeling), you often need the subtitle files for 50, 100, or more videos. The current process is agonizing: copy-paste URL, click, download, repeat dozens of times. It's a massive time sink.

My Solution: YTVidHub is designed around bulk processing. The core feature is a clean interface where you can paste dozens of YouTube URLs at once, and the system intelligently extracts all available subtitles (including auto-generated ones) and packages them into a single, organized ZIP file for one-click download.

Target Users: Academic researchers needing data sets, content creators doing competitive keyword analysis, and language learners building large vocabulary corpora.

The architecture challenge right now is optimizing the backend queuing system for high-volume, concurrent requests to ensure we can handle large batches quickly and reliably without hitting rate limits.

It's still pre-launch, but I'd love any feedback on this specific problem space. Is this a pain point you've encountered? What's your current workaround?

Franklinjobs617··on Show HN: Image-to-Dot-to-Dot Generator. Print Custom Puzzles
I’m the maker of ConnectTheDotsPrintable. Thanks for checking it out!

A common question I anticipated was the complexity. It’s tricky to balance enough detail for the final image to be recognizable, while keeping the dot count manageable for a fun puzzle. The contour simplification algorithm handles this by focusing on areas of high contrast and ignoring fine texture noise.

A technical detail: I spent significant time optimizing the dot sequencing step. It’s not simply linear. For complex shapes, the algorithm dynamically determines the shortest Eulerian path that touches all necessary contour points, ensuring the final numbered puzzle remains logical and solvable for the user.

I know the printable market is saturated, but I believe the focus on hyper-personalization is the necessary differentiator. I'm especially interested in feedback on the algorithm's performance on photos versus line art. Let me know what you think!

Franklinjobs617··on Show HN: Ambigram Generator: Create words that read the same upside-down
Hello Hacker News!

I'm the creator of Ambigram Generator (https://www.ambigramgenerator.me/). It generates rotationally symmetrical ambigrams—words or phrases that read the same when inverted (rotated 180 degrees).

The Engineering Deep Dive: From SVG to 3D Print While the 2D generation relies on a complex rule-based dictionary for character pairing and SVG path merging (a significant combinatorial challenge in itself), the most interesting part for makers and engineers is the 3D functionality.

1. 3D Model Generation and WebGL: Once the optimal 2D ambigram is generated, we extrude the 2D SVG vector path into a 3D mesh. This involves:

Mesh Extrusion: Using Three.js to handle the complex geometry of the merged character paths. We implemented custom logic to ensure clean, manifold geometry, crucial for the next step.

Real-time Preview: The 3D view is rendered using WebGL, allowing users to interactively rotate the model to confirm the ambigram symmetry from all angles. We also include a feature to generate a looping GIF preview that cycles through angles, providing an immediate, shareable demonstration of the effect.

2. The Bridge to the Physical World: STL Export The generator's core utility is the ability to export the resulting 3D model as an STL file. This transforms the generated word into a physical object ready for 3D printing.

Key Challenge: STL files require closed, watertight meshes (manifold geometry). Any flaws in the initial SVG or the extrusion process (like overlapping faces or open edges) will result in a non-printable file. We spent considerable time tuning the extrusion depth and simplifying the mesh to produce robust, validated STL files.

Open Questions for the Makers/3D Community I'd appreciate any feedback on the 3D pipeline:

Slicing Optimization: Have any makers here found particular settings (e.g., specific wall thickness or infill patterns) that work best for printing these highly detailed and symmetrical text models?

WebAssembly for Geometry: Currently, all geometry processing is client-side in JS. Would integrating a C++/Rust geometry library via WebAssembly be a worthwhile effort to speed up complex mesh generation before export?

Try generating an ambigram and check out the 3D preview and STL export feature!