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: Interviews Chat – Never bomb another job interview with this AI copilot

Hey HN! I'm Artur, a full-stack developer with a passion for building tools that solve real-world problems. After years of navigating the often-stressful world of job interviews, I decided to build Interviews Chat, an AI-powered platform designed to help you prepare for and ace your next interview.<p>Here's what Interviews Chat offers:<p>Personalized Question Prep: Paste your resume and the job description, and our AI will generate a tailored list of potential interview questions. No more generic lists – get ready for the specific questions you're most likely to face.<p>Realistic Practice: Record your answers to practice questions in a simulated interview environment using your webcam. This helps you get comfortable with the format and build confidence.<p>In-depth Feedback: Our AI analyzes your recorded responses, providing detailed feedback on content relevance, clarity, and even your confidence level.<p>Real-time Interview Copilot: For those crucial live interviews, our AI acts as a silent partner, listening in and offering real-time suggestions on what to say next. It can even analyze whiteboard challenges and coding tasks to help you shine.<p>Tech Stack:<p>Interviews Chat leverages the power of Next.js, React, Vercel, and OpenAI's cutting-edge language models (GPT, Whisper) to deliver a seamless and effective interview preparation experience.<p>Why I Built It:<p>I believe everyone deserves to feel confident and prepared going into a job interview. Interviews Chat removes the guesswork and anxiety, providing you with the tools and insights you need to showcase your skills and land your dream job.<p>Try it out:<p>I'm excited to share Interviews Chat with the HN community. You can try it out with free credits at <a href="https://www.interviews.chat" rel="nofollow">https://www.interviews.chat</a><p>I'd love to hear your feedback and suggestions!

Show HN: zfind – CLI like find but using SQL syntax and also does tar/zip

I wrote this because I needed to search a lot of files, including some archives, for files in a date range but couldn't find any good tools.<p>Also I never liked find's option syntax. I think most people already know SQL (or at least it's easier to learn) and a much better match for this task.

Show HN: zfind – CLI like find but using SQL syntax and also does tar/zip

I wrote this because I needed to search a lot of files, including some archives, for files in a date range but couldn't find any good tools.<p>Also I never liked find's option syntax. I think most people already know SQL (or at least it's easier to learn) and a much better match for this task.

Show HN: Synthesize TikZ Graphics Programs for Scientific Figures and Sketches

Creating high-quality scientific figures can be time-consuming and challenging, even though sketching ideas on paper is relatively easy. Furthermore, recreating existing figures that are not stored in formats preserving semantic information is equally complex. To tackle this problem, we introduce DeTikZify, a novel multimodal language model that automatically synthesizes scientific figures as semantics-preserving TikZ graphics programs based on sketches and existing figures. We also introduce a Monte Carlo Tree Search-based inference algorithm that enables DeTikZify to iteratively refine its outputs without the need for additional training.

Show HN: Synthesize TikZ Graphics Programs for Scientific Figures and Sketches

Creating high-quality scientific figures can be time-consuming and challenging, even though sketching ideas on paper is relatively easy. Furthermore, recreating existing figures that are not stored in formats preserving semantic information is equally complex. To tackle this problem, we introduce DeTikZify, a novel multimodal language model that automatically synthesizes scientific figures as semantics-preserving TikZ graphics programs based on sketches and existing figures. We also introduce a Monte Carlo Tree Search-based inference algorithm that enables DeTikZify to iteratively refine its outputs without the need for additional training.

Show HN: Synthesize TikZ Graphics Programs for Scientific Figures and Sketches

Creating high-quality scientific figures can be time-consuming and challenging, even though sketching ideas on paper is relatively easy. Furthermore, recreating existing figures that are not stored in formats preserving semantic information is equally complex. To tackle this problem, we introduce DeTikZify, a novel multimodal language model that automatically synthesizes scientific figures as semantics-preserving TikZ graphics programs based on sketches and existing figures. We also introduce a Monte Carlo Tree Search-based inference algorithm that enables DeTikZify to iteratively refine its outputs without the need for additional training.

Show HN: XPipe, a brand-new type of remote file browser and shell connection hub

Hey HN, I built this over the last year as I always wanted to have an easy file and terminal access to all of my servers, including containers and clusters that you normally can't connect to with existing solutions out of the box.<p>At first glance it might not look very novel, but if you dig a little deeper, you will see that the entire foundation of how it communicates with remote systems is completely different from any other solution out there. What happens in the background can essentially be explained this way: It launches a local shell process like cmd, sh, etc. and in it executes a command that opens a remote shell connection such as ssh user@host. All communication is then done through the stdin/stdout/stderr of that process. From there, it detects what kind of server and environment, e.g. shell type, os, etc. you have logged into and adjusts how it talks to the remote system. By then using file system related commands such as ls, rm, touch, etc. and its equivalents, it can realize a functional file manager that works on essentially every system without any protocol requirements. For other types of connections, it can just execute things like docker exec -i to open a shell into a container and work the same way. Right now it supports: - SSH by running your locally installed SSH CLI client - Docker, Podman, LXD, and Kubernetes containers - WSL, MSYS2, and Cygwin environments on Windows - Various other things like some VMs for VMware and Proxmox, but work is still going on on there<p>This approach to delegate everything to your installed tools is also utilized for other tasks. That means that I can save a lot of development time while you can happily use the tools you are comfortable with in conjunction with XPipe. In fact, XPipe doesn't ship with any libraries or tools for remote shell connections, protocol handling, or terminal integration at all. It just delegates everything to your own text editor, terminal emulator, RDP clients, and more.<p>Due to its nature, XPipe has to handle a lot of sensitive information like passwords, keys, and more. To tackle the topics of security and privacy, I put an emphasis on security settings and created a dedicated security page in the docs that should hopefully contain all relevant information. There is also a password manager integration, so you don't have to store any sensitive information in XPipe itself if you use a compatible password manager.<p>As it is a common use case to synchronize connection information across many systems, e.g. your desktop at home and laptop for travel, there is also a git integration which allows you to have XPipe automatically synchronize all connection information with a remote git repository of your choice. It supports any git remote repository, advanced authentication measures like SSH auth, GPG signing, and more. You can also use this for collaboration if you're working in a team.<p>The early stage development has been quite challenging as this new approach requires a completely new implementation, but I am confident that it's ready now. I appreciate any kind of feedback from you to guide me in the right development direction from here.<p>Enjoy!

Show HN: XPipe, a brand-new type of remote file browser and shell connection hub

Hey HN, I built this over the last year as I always wanted to have an easy file and terminal access to all of my servers, including containers and clusters that you normally can't connect to with existing solutions out of the box.<p>At first glance it might not look very novel, but if you dig a little deeper, you will see that the entire foundation of how it communicates with remote systems is completely different from any other solution out there. What happens in the background can essentially be explained this way: It launches a local shell process like cmd, sh, etc. and in it executes a command that opens a remote shell connection such as ssh user@host. All communication is then done through the stdin/stdout/stderr of that process. From there, it detects what kind of server and environment, e.g. shell type, os, etc. you have logged into and adjusts how it talks to the remote system. By then using file system related commands such as ls, rm, touch, etc. and its equivalents, it can realize a functional file manager that works on essentially every system without any protocol requirements. For other types of connections, it can just execute things like docker exec -i to open a shell into a container and work the same way. Right now it supports: - SSH by running your locally installed SSH CLI client - Docker, Podman, LXD, and Kubernetes containers - WSL, MSYS2, and Cygwin environments on Windows - Various other things like some VMs for VMware and Proxmox, but work is still going on on there<p>This approach to delegate everything to your installed tools is also utilized for other tasks. That means that I can save a lot of development time while you can happily use the tools you are comfortable with in conjunction with XPipe. In fact, XPipe doesn't ship with any libraries or tools for remote shell connections, protocol handling, or terminal integration at all. It just delegates everything to your own text editor, terminal emulator, RDP clients, and more.<p>Due to its nature, XPipe has to handle a lot of sensitive information like passwords, keys, and more. To tackle the topics of security and privacy, I put an emphasis on security settings and created a dedicated security page in the docs that should hopefully contain all relevant information. There is also a password manager integration, so you don't have to store any sensitive information in XPipe itself if you use a compatible password manager.<p>As it is a common use case to synchronize connection information across many systems, e.g. your desktop at home and laptop for travel, there is also a git integration which allows you to have XPipe automatically synchronize all connection information with a remote git repository of your choice. It supports any git remote repository, advanced authentication measures like SSH auth, GPG signing, and more. You can also use this for collaboration if you're working in a team.<p>The early stage development has been quite challenging as this new approach requires a completely new implementation, but I am confident that it's ready now. I appreciate any kind of feedback from you to guide me in the right development direction from here.<p>Enjoy!

Show HN: XPipe, a brand-new type of remote file browser and shell connection hub

Hey HN, I built this over the last year as I always wanted to have an easy file and terminal access to all of my servers, including containers and clusters that you normally can't connect to with existing solutions out of the box.<p>At first glance it might not look very novel, but if you dig a little deeper, you will see that the entire foundation of how it communicates with remote systems is completely different from any other solution out there. What happens in the background can essentially be explained this way: It launches a local shell process like cmd, sh, etc. and in it executes a command that opens a remote shell connection such as ssh user@host. All communication is then done through the stdin/stdout/stderr of that process. From there, it detects what kind of server and environment, e.g. shell type, os, etc. you have logged into and adjusts how it talks to the remote system. By then using file system related commands such as ls, rm, touch, etc. and its equivalents, it can realize a functional file manager that works on essentially every system without any protocol requirements. For other types of connections, it can just execute things like docker exec -i to open a shell into a container and work the same way. Right now it supports: - SSH by running your locally installed SSH CLI client - Docker, Podman, LXD, and Kubernetes containers - WSL, MSYS2, and Cygwin environments on Windows - Various other things like some VMs for VMware and Proxmox, but work is still going on on there<p>This approach to delegate everything to your installed tools is also utilized for other tasks. That means that I can save a lot of development time while you can happily use the tools you are comfortable with in conjunction with XPipe. In fact, XPipe doesn't ship with any libraries or tools for remote shell connections, protocol handling, or terminal integration at all. It just delegates everything to your own text editor, terminal emulator, RDP clients, and more.<p>Due to its nature, XPipe has to handle a lot of sensitive information like passwords, keys, and more. To tackle the topics of security and privacy, I put an emphasis on security settings and created a dedicated security page in the docs that should hopefully contain all relevant information. There is also a password manager integration, so you don't have to store any sensitive information in XPipe itself if you use a compatible password manager.<p>As it is a common use case to synchronize connection information across many systems, e.g. your desktop at home and laptop for travel, there is also a git integration which allows you to have XPipe automatically synchronize all connection information with a remote git repository of your choice. It supports any git remote repository, advanced authentication measures like SSH auth, GPG signing, and more. You can also use this for collaboration if you're working in a team.<p>The early stage development has been quite challenging as this new approach requires a completely new implementation, but I am confident that it's ready now. I appreciate any kind of feedback from you to guide me in the right development direction from here.<p>Enjoy!

Show HN: XPipe, a brand-new type of remote file browser and shell connection hub

Hey HN, I built this over the last year as I always wanted to have an easy file and terminal access to all of my servers, including containers and clusters that you normally can't connect to with existing solutions out of the box.<p>At first glance it might not look very novel, but if you dig a little deeper, you will see that the entire foundation of how it communicates with remote systems is completely different from any other solution out there. What happens in the background can essentially be explained this way: It launches a local shell process like cmd, sh, etc. and in it executes a command that opens a remote shell connection such as ssh user@host. All communication is then done through the stdin/stdout/stderr of that process. From there, it detects what kind of server and environment, e.g. shell type, os, etc. you have logged into and adjusts how it talks to the remote system. By then using file system related commands such as ls, rm, touch, etc. and its equivalents, it can realize a functional file manager that works on essentially every system without any protocol requirements. For other types of connections, it can just execute things like docker exec -i to open a shell into a container and work the same way. Right now it supports: - SSH by running your locally installed SSH CLI client - Docker, Podman, LXD, and Kubernetes containers - WSL, MSYS2, and Cygwin environments on Windows - Various other things like some VMs for VMware and Proxmox, but work is still going on on there<p>This approach to delegate everything to your installed tools is also utilized for other tasks. That means that I can save a lot of development time while you can happily use the tools you are comfortable with in conjunction with XPipe. In fact, XPipe doesn't ship with any libraries or tools for remote shell connections, protocol handling, or terminal integration at all. It just delegates everything to your own text editor, terminal emulator, RDP clients, and more.<p>Due to its nature, XPipe has to handle a lot of sensitive information like passwords, keys, and more. To tackle the topics of security and privacy, I put an emphasis on security settings and created a dedicated security page in the docs that should hopefully contain all relevant information. There is also a password manager integration, so you don't have to store any sensitive information in XPipe itself if you use a compatible password manager.<p>As it is a common use case to synchronize connection information across many systems, e.g. your desktop at home and laptop for travel, there is also a git integration which allows you to have XPipe automatically synchronize all connection information with a remote git repository of your choice. It supports any git remote repository, advanced authentication measures like SSH auth, GPG signing, and more. You can also use this for collaboration if you're working in a team.<p>The early stage development has been quite challenging as this new approach requires a completely new implementation, but I am confident that it's ready now. I appreciate any kind of feedback from you to guide me in the right development direction from here.<p>Enjoy!

Show HN: 2d web paddle game

Simple retro paddle arcade game written in Javascript, using good ol' Canvas.

Show HN: 2d web paddle game

Simple retro paddle arcade game written in Javascript, using good ol' Canvas.

Show HN: 2d web paddle game

Simple retro paddle arcade game written in Javascript, using good ol' Canvas.

Show HN: Mesop – Open-source Python UI framework

I’m excited to share about Mesop - a new, open-source Python UI framework that enables Python developers to quickly build delightful web apps in a scalable way.<p>A small team of us at Google have been developing Mesop as an unofficial 20% project for the past few months. A wide range of research and product teams at Google have been using it to rapidly build internal apps and we’ve gotten a lot of positive feedback internally so now we’re looking to get feedback from the open-source community.<p>We think that Mesop provides a unique approach to building web UIs in Python - making it both easy to get started and also flexible enough to build customized UIs for a wide range of use cases. You can learn more about why we built Mesop here: <a href="https://google.github.io/mesop/blog/2024/05/13/why-mesop/" rel="nofollow">https://google.github.io/mesop/blog/2024/05/13/why-mesop/</a><p>To look at some example Mesop apps, check out our demo gallery: <a href="https://google.github.io/mesop/demo/" rel="nofollow">https://google.github.io/mesop/demo/</a>. Also, the demo gallery itself is built with Mesop: <a href="https://github.com/google/mesop/blob/main/demo/main.py">https://github.com/google/mesop/blob/main/demo/main.py</a> which demonstrates the type of flexibility you have in building apps with Mesop.<p>A couple of us will be on here answering questions. Let us know what you think!

Show HN: Mesop – Open-source Python UI framework

I’m excited to share about Mesop - a new, open-source Python UI framework that enables Python developers to quickly build delightful web apps in a scalable way.<p>A small team of us at Google have been developing Mesop as an unofficial 20% project for the past few months. A wide range of research and product teams at Google have been using it to rapidly build internal apps and we’ve gotten a lot of positive feedback internally so now we’re looking to get feedback from the open-source community.<p>We think that Mesop provides a unique approach to building web UIs in Python - making it both easy to get started and also flexible enough to build customized UIs for a wide range of use cases. You can learn more about why we built Mesop here: <a href="https://google.github.io/mesop/blog/2024/05/13/why-mesop/" rel="nofollow">https://google.github.io/mesop/blog/2024/05/13/why-mesop/</a><p>To look at some example Mesop apps, check out our demo gallery: <a href="https://google.github.io/mesop/demo/" rel="nofollow">https://google.github.io/mesop/demo/</a>. Also, the demo gallery itself is built with Mesop: <a href="https://github.com/google/mesop/blob/main/demo/main.py">https://github.com/google/mesop/blob/main/demo/main.py</a> which demonstrates the type of flexibility you have in building apps with Mesop.<p>A couple of us will be on here answering questions. Let us know what you think!

Show HN: Original 8x16 ASCII Fixed Width Font: Classic Console Neue

Show HN: Original 8x16 ASCII Fixed Width Font: Classic Console Neue

Show HN: Laudspeaker – Open-source mobile push, SMS and email automation

Hey HN, we are sharing again, after a year of updates!<p>Laudspeaker (<a href="https://laudspeaker.com/">https://laudspeaker.com/</a>) is an open source customer engagement suite (also called marketing automation software). If you've used tools like Braze, One Signal, Airship, Iterable, Customer.io or some others, Laudspeaker is an alternative to these. Here is a quick demo: <a href="https://www.loom.com/share/4b309390ee274ea491981e1394e9abc4" rel="nofollow">https://www.loom.com/share/4b309390ee274ea491981e1394e9abc4</a>. And here is a link to sign up and try free (no cc needed): <a href="https://app.laudspeaker.com/signup">https://app.laudspeaker.com/signup</a>.<p>Or if you prefer to just jump in, go to <a href="https://app.laudspeaker.com/login">https://app.laudspeaker.com/login</a> and use this test account:<p><pre><code> email: test94@laudspeaker.com pw: test93@laudspeaker.com </code></pre> The main things Laudspeaker lets you do are:<p>1. Define 'segments': which of your users should receive messages.<p>2. Define 'messaging journeys': when, where and with which channels you want to reach users. Right now we support push, email, SMS, and soon we'll also include in-app messages and WhatsApp.<p>For example, one customer of ours runs a journey like this: "Wait for a user to complete onboarding on our mobile app, then send a welcome push. If they complete an action the next day on the app, stop sending messages, otherwise send a followup email."<p>There are quite a few big updates since our last Show HN (<a href="https://news.ycombinator.com/item?id=34835559">https://news.ycombinator.com/item?id=34835559</a>):<p>We now have a mobile SDK for sending and receiving push notifications. We have revamped the journey builder, and made our segment builder much more comprehensive. Our application is also a lot more battle tested - we are deployed with a major fintech in Asia and are sending XX million messages a week to more than x million users.<p>We've seen a lot of demand from consumer focused apps and websites who find most of the existing solutions' pricing models prohibitively expensive so please reach out if that sounds like you. We have successfully migrated people over from Braze, customer io and others.<p>If you're interested in the mobile SdK, see our tutorial: <a href="https://laudspeaker.com/docs/getting-started/setting-up-mobile-push">https://laudspeaker.com/docs/getting-started/setting-up-mobi...</a>,<p>and sample apps: <a href="https://github.com/laudspeaker/android-sample-app">https://github.com/laudspeaker/android-sample-app</a>, <a href="https://github.com/laudspeaker/ios-sample-app">https://github.com/laudspeaker/ios-sample-app</a>.<p>Our Github is <a href="https://github.com/laudspeaker/laudspeaker">https://github.com/laudspeaker/laudspeaker</a>. Try it out for free at <a href="https://app.laudspeaker.com/signup">https://app.laudspeaker.com/signup</a>.<p>We'd love to hear your feedback and comments!

Show HN: Laudspeaker – Open-source mobile push, SMS and email automation

Hey HN, we are sharing again, after a year of updates!<p>Laudspeaker (<a href="https://laudspeaker.com/">https://laudspeaker.com/</a>) is an open source customer engagement suite (also called marketing automation software). If you've used tools like Braze, One Signal, Airship, Iterable, Customer.io or some others, Laudspeaker is an alternative to these. Here is a quick demo: <a href="https://www.loom.com/share/4b309390ee274ea491981e1394e9abc4" rel="nofollow">https://www.loom.com/share/4b309390ee274ea491981e1394e9abc4</a>. And here is a link to sign up and try free (no cc needed): <a href="https://app.laudspeaker.com/signup">https://app.laudspeaker.com/signup</a>.<p>Or if you prefer to just jump in, go to <a href="https://app.laudspeaker.com/login">https://app.laudspeaker.com/login</a> and use this test account:<p><pre><code> email: test94@laudspeaker.com pw: test93@laudspeaker.com </code></pre> The main things Laudspeaker lets you do are:<p>1. Define 'segments': which of your users should receive messages.<p>2. Define 'messaging journeys': when, where and with which channels you want to reach users. Right now we support push, email, SMS, and soon we'll also include in-app messages and WhatsApp.<p>For example, one customer of ours runs a journey like this: "Wait for a user to complete onboarding on our mobile app, then send a welcome push. If they complete an action the next day on the app, stop sending messages, otherwise send a followup email."<p>There are quite a few big updates since our last Show HN (<a href="https://news.ycombinator.com/item?id=34835559">https://news.ycombinator.com/item?id=34835559</a>):<p>We now have a mobile SDK for sending and receiving push notifications. We have revamped the journey builder, and made our segment builder much more comprehensive. Our application is also a lot more battle tested - we are deployed with a major fintech in Asia and are sending XX million messages a week to more than x million users.<p>We've seen a lot of demand from consumer focused apps and websites who find most of the existing solutions' pricing models prohibitively expensive so please reach out if that sounds like you. We have successfully migrated people over from Braze, customer io and others.<p>If you're interested in the mobile SdK, see our tutorial: <a href="https://laudspeaker.com/docs/getting-started/setting-up-mobile-push">https://laudspeaker.com/docs/getting-started/setting-up-mobi...</a>,<p>and sample apps: <a href="https://github.com/laudspeaker/android-sample-app">https://github.com/laudspeaker/android-sample-app</a>, <a href="https://github.com/laudspeaker/ios-sample-app">https://github.com/laudspeaker/ios-sample-app</a>.<p>Our Github is <a href="https://github.com/laudspeaker/laudspeaker">https://github.com/laudspeaker/laudspeaker</a>. Try it out for free at <a href="https://app.laudspeaker.com/signup">https://app.laudspeaker.com/signup</a>.<p>We'd love to hear your feedback and comments!

Show HN: Laudspeaker – Open-source mobile push, SMS and email automation

Hey HN, we are sharing again, after a year of updates!<p>Laudspeaker (<a href="https://laudspeaker.com/">https://laudspeaker.com/</a>) is an open source customer engagement suite (also called marketing automation software). If you've used tools like Braze, One Signal, Airship, Iterable, Customer.io or some others, Laudspeaker is an alternative to these. Here is a quick demo: <a href="https://www.loom.com/share/4b309390ee274ea491981e1394e9abc4" rel="nofollow">https://www.loom.com/share/4b309390ee274ea491981e1394e9abc4</a>. And here is a link to sign up and try free (no cc needed): <a href="https://app.laudspeaker.com/signup">https://app.laudspeaker.com/signup</a>.<p>Or if you prefer to just jump in, go to <a href="https://app.laudspeaker.com/login">https://app.laudspeaker.com/login</a> and use this test account:<p><pre><code> email: test94@laudspeaker.com pw: test93@laudspeaker.com </code></pre> The main things Laudspeaker lets you do are:<p>1. Define 'segments': which of your users should receive messages.<p>2. Define 'messaging journeys': when, where and with which channels you want to reach users. Right now we support push, email, SMS, and soon we'll also include in-app messages and WhatsApp.<p>For example, one customer of ours runs a journey like this: "Wait for a user to complete onboarding on our mobile app, then send a welcome push. If they complete an action the next day on the app, stop sending messages, otherwise send a followup email."<p>There are quite a few big updates since our last Show HN (<a href="https://news.ycombinator.com/item?id=34835559">https://news.ycombinator.com/item?id=34835559</a>):<p>We now have a mobile SDK for sending and receiving push notifications. We have revamped the journey builder, and made our segment builder much more comprehensive. Our application is also a lot more battle tested - we are deployed with a major fintech in Asia and are sending XX million messages a week to more than x million users.<p>We've seen a lot of demand from consumer focused apps and websites who find most of the existing solutions' pricing models prohibitively expensive so please reach out if that sounds like you. We have successfully migrated people over from Braze, customer io and others.<p>If you're interested in the mobile SdK, see our tutorial: <a href="https://laudspeaker.com/docs/getting-started/setting-up-mobile-push">https://laudspeaker.com/docs/getting-started/setting-up-mobi...</a>,<p>and sample apps: <a href="https://github.com/laudspeaker/android-sample-app">https://github.com/laudspeaker/android-sample-app</a>, <a href="https://github.com/laudspeaker/ios-sample-app">https://github.com/laudspeaker/ios-sample-app</a>.<p>Our Github is <a href="https://github.com/laudspeaker/laudspeaker">https://github.com/laudspeaker/laudspeaker</a>. Try it out for free at <a href="https://app.laudspeaker.com/signup">https://app.laudspeaker.com/signup</a>.<p>We'd love to hear your feedback and comments!