> My main motivation to build this is that I read faster than I listen

Yes! However occasionally I find it useful to refer to the original video (especially when I want to share a video at a certain timestamp.) Searchable transcripts are a great way to navigate a video if they have links that jump to the relevant timestamp in the video.

So I designed a special file format and web app based on oTranscribe + Markdown:

- https://raw.githubusercontent.com/Leftium/oTranscribe/refs/h...

- https://otranscribe.netlify.app/?vsl=definedefine

I made a tool to convert YouTube SBV/TTML files; it should be possible to add support for one of your output formats: https://github.com/Leftium/otrgen

---

There was a similar show HN[1] that opened my eyes to OpenAI Whisper, however your python script provides a better starting point than a bash script. I'll probably reference both projects when I make my own projects (including a beat-aware YouTube player that needs the audio data for beat-detection analysis.)

[1]: https://hw.leftium.com/#/item/41473379

It seems a lot of thought was put into the design of LogTape. I may integrate my logging tool with LogTape. My tool needs the callsite, so I don't think I can just write a LogTape sink; I think it would also have to wrap/extend LogTape itself.

---

I built a DX-focused logging library on top of debug-js. Notable features of https://github.com/Leftium/gg:

- Automatic namespaces based on calling function + path to source filename/path.

- Can be inserted into the middle of expressions.

- Can output a link that opens the file in your editor/IDE of choice.

- Simple to disable

- Diagnostics/hints to help with installation/configuration

---

I was surprised by the amount of logs already being output (by Vite) when I simply added https://github.com/debug-js/debug to my project.

Fortunately, debug-js output is very simple to filter via ENV and/or localStorage.debug

---

What I look for in a logging library (with more focus on dev/debugging than production):

- Easy to add new logs.

- Easy to identify the location of the code that triggered the log. I noticed a lot of my logging was simply to indicate the start and maybe end of a function call. If needed, I might add additional logs between these.

- Easy to surgically disable/filter groups of logs. Should be easier than commenting/uncommenting calls to logger. Otherwise I end up with lots of uninteresting log chatter (or I delete log statements, only to add them again later...)

https://www.recurse.com/hire

I haven't used them, but read the testimonials:

> ...sent us two profiles of solid candidates, one of which we hired!

> ...other recruiters sent like 50 CVs and we couldn't find anyone, and then RC sends a single candidate and we hired him.

How they do it: the Recurse Center puts more thought into collecting a small set of excellent candidates, then puts even more thought into matching them with employers.

Ah, what happened was the OP copied the text from his previous submission. So the original working link got truncated.

https://news.ycombinator.com/item?id=44207055

A feature I would love to see in a YouTube player: better transcript view

- Single click to open transcript

- Transcript not crammed into tiny window in corner

- Often I use the transcript as a navigation tool when (re)viewing a long video. Especially when I want to share a specific part of a video.

---

And I found a bug in SkipCut when clicking a FAQ:

- If the video was started (then paused) opening a FAQ starts the video (audio).

- Possibly related? often the browser jumps down the page, so the FAQ I clicked is not visible unless I scroll back up. (Or maybe it is scrolling the FAQ to near the top of the viewport? It's disorienting. If intentional, a smooth scroll animation may help.)