The best Hacker News stories from Show from the past day

from

All Show

from the past*

day week month

with these search terms:

Create follow Go back

Latest posts:

Show HN: A tool for creating chord charts on the go

Author here - one of the most notable facts about the app is that it's made entirely in Godot Game Engine! I think it's great for apps like this because it makes it especialy easy to iterate on GUI designs such as this one.<p>Feel free to ask me anything about Chord Chart Memo, or my experience with Godot.

Show HN: A tool for creating chord charts on the go

Author here - one of the most notable facts about the app is that it's made entirely in Godot Game Engine! I think it's great for apps like this because it makes it especialy easy to iterate on GUI designs such as this one.<p>Feel free to ask me anything about Chord Chart Memo, or my experience with Godot.

Show HN: FFmpeg-over-IP – Connect to remote FFmpeg servers

Dear HN,<p>I’m excited to show case a personal project. It has helped me quite a bit with my home lab, I hope it can help you with yours too! ffmpeg-over-ip has two components, a server and a client. You can run the server in an environment with access to a GPU and a locally installed version of ffmpeg, the client only needs network access to the server and no GPU or ffmpeg locally.<p>Both and client and the server need a shared filesystem for this to work (so the server can write output to it, and client can read from it). In my usecase, smb works well if your (GPU) server is a windows machine, nfs works really well for linux setups.<p>This utility can be useful in a number of scenarios:<p>- You find passing through a (v)GPU to your virtual machines complicated<p>- You want to use the same GPU for ffmpeg in multiple virtual machines<p>- Your server has a weak GPU so you want to use the GPU from your gaming machine<p>- Your GPU drivers in one OS are not as good as another (AMD RX6400 never worked for me in linux, but did so in windows)<p>I’ve posted some instructions in the Github package README, please let me know if they are unclear in any way and I’ll try to help!<p>Here's the link: <a href="https://github.com/steelbrain/ffmpeg-over-ip">https://github.com/steelbrain/ffmpeg-over-ip</a>

Show HN: FFmpeg-over-IP – Connect to remote FFmpeg servers

Dear HN,<p>I’m excited to show case a personal project. It has helped me quite a bit with my home lab, I hope it can help you with yours too! ffmpeg-over-ip has two components, a server and a client. You can run the server in an environment with access to a GPU and a locally installed version of ffmpeg, the client only needs network access to the server and no GPU or ffmpeg locally.<p>Both and client and the server need a shared filesystem for this to work (so the server can write output to it, and client can read from it). In my usecase, smb works well if your (GPU) server is a windows machine, nfs works really well for linux setups.<p>This utility can be useful in a number of scenarios:<p>- You find passing through a (v)GPU to your virtual machines complicated<p>- You want to use the same GPU for ffmpeg in multiple virtual machines<p>- Your server has a weak GPU so you want to use the GPU from your gaming machine<p>- Your GPU drivers in one OS are not as good as another (AMD RX6400 never worked for me in linux, but did so in windows)<p>I’ve posted some instructions in the Github package README, please let me know if they are unclear in any way and I’ll try to help!<p>Here's the link: <a href="https://github.com/steelbrain/ffmpeg-over-ip">https://github.com/steelbrain/ffmpeg-over-ip</a>

Show HN: kew – A Terminal Music Player for Linux

Hi HN,<p>I created kew, a music player for the Linux terminal.<p>This started when I asked myself: what if I could just type something like "play nirvana" in the terminal and have the rest taken care of automatically? That got the ball rolling and I kept adding stuff: covers in ascii and then as sixel images, a playlist view, a visualizer, a library view and finally search.<p>While kew can be used as a commandline tool, it has evolved into a TUI app.<p>Here are some example commands:<p>kew nirvana # Plays all of your Nirvana songs, shuffled<p>kew nevermind # Plays the "Nevermind" album in order<p>kew spirit # Plays "Smells Like Teen Spirit"<p>kew all # Plays all your music, shuffled<p>kew albums # Plays one album after the other in random order<p>It works best when your music library is organized like this: Artist/Album(s)/Track(s)<p>kew is written in C and licensed under GPLv2.<p>Source and screenshot: <a href="https://github.com/ravachol/kew">https://github.com/ravachol/kew</a>

Show HN: kew – A Terminal Music Player for Linux

Hi HN,<p>I created kew, a music player for the Linux terminal.<p>This started when I asked myself: what if I could just type something like "play nirvana" in the terminal and have the rest taken care of automatically? That got the ball rolling and I kept adding stuff: covers in ascii and then as sixel images, a playlist view, a visualizer, a library view and finally search.<p>While kew can be used as a commandline tool, it has evolved into a TUI app.<p>Here are some example commands:<p>kew nirvana # Plays all of your Nirvana songs, shuffled<p>kew nevermind # Plays the "Nevermind" album in order<p>kew spirit # Plays "Smells Like Teen Spirit"<p>kew all # Plays all your music, shuffled<p>kew albums # Plays one album after the other in random order<p>It works best when your music library is organized like this: Artist/Album(s)/Track(s)<p>kew is written in C and licensed under GPLv2.<p>Source and screenshot: <a href="https://github.com/ravachol/kew">https://github.com/ravachol/kew</a>

Show HN: kew – A Terminal Music Player for Linux

Hi HN,<p>I created kew, a music player for the Linux terminal.<p>This started when I asked myself: what if I could just type something like "play nirvana" in the terminal and have the rest taken care of automatically? That got the ball rolling and I kept adding stuff: covers in ascii and then as sixel images, a playlist view, a visualizer, a library view and finally search.<p>While kew can be used as a commandline tool, it has evolved into a TUI app.<p>Here are some example commands:<p>kew nirvana # Plays all of your Nirvana songs, shuffled<p>kew nevermind # Plays the "Nevermind" album in order<p>kew spirit # Plays "Smells Like Teen Spirit"<p>kew all # Plays all your music, shuffled<p>kew albums # Plays one album after the other in random order<p>It works best when your music library is organized like this: Artist/Album(s)/Track(s)<p>kew is written in C and licensed under GPLv2.<p>Source and screenshot: <a href="https://github.com/ravachol/kew">https://github.com/ravachol/kew</a>

Show HN: Open source framework OpenAI uses for Advanced Voice

Hey HN, we've been working with OpenAI for the past few months on the new Realtime API.<p>The goal is to give everyone access to the same stack that underpins Advanced Voice in the ChatGPT app.<p>Under the hood it works like this: - A user's speech is captured by a LiveKit client SDK in the ChatGPT app - Their speech is streamed using WebRTC to OpenAI’s voice agent - The agent relays the speech prompt over websocket to GPT-4o - GPT-4o runs inference and streams speech packets (over websocket) back to the agent - The agent relays generated speech using WebRTC back to the user’s device<p>The Realtime API that OpenAI launched is the websocket interface to GPT-4o. This backend framework covers the voice agent portion. Besides having additional logic like function calling, the agent fundamentally proxies WebRTC to websocket.<p>The reason for this is because websocket isn’t the best choice for client-server communication. The vast majority of packet loss occurs between a server and client device and websocket doesn’t provide programmatic control or intervention in lossy network environments like WiFi or cellular. Packet loss leads to higher latency and choppy or garbled audio.

Show HN: Open source framework OpenAI uses for Advanced Voice

Hey HN, we've been working with OpenAI for the past few months on the new Realtime API.<p>The goal is to give everyone access to the same stack that underpins Advanced Voice in the ChatGPT app.<p>Under the hood it works like this: - A user's speech is captured by a LiveKit client SDK in the ChatGPT app - Their speech is streamed using WebRTC to OpenAI’s voice agent - The agent relays the speech prompt over websocket to GPT-4o - GPT-4o runs inference and streams speech packets (over websocket) back to the agent - The agent relays generated speech using WebRTC back to the user’s device<p>The Realtime API that OpenAI launched is the websocket interface to GPT-4o. This backend framework covers the voice agent portion. Besides having additional logic like function calling, the agent fundamentally proxies WebRTC to websocket.<p>The reason for this is because websocket isn’t the best choice for client-server communication. The vast majority of packet loss occurs between a server and client device and websocket doesn’t provide programmatic control or intervention in lossy network environments like WiFi or cellular. Packet loss leads to higher latency and choppy or garbled audio.

Show HN: Open source framework OpenAI uses for Advanced Voice

Hey HN, we've been working with OpenAI for the past few months on the new Realtime API.<p>The goal is to give everyone access to the same stack that underpins Advanced Voice in the ChatGPT app.<p>Under the hood it works like this: - A user's speech is captured by a LiveKit client SDK in the ChatGPT app - Their speech is streamed using WebRTC to OpenAI’s voice agent - The agent relays the speech prompt over websocket to GPT-4o - GPT-4o runs inference and streams speech packets (over websocket) back to the agent - The agent relays generated speech using WebRTC back to the user’s device<p>The Realtime API that OpenAI launched is the websocket interface to GPT-4o. This backend framework covers the voice agent portion. Besides having additional logic like function calling, the agent fundamentally proxies WebRTC to websocket.<p>The reason for this is because websocket isn’t the best choice for client-server communication. The vast majority of packet loss occurs between a server and client device and websocket doesn’t provide programmatic control or intervention in lossy network environments like WiFi or cellular. Packet loss leads to higher latency and choppy or garbled audio.

Show HN: Chebyshev approximation calculator

Hi everyone,<p>here's a web app I made that generates code for efficiently approximating mathematical functions. This is useful when performance matters more than perfect accuracy, for example in embedded systems.<p>The app uses Chebyshev expansions, which despite their theoretical depth result in suprisingly compact and readable code in practice. This code is generated for you and using it does not require any knowledge of the underlying theory.<p>Source code and more info: <a href="https://github.com/stuffmatic/chebyshev-calculator">https://github.com/stuffmatic/chebyshev-calculator</a>

Show HN: Chebyshev approximation calculator

Hi everyone,<p>here's a web app I made that generates code for efficiently approximating mathematical functions. This is useful when performance matters more than perfect accuracy, for example in embedded systems.<p>The app uses Chebyshev expansions, which despite their theoretical depth result in suprisingly compact and readable code in practice. This code is generated for you and using it does not require any knowledge of the underlying theory.<p>Source code and more info: <a href="https://github.com/stuffmatic/chebyshev-calculator">https://github.com/stuffmatic/chebyshev-calculator</a>

Show HN: Chebyshev approximation calculator

Hi everyone,<p>here's a web app I made that generates code for efficiently approximating mathematical functions. This is useful when performance matters more than perfect accuracy, for example in embedded systems.<p>The app uses Chebyshev expansions, which despite their theoretical depth result in suprisingly compact and readable code in practice. This code is generated for you and using it does not require any knowledge of the underlying theory.<p>Source code and more info: <a href="https://github.com/stuffmatic/chebyshev-calculator">https://github.com/stuffmatic/chebyshev-calculator</a>

Show HN: One – A new React framework unifying web, native and local-first

Hey HN, I'm Nate, the creator of Tamagui.<p>One is a React framework that does two things differently in hopes of simplifying how we build websites and apps:<p>1. It unifies React Native and React web with typed file system routing by making Vite able to serve RN. This lets you share (or diverge) your code in a simpler way for cross-platform apps.<p>2. We've partnered with Zero (<a href="https://zerosync.dev" rel="nofollow">https://zerosync.dev</a>) to make local-first work well. We've been building a solution in One that makes Zero supporting server rendering, without waterfalls, and with seamless server/client handoff.<p>---<p>Honestly - I'm a bit hesitant to post One here.<p>HN has really soured on frontend/frameworks. And I get it. We've collectively complicated the hell out of things.<p>That's why I decided to build One. I loved Rails, it made me as a young developer able to finally realize way more ambitious projects than I'd ever done before. I also liked the promise (not implementation) of Meteor - it felt like the clear future, I guess just a bit too early (and a bit too scope-creeped).<p>I worked at Uniswap and built Tamagui and so spent a lot of time building cross-platform apps that share code. Uniswap is built on Tamagui and I think proves you <i>can</i> make really high quality UX while sharing a lot of code - but it's insanely hard and requires a huge team. My goal with One is to make what is now possible but hard dramatically easier.<p>And I think the path to there goes through local-first, because it makes building super responsive apps much, much simpler, and Zero is the first library to actually pull it off in a way that doesn't bloat your bundle or have very limiting constraints.<p>I happened to live down the street from Aaron, one of the founders of Zero, in our tiny town in Hawaii. We talked a lot about Zero over the last couple years, and I found it really admirable how he consistently chose the "harder but better" path in building it. It really shaped into something incredible, and that convinced me to actually launch One, which at the time was more of an experiment.<p>I can see a lot of potential criticism - do we need yet another framework, this is too shiny and vaporware-y, this is just more complexity and abstraction, etc. Happy to respond to those comments if they come.<p>I'm just building out something that I've been wanting for a long time. Opinionated enough to let me move fast like Rails, but leaning on the great work of team Zero so that we don't end up with the scope creep of Meteor. And honestly, it's just really fun to hack on.

Show HN: One – A new React framework unifying web, native and local-first

Hey HN, I'm Nate, the creator of Tamagui.<p>One is a React framework that does two things differently in hopes of simplifying how we build websites and apps:<p>1. It unifies React Native and React web with typed file system routing by making Vite able to serve RN. This lets you share (or diverge) your code in a simpler way for cross-platform apps.<p>2. We've partnered with Zero (<a href="https://zerosync.dev" rel="nofollow">https://zerosync.dev</a>) to make local-first work well. We've been building a solution in One that makes Zero supporting server rendering, without waterfalls, and with seamless server/client handoff.<p>---<p>Honestly - I'm a bit hesitant to post One here.<p>HN has really soured on frontend/frameworks. And I get it. We've collectively complicated the hell out of things.<p>That's why I decided to build One. I loved Rails, it made me as a young developer able to finally realize way more ambitious projects than I'd ever done before. I also liked the promise (not implementation) of Meteor - it felt like the clear future, I guess just a bit too early (and a bit too scope-creeped).<p>I worked at Uniswap and built Tamagui and so spent a lot of time building cross-platform apps that share code. Uniswap is built on Tamagui and I think proves you <i>can</i> make really high quality UX while sharing a lot of code - but it's insanely hard and requires a huge team. My goal with One is to make what is now possible but hard dramatically easier.<p>And I think the path to there goes through local-first, because it makes building super responsive apps much, much simpler, and Zero is the first library to actually pull it off in a way that doesn't bloat your bundle or have very limiting constraints.<p>I happened to live down the street from Aaron, one of the founders of Zero, in our tiny town in Hawaii. We talked a lot about Zero over the last couple years, and I found it really admirable how he consistently chose the "harder but better" path in building it. It really shaped into something incredible, and that convinced me to actually launch One, which at the time was more of an experiment.<p>I can see a lot of potential criticism - do we need yet another framework, this is too shiny and vaporware-y, this is just more complexity and abstraction, etc. Happy to respond to those comments if they come.<p>I'm just building out something that I've been wanting for a long time. Opinionated enough to let me move fast like Rails, but leaning on the great work of team Zero so that we don't end up with the scope creep of Meteor. And honestly, it's just really fun to hack on.

Show HN: One – A new React framework unifying web, native and local-first

Hey HN, I'm Nate, the creator of Tamagui.<p>One is a React framework that does two things differently in hopes of simplifying how we build websites and apps:<p>1. It unifies React Native and React web with typed file system routing by making Vite able to serve RN. This lets you share (or diverge) your code in a simpler way for cross-platform apps.<p>2. We've partnered with Zero (<a href="https://zerosync.dev" rel="nofollow">https://zerosync.dev</a>) to make local-first work well. We've been building a solution in One that makes Zero supporting server rendering, without waterfalls, and with seamless server/client handoff.<p>---<p>Honestly - I'm a bit hesitant to post One here.<p>HN has really soured on frontend/frameworks. And I get it. We've collectively complicated the hell out of things.<p>That's why I decided to build One. I loved Rails, it made me as a young developer able to finally realize way more ambitious projects than I'd ever done before. I also liked the promise (not implementation) of Meteor - it felt like the clear future, I guess just a bit too early (and a bit too scope-creeped).<p>I worked at Uniswap and built Tamagui and so spent a lot of time building cross-platform apps that share code. Uniswap is built on Tamagui and I think proves you <i>can</i> make really high quality UX while sharing a lot of code - but it's insanely hard and requires a huge team. My goal with One is to make what is now possible but hard dramatically easier.<p>And I think the path to there goes through local-first, because it makes building super responsive apps much, much simpler, and Zero is the first library to actually pull it off in a way that doesn't bloat your bundle or have very limiting constraints.<p>I happened to live down the street from Aaron, one of the founders of Zero, in our tiny town in Hawaii. We talked a lot about Zero over the last couple years, and I found it really admirable how he consistently chose the "harder but better" path in building it. It really shaped into something incredible, and that convinced me to actually launch One, which at the time was more of an experiment.<p>I can see a lot of potential criticism - do we need yet another framework, this is too shiny and vaporware-y, this is just more complexity and abstraction, etc. Happy to respond to those comments if they come.<p>I'm just building out something that I've been wanting for a long time. Opinionated enough to let me move fast like Rails, but leaning on the great work of team Zero so that we don't end up with the scope creep of Meteor. And honestly, it's just really fun to hack on.

Show HN: One – A new React framework unifying web, native and local-first

Hey HN, I'm Nate, the creator of Tamagui.<p>One is a React framework that does two things differently in hopes of simplifying how we build websites and apps:<p>1. It unifies React Native and React web with typed file system routing by making Vite able to serve RN. This lets you share (or diverge) your code in a simpler way for cross-platform apps.<p>2. We've partnered with Zero (<a href="https://zerosync.dev" rel="nofollow">https://zerosync.dev</a>) to make local-first work well. We've been building a solution in One that makes Zero supporting server rendering, without waterfalls, and with seamless server/client handoff.<p>---<p>Honestly - I'm a bit hesitant to post One here.<p>HN has really soured on frontend/frameworks. And I get it. We've collectively complicated the hell out of things.<p>That's why I decided to build One. I loved Rails, it made me as a young developer able to finally realize way more ambitious projects than I'd ever done before. I also liked the promise (not implementation) of Meteor - it felt like the clear future, I guess just a bit too early (and a bit too scope-creeped).<p>I worked at Uniswap and built Tamagui and so spent a lot of time building cross-platform apps that share code. Uniswap is built on Tamagui and I think proves you <i>can</i> make really high quality UX while sharing a lot of code - but it's insanely hard and requires a huge team. My goal with One is to make what is now possible but hard dramatically easier.<p>And I think the path to there goes through local-first, because it makes building super responsive apps much, much simpler, and Zero is the first library to actually pull it off in a way that doesn't bloat your bundle or have very limiting constraints.<p>I happened to live down the street from Aaron, one of the founders of Zero, in our tiny town in Hawaii. We talked a lot about Zero over the last couple years, and I found it really admirable how he consistently chose the "harder but better" path in building it. It really shaped into something incredible, and that convinced me to actually launch One, which at the time was more of an experiment.<p>I can see a lot of potential criticism - do we need yet another framework, this is too shiny and vaporware-y, this is just more complexity and abstraction, etc. Happy to respond to those comments if they come.<p>I'm just building out something that I've been wanting for a long time. Opinionated enough to let me move fast like Rails, but leaning on the great work of team Zero so that we don't end up with the scope creep of Meteor. And honestly, it's just really fun to hack on.

Show HN: TurtleSpaces Web Logo – online 3D Logo implementation

Show HN: RelayBeam – A new way of messaging using Ports

Hi HN! I am developing RelayBeam, to overcome the challenges faced by existing messaging platforms. I've introduced Ports based feature for contextual communication.<p>It organizes conversations based on context through the user-defined ports.<p>I've explained in detail about it with some examples at <a href="https://relaybeam.com/about" rel="nofollow">https://relaybeam.com/about</a><p>Do try and suggest any more features you'd like to use!

Show HN: Quilt – Powerful RAG UI for Document QA

Hey HN! We've just launched Quilt, a robust RAG (Retrieval-Augmented Generation) UI that revolutionizes how you interact with your documents.<p>Key features: - Multi-user setup with private/public document collections - Advanced hybrid RAG pipeline combining full-text & vector search - Smart citations with in-browser PDF preview and highlights - Fully customizable settings and prompts through the UI<p>Making an account is free, no need to even use a strong password: this is only to ensure your documents are separate from the rest.<p>We're keen to hear your thoughts and feedback. What features would you like to see next?