Congrats on the impressive project! Sharing structs between the frontend and backend sounds very helpful. I've experienced the advantage of shared FE and BE code in JS/TS projects, and it’s definitely valuable.
What led you to choose Leptos for the frontend besides the shared code advantage?
That's awesome! Reaching the point where subscribers cover costs is a huge milestone. Rust's reliability making it easy to revisit projects is a big plus. How do you find Rocket and Actix compared to Axum? Why Tera instead of Askama? Would love to hear your take!
Thanks for the feedback! I'm glad to hear you find the notification idea useful. I'm considering displaying the current backlog and estimated completion times as you propose.
How would you expect to get an understanding of the backlog? Would a dedicated page for the entire backlog be helpful, or would you prefer to see which episodes are being transcribed on each podcast page?
Any insights on what would be most helpful for you would be greatly appreciated!
Thanks for the motivation! I completely agree - using Rust to build a web app is truly refreshing. I've worked with Java, TypeScript, and Python in recent years, and it's gratifying to catch most errors at compile time instead of during runtime
Thanks. Interesting. What are some best practices for integrating Rust with Elixir/Phoenix in a project, especially when managing CRUD operations and maintaining system efficiency you learned along your side project?
We hit the front page on Hacker News and received many submissions, which led to network errors when fetching some podcasts. I've just added retry logic and scheduling for new podcast fetches and pushed these changes to production.
The Criminal[1] podcast is now added. Due to the current demand, our transcription queue is a bit backed up, so transcription for this podcast will appear in a few days. Please be invited to have a look the next days again.
I'm actively working on securing more GPUs to help scale this process efficiently so in the future you don't have to wait that long.
Would it be interesting if I add e-mail "transcription ready" notifications for those who submit a new podcast?
Thanks! I was inspired by levelsio's meme about having MVPs in a single index.php file. Traditionally, I've organized codebases into folders, but I started questioning its necessity.
Folders often just add an extra layer to search through. It's basically a search param. With Neovim and strict naming conventions, I've found managing everything in one file works quite well. Keyboard navigation can make folders feel like a hassle in the vi context. This setup has been effective so far, though potential downsides might appear later on.
Thanks for asking! Using SQLite with SQLx in Rust provides type-safe SQL queries, which enhances safety by catching errors at compile time.
As for backups, the setup is straightforward: just periodically copy the SQLite file to a secure location. Since it's a single binary and a database file, this keeps things simple and low-maintenance.
Just posting on X (replying under trending posts or in 'build in public' communities).
Some people used the share feature of Audioscrape to emphasize their points in discussions on X. For example, 'Here, this is what Zuckerberg said recently about Y <Link to moment>'
Thanks for sharing your experience! It's impressive to hear about your success with Actix/SQLx and Rust's scalability and efficiency. Knowing Rust can handle such scale is encouraging and gives us confidence for future growth!
While we currently have fewer users, I've also found Rust's type safety and robust system invaluable for building reliable software. In my experience, if it compiles, it just works—quite a contrast to dealing with runtime error minefields in Python, Java, or TypeScript.
I met him in person at the Nvidia AI inception event in Berlin a few weeks ago.
Very friendly and down to earth personality. He said that Nvidia had tough competition when he started (there was only on chip graphics acceleration in 1994) and literally no market for his product because no applications/games supported external graphic acceleration. Still, he and his team were convinced that general purpose computing (CPUs) for everything is not as good as providing a dedicated, specialized computing unit (in this case for graphics). So they just built it and made it. Even though they were nearly bankrupt for multiple times, they survived until 2023 and established themselves as a leader in their field.
He basically worked on this for 30 years. Not many founders show the same endurance.
I am using Replicate to run docker images with a pipeline based on faster-whipser, VAD, pyannote and a custom LLM enhancement flow.
Thanks for sharing candle/ort. Interesting to see the WASM in-browser opportunities