Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
smoores
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
1.
▲
by
smoores
17d ago
Viterbi and Needleman-Wunsch are essentially the same algorithm, developed in parallel for two different domains! The Viterbi formulation of the algorithm is the one usually applied to signal decoding, since that's what it was original
2.
▲
by
smoores
17d ago
I'll post again when we release the v3 apps — even in alpha, they're really awesome, I think they blow the Kindle app out of the water!
3.
▲
by
smoores
17d ago
Oh, cool! Yeah that seems like a good application. The current Storyteller alignment algorithm actually does do just that! We use Whisper to transcribe the audio to text, and then use error-align[1] to align on the text. There are a few dis
4.
▲
by
smoores
17d ago
You gotta give me more than that haha. It's not readable in what way?
5.
▲
by
smoores
17d ago
Well, first of all, lots of people specifically do use this because they have print disabilities or neurodivergence that makes it challenging to read long stretches of text. Also, disability isn't binary? Some people have an easier tim
6.
▲
by
smoores
17d ago
My guess is, like many accessibility tools, it will vary by person! The Storyteller apps don't actually support this multi-level granularity demostrated in the demo here — until this iteration of the alignment algorithm, the timing was
7.
▲
by
smoores
17d ago
Sure! Some people have print disabilities like dyslexia and neurodivergence that makes reading text for an entire novel-length book challenging. Other people are perfectly competent print readers, but find that they enjoy having their book
8.
▲
by
smoores
17d ago
Hm, I don't know what you're referring to. Is the text too small for you? I wrote the blog post on FF for Linux and FF for Android, and I didn't need to zoom in to review it, though some of the graphics do definitely end up w
9.
▲
by
smoores
18d ago
Almost everyone who uses the readaloud features in Storyteller speeds up the audio playback quite a bit, often 2-3x, so that it matches their reading speed better. The Storyteller apps let you set different playback speeds for pure audio pl
10.
▲
by
smoores
18d ago
You can use a KOReader plugin, https://github.com/stradichenko/audiobook.koplugin , which has work-in-progress support for Media Overlays (the EPUB spec that Storyteller uses for readaloud)!
11.
▲
by
smoores
18d ago
... Okay!
12.
▲
by
smoores
18d ago
There are two koreader plugins: 1. StorytellerSync ( https://github.com/Sirozha1337/storytellersync.koplugin ), which syncs your KOReader progress directly to your Storyteller server 2. Audiobook ( https://gith
13.
▲
by
smoores
18d ago
Thanks! We're improving it all the time — we're working on big new releases ("v3") for the web app and mobile apps. There's a Discord server linked in the docs if you ever need any help out want to chat!
14.
▲
by
smoores
18d ago
That is actually the exact use case that I originally built Storyteller for! I wanted to listen to my books on long runs, and then switch to reading when I got back. The Storyteller mobile apps have great support for this, I think. They hav
15.
▲
Automating Immersive Reading
(smoores.dev)
127 points
by
smoores
18d ago
|
49 comments
16.
▲
by
smoores
18d ago
I took a week of from work recently to reimplement Storyteller's forced alignment algorithm. Storyteller[1] is an open source, self hosted platform for creating, managing, and reading/listening to "readaloud" books — boo
17.
▲
Making React ProseMirror Fast
(handlewithcare.dev)
2 points
by
smoores
6mo ago
|
1 comments
18.
▲
by
smoores
6mo ago
Just finished a new blog post about React ProseMirror. Happy to chat if anyone has questions, hope you enjoy!
19.
▲
We're building a better rich text editing toolkit
(handlewithcare.dev)
5 points
by
smoores
6mo ago
|
2 comments
20.
▲
by
smoores
6mo ago
Hey folks! Handle with Care is a software collective that builds and maintains open source rich text editing libraries, including React ProseMirror [1]. We all came from The New York Times’ content management system team, and we spend a lot
21.
▲
Using React Transitions for low priority text editor updates
(handlewithcare.dev)
2 points
by
smoores
9mo ago
|
1 comments
22.
▲
by
smoores
9mo ago
Howdy! React ProseMirror maintainer here. Our collective has been helping out a client with migrating their existing text editor to use React ProseMirror from @tiptap/react. They had a very complex system for deferring updates to their
23.
▲
by
smoores
1y ago
I found myself recently needing to implement the HTTP range request protocol in order to support video elements in Safari. It took some effort, so I figured I would document what I learned in case it’s useful for anyone else!
24.
▲
by
smoores
2y ago
Thank you for the kind words, I really appreciate it! I'm glad you enjoyed it
25.
▲
Why I rebuilt ProseMirror's renderer in React
(smoores.dev)
4 points
by
smoores
2y ago
|
3 comments
26.
▲
by
smoores
2y ago
Howdy folks. This is a somewhat long (… sorry!) deep dive into several years’ worth of work that started when I was a staff engineer at The New York Times and has followed me into open source development in the years since I left to do my o
27.
▲
by
smoores
2y ago
Thanks! Looking forward to your feedback!
28.
▲
by
smoores
2y ago
Readium is fantastic, and Storyteller uses it basically whenever possible. But Readium is exclusively for reading EPUB contents, and doesn’t have any support for modifying or creating them, which is the primary purpose of this library!
29.
▲
by
smoores
2y ago
Thanks, yeah I agree. The vast majority of the code in this library lives in a single class definition. Is it possible to move the implementations into separate files? Totally. Would that make the codebase more legible? I think at the momen
30.
▲
by
smoores
2y ago
This is like... comically hard to express succinctly haha. We've been having several conversations about how to explain it quickly to new folks. I like the phrase that the Readium folks use, "guided narration", but I don'
More ›