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: Juno – Code Interpreter in Your Jupyter Notebook

ChatGPT Code Interpreter is a game changer for data cleaning, analysis, and plotting, but as early users my friend @amauboussin and I were frustrated that there is no easy way to work on top of its results. You can’t edit code, install packages, work on large datasets, collaborate with teammates, or use it for privacy-sensitive workloads.<p>So we built Juno to bring the power of Code Interpreter to your local Jupyter notebook. It understands your data, generates code directly in your notebook, and can fix its own errors. We’ve found ourselves using it for tons of analysis tasks at our startups, so we decided to release it to everyone!

Show HN: Juno – Code Interpreter in Your Jupyter Notebook

ChatGPT Code Interpreter is a game changer for data cleaning, analysis, and plotting, but as early users my friend @amauboussin and I were frustrated that there is no easy way to work on top of its results. You can’t edit code, install packages, work on large datasets, collaborate with teammates, or use it for privacy-sensitive workloads.<p>So we built Juno to bring the power of Code Interpreter to your local Jupyter notebook. It understands your data, generates code directly in your notebook, and can fix its own errors. We’ve found ourselves using it for tons of analysis tasks at our startups, so we decided to release it to everyone!

Show HN: Nixhub.io – Find Specific Versions of Nix Packages

Show HN: Nixhub.io – Find Specific Versions of Nix Packages

Show HN: Nixhub.io – Find Specific Versions of Nix Packages

Show HN: Open-Source AI Playground

Show HN: DiskerNet – Browse the Internet from Your Disk, Now Open Source

Show HN: DiskerNet – Browse the Internet from Your Disk, Now Open Source

Show HN: Peeng – like Pingdom, but the other way around and simpler

Hey folks! Shahar and Tal from Keep (<a href="https://www.keephq.dev">https://www.keephq.dev</a>) here!<p>For the last few weeks we’ve been building Peeng and can now share our beta with you: <a href="https://www.peeng.sh" rel="nofollow noreferrer">https://www.peeng.sh</a>. Peeng is the easiest and quickest “heartbeat” architecture we could think of. Just pick a subdomain (e.g. x.peeng.sh), configure an interval, an endpoint, and a payload, and hit that subdomain every <X (interval) seconds — If you won’t, Peeng will send an HTTP POST request to your configured endpoint.<p>It’s Pingdom/Cronitor/heartbeat.sh free alternative (but the other way around and A LOT simpler, with a lot more capabilities), suitable for developers, system administrators, DevOps, and individuals with complex networking situations (think “onprem” or K8s clusters with no inbound). Instead of inbound heartbeat checks — Peeng presents outbound heartbeat checks!<p>Quick demo: <a href="https://youtu.be/ZX5mrnMRCwU" rel="nofollow noreferrer">https://youtu.be/ZX5mrnMRCwU</a><p>Why we built this:<p>- We needed an easy way to let Keep (<a href="https://github.com/keephq/keep">https://github.com/keephq/keep</a>) customers behind closed networks monitor their Keep instance - We needed an easy & quick way to setup monitoring for our cronjobs - We wanted to give people with complex networking situations (e.g. behind a firewall) an easy way to monitor their services/processes<p>The beta version lets you:<p>- Create 5 endpoints for free - Configure the endpoint and the payload to be sent when the subdomain is not hit - See the visits (every HTTP GET request to your subdomain) and requests (every HTTP POST sent to your configured endpoint) - Secret header (x-peeng-secret) that confirms requests are made by you<p>What’s next:<p>- A status page that displays your subdomains and their health together with embeddable status blocks that allow you to display the status of an endpoint in your web page (you can also send query params when sending the GET requests that will be included) - Rest API (for subdomain creation, beats retrieval, etc., imagine curl -X POST peeng.sh/subdomain -H API_KEY —json {”subdomain”: “hn”, “endpoint”: “<a href="https://..”" rel="nofollow noreferrer">https://xn--ivg</a>, “payload”: {…}}) - Hierarchy-based subdomains that allow you to create a nested heartbeat solution (i.e. dynamically create a heartbeat subdomain under x.peeng.sh → y.x.peeng.sh, z.x.peeng.sh)<p>This is still very early, so we’d love to hear your feedback and opinions. We’re open to any feature request, so just reach out via Intercom :)

Show HN: Peeng – like Pingdom, but the other way around and simpler

Hey folks! Shahar and Tal from Keep (<a href="https://www.keephq.dev">https://www.keephq.dev</a>) here!<p>For the last few weeks we’ve been building Peeng and can now share our beta with you: <a href="https://www.peeng.sh" rel="nofollow noreferrer">https://www.peeng.sh</a>. Peeng is the easiest and quickest “heartbeat” architecture we could think of. Just pick a subdomain (e.g. x.peeng.sh), configure an interval, an endpoint, and a payload, and hit that subdomain every <X (interval) seconds — If you won’t, Peeng will send an HTTP POST request to your configured endpoint.<p>It’s Pingdom/Cronitor/heartbeat.sh free alternative (but the other way around and A LOT simpler, with a lot more capabilities), suitable for developers, system administrators, DevOps, and individuals with complex networking situations (think “onprem” or K8s clusters with no inbound). Instead of inbound heartbeat checks — Peeng presents outbound heartbeat checks!<p>Quick demo: <a href="https://youtu.be/ZX5mrnMRCwU" rel="nofollow noreferrer">https://youtu.be/ZX5mrnMRCwU</a><p>Why we built this:<p>- We needed an easy way to let Keep (<a href="https://github.com/keephq/keep">https://github.com/keephq/keep</a>) customers behind closed networks monitor their Keep instance - We needed an easy & quick way to setup monitoring for our cronjobs - We wanted to give people with complex networking situations (e.g. behind a firewall) an easy way to monitor their services/processes<p>The beta version lets you:<p>- Create 5 endpoints for free - Configure the endpoint and the payload to be sent when the subdomain is not hit - See the visits (every HTTP GET request to your subdomain) and requests (every HTTP POST sent to your configured endpoint) - Secret header (x-peeng-secret) that confirms requests are made by you<p>What’s next:<p>- A status page that displays your subdomains and their health together with embeddable status blocks that allow you to display the status of an endpoint in your web page (you can also send query params when sending the GET requests that will be included) - Rest API (for subdomain creation, beats retrieval, etc., imagine curl -X POST peeng.sh/subdomain -H API_KEY —json {”subdomain”: “hn”, “endpoint”: “<a href="https://..”" rel="nofollow noreferrer">https://xn--ivg</a>, “payload”: {…}}) - Hierarchy-based subdomains that allow you to create a nested heartbeat solution (i.e. dynamically create a heartbeat subdomain under x.peeng.sh → y.x.peeng.sh, z.x.peeng.sh)<p>This is still very early, so we’d love to hear your feedback and opinions. We’re open to any feature request, so just reach out via Intercom :)

Show HN: Peeng – like Pingdom, but the other way around and simpler

Hey folks! Shahar and Tal from Keep (<a href="https://www.keephq.dev">https://www.keephq.dev</a>) here!<p>For the last few weeks we’ve been building Peeng and can now share our beta with you: <a href="https://www.peeng.sh" rel="nofollow noreferrer">https://www.peeng.sh</a>. Peeng is the easiest and quickest “heartbeat” architecture we could think of. Just pick a subdomain (e.g. x.peeng.sh), configure an interval, an endpoint, and a payload, and hit that subdomain every <X (interval) seconds — If you won’t, Peeng will send an HTTP POST request to your configured endpoint.<p>It’s Pingdom/Cronitor/heartbeat.sh free alternative (but the other way around and A LOT simpler, with a lot more capabilities), suitable for developers, system administrators, DevOps, and individuals with complex networking situations (think “onprem” or K8s clusters with no inbound). Instead of inbound heartbeat checks — Peeng presents outbound heartbeat checks!<p>Quick demo: <a href="https://youtu.be/ZX5mrnMRCwU" rel="nofollow noreferrer">https://youtu.be/ZX5mrnMRCwU</a><p>Why we built this:<p>- We needed an easy way to let Keep (<a href="https://github.com/keephq/keep">https://github.com/keephq/keep</a>) customers behind closed networks monitor their Keep instance - We needed an easy & quick way to setup monitoring for our cronjobs - We wanted to give people with complex networking situations (e.g. behind a firewall) an easy way to monitor their services/processes<p>The beta version lets you:<p>- Create 5 endpoints for free - Configure the endpoint and the payload to be sent when the subdomain is not hit - See the visits (every HTTP GET request to your subdomain) and requests (every HTTP POST sent to your configured endpoint) - Secret header (x-peeng-secret) that confirms requests are made by you<p>What’s next:<p>- A status page that displays your subdomains and their health together with embeddable status blocks that allow you to display the status of an endpoint in your web page (you can also send query params when sending the GET requests that will be included) - Rest API (for subdomain creation, beats retrieval, etc., imagine curl -X POST peeng.sh/subdomain -H API_KEY —json {”subdomain”: “hn”, “endpoint”: “<a href="https://..”" rel="nofollow noreferrer">https://xn--ivg</a>, “payload”: {…}}) - Hierarchy-based subdomains that allow you to create a nested heartbeat solution (i.e. dynamically create a heartbeat subdomain under x.peeng.sh → y.x.peeng.sh, z.x.peeng.sh)<p>This is still very early, so we’d love to hear your feedback and opinions. We’re open to any feature request, so just reach out via Intercom :)

Show HN: Use DNS TXT to share information

dig +short TXT youpay.govorenefekt.com @1.1.1.1 | fold -s<p>You can base64 encode an image, split to TXT records and send over Internet. Useful in certain circumstances. Like when one of the communicating parties is under severe censorship.

Show HN: Use DNS TXT to share information

dig +short TXT youpay.govorenefekt.com @1.1.1.1 | fold -s<p>You can base64 encode an image, split to TXT records and send over Internet. Useful in certain circumstances. Like when one of the communicating parties is under severe censorship.

Show HN: Use DNS TXT to share information

dig +short TXT youpay.govorenefekt.com @1.1.1.1 | fold -s<p>You can base64 encode an image, split to TXT records and send over Internet. Useful in certain circumstances. Like when one of the communicating parties is under severe censorship.

Show HN: Stemformulas.com

During my (ongoing) engineering degree, I've often looked up formulas and been frustrated at the lack of reliable results. Some formulas (usually the easy ones) get their own blurb on Google results, while others are a few clicks away, or are most easily accessed by looking at random university slides on Google images.<p>It felt like, in this day and age, there should be a site that serves the small but noble purpose of being a source of truth for formulas, while leveraging modern website technology to provide a fast and user-friendly experience.<p>So, I made stemformulas.com (with some friends)! It's a really simple website, basically just collection of formulas with a search bar. The formulas are displayed in LaTeX, they're double checked by me against sources that I link for further reading, and I write out all the variable definitions for each one. A feature I recently added was the ability to copy the LaTeX on any formula page (e.g. go to <a href="https://stemformulas.com/formulas/schrodingers-equation/" rel="nofollow noreferrer">https://stemformulas.com/formulas/schrodingers-equation/</a> and click on any LaTeX). LLMs aren't great at getting complex LaTeX right yet, so this felt like a nice value add for users.<p>I've been using this site as basically just a personal hashmap of formulas, but I think it has the potential to help others as well, so I'm hoping to get feedback, formula suggestions, and maybe even some contributors with this post.<p>If you're interested, the source code for the project is available on GitHub at: <a href="https://github.com/stemformulas/stemformulas.github.io">https://github.com/stemformulas/stemformulas.github.io</a><p>About page: <a href="https://stemformulas.com/about/" rel="nofollow noreferrer">https://stemformulas.com/about/</a><p>Thank you all!

Show HN: Curated Transformers – PyTorch LLMs with less code duplication

Show HN: Count lines of code in public GitHub repos

Show HN: Simulating two gears in my game

Show HN: Simulating two gears in my game

Show HN: Structured output from LLMs without reprompting

Built a tool for transforming unstructured data into structured outputs using language models (with 100% adherence).<p>If you're facing problems getting GPT to adhere to a schema (JSON, XML, etc.) or regex, need to bulk process some unstructured data, or generate synthetic data, check it out.<p>We run our own tuned model (you can self-host if you want), so, we're able to have incredibly fine grained control over text generation.<p>Repository: <a href="https://github.com/automorphic-ai/trex">https://github.com/automorphic-ai/trex</a><p>Playground: <a href="https://automorphic.ai/playground" rel="nofollow noreferrer">https://automorphic.ai/playground</a>