The best Hacker News stories from Show from the past day
Latest posts:
Show HN: WeExpire.org – Notes readable only after your death
Show HN: Lofi, a Tiny Spotify Player
Show HN: Lofi, a Tiny Spotify Player
Show HN: Lofi, a Tiny Spotify Player
Show HN: ChatGPT-i18n – Translate websites' locale json files with AI assistance
I build this app because I was tired of using Google Translate to translate my locale files (i18n). I wanted to use a more efficient and accurate translation tool. ChatGPT, however, always break my json and cannot translate large contents. So I build this app to solve these problems. Hope it can save your time.<p>github: <a href="https://github.com/ObservedObserver/chatgpt-i18n">https://github.com/ObservedObserver/chatgpt-i18n</a><p>online app: <a href="https://chatgpt-i18n.vercel.app/" rel="nofollow">https://chatgpt-i18n.vercel.app/</a>
Show HN: ChatGPT-i18n – Translate websites' locale json files with AI assistance
I build this app because I was tired of using Google Translate to translate my locale files (i18n). I wanted to use a more efficient and accurate translation tool. ChatGPT, however, always break my json and cannot translate large contents. So I build this app to solve these problems. Hope it can save your time.<p>github: <a href="https://github.com/ObservedObserver/chatgpt-i18n">https://github.com/ObservedObserver/chatgpt-i18n</a><p>online app: <a href="https://chatgpt-i18n.vercel.app/" rel="nofollow">https://chatgpt-i18n.vercel.app/</a>
Show HN: ChatGPT-i18n – Translate websites' locale json files with AI assistance
I build this app because I was tired of using Google Translate to translate my locale files (i18n). I wanted to use a more efficient and accurate translation tool. ChatGPT, however, always break my json and cannot translate large contents. So I build this app to solve these problems. Hope it can save your time.<p>github: <a href="https://github.com/ObservedObserver/chatgpt-i18n">https://github.com/ObservedObserver/chatgpt-i18n</a><p>online app: <a href="https://chatgpt-i18n.vercel.app/" rel="nofollow">https://chatgpt-i18n.vercel.app/</a>
Show HN: APIRank.dev – We crawled and ranked public APIs from the internet
tl;dr we at Escape (YC W23), we scanned 5651+ public APIs on the internet with our in house feedback driven API exploration tech, and ranked them using security, performance, reliability, and design criteria. The results are public on <a href="https://apirank.dev" rel="nofollow">https://apirank.dev</a>. You can request that we index your own API to the list for free and see how it compares to others.<p>Why we did that?<p>During a YC meetup I spoke with a fellow founder that told me how hard it was to pick the right external APIs to use within your own projects. I realized that most of what we build relies on public APIs from external vendors, but there was no benchmark to help developers compare and evaluate public APIs before picking one. So we decided to do it ourselves. Say hi to apirank.dev.<p>Why is ranking public APIs hard? Automating Public API technical assessment is a tough problem. First, we needed to find all the public APIs and their specifications - mostly OpenAPI files.<p>We used several strategies to find those:<p>- Crawl API repositories like apis.guru<p>- Crawl Github for openapi.json and openapi.yaml files<p>- A cool google dork<p>Those strategies enabled us to gather around ~20.000 OpenAPI specs.<p>Then lies the hard part of the problem:<p>We want to dynamically evaluate those APIs' security, performance, and reliability.<p>But APIs take parameters that are tightly coupled to the underlying business logic.<p>A naive automated way would not work: putting random data in parameters would likely not pass the API's validation layer, thus giving us little insight into the real API behavior.<p>Manually creating tests for each API is also not sustainable: it would take years for our 10-people team. We needed to do it in an automated way.<p>Fortunately, our main R&D efforts at Escape aimed to generate legitimate traffic against any API efficently.<p>That's how we developed Feedback-Driven API exploration, a new technique that quickly asses the underlying business logic of an API by analyzing responses and dependencies between requests. (see <a href="https://escape.tech/blog/feedback-driven-api-exploration/">https://escape.tech/blog/feedback-driven-api-exploration/</a>)<p>We originally developed this technology for advanced API security testing. But from there, it was super easy to also test the performance and the reliability of APIs.<p>How we ranked APIs?<p>Now that we have a scalable way to gather exciting data from public APIs, we need to find a way to rank them. And this ranking should be meaningful to developers when choosing their APIs.<p>We decided to rank APIs using the following five criteria:<p>- Security
- Performance
- Reliability
- Design
- Popularity<p>Security score is computed as a combination of the number of OWASP top 10 vulnerabilities, and the number of sensitive information leaks detected by our scanner<p>The performance score is derived from the median response time of the API, aka the P50<p>The reliability score is derived from the number of inconsistent server responses, either 500 errors or responses that are not conform with the specification<p>The Design score reflects the quality of the OpenAPI specification file. Having comments, examples, a license, and contact information improves this score<p>The popularity score is computed from the number of references to the API found online<p>If you are curious about your API's performance, you can ask us to index your own api for free at <a href="https://apirank.dev/submit" rel="nofollow">https://apirank.dev/submit</a>
Show HN: APIRank.dev – We crawled and ranked public APIs from the internet
tl;dr we at Escape (YC W23), we scanned 5651+ public APIs on the internet with our in house feedback driven API exploration tech, and ranked them using security, performance, reliability, and design criteria. The results are public on <a href="https://apirank.dev" rel="nofollow">https://apirank.dev</a>. You can request that we index your own API to the list for free and see how it compares to others.<p>Why we did that?<p>During a YC meetup I spoke with a fellow founder that told me how hard it was to pick the right external APIs to use within your own projects. I realized that most of what we build relies on public APIs from external vendors, but there was no benchmark to help developers compare and evaluate public APIs before picking one. So we decided to do it ourselves. Say hi to apirank.dev.<p>Why is ranking public APIs hard? Automating Public API technical assessment is a tough problem. First, we needed to find all the public APIs and their specifications - mostly OpenAPI files.<p>We used several strategies to find those:<p>- Crawl API repositories like apis.guru<p>- Crawl Github for openapi.json and openapi.yaml files<p>- A cool google dork<p>Those strategies enabled us to gather around ~20.000 OpenAPI specs.<p>Then lies the hard part of the problem:<p>We want to dynamically evaluate those APIs' security, performance, and reliability.<p>But APIs take parameters that are tightly coupled to the underlying business logic.<p>A naive automated way would not work: putting random data in parameters would likely not pass the API's validation layer, thus giving us little insight into the real API behavior.<p>Manually creating tests for each API is also not sustainable: it would take years for our 10-people team. We needed to do it in an automated way.<p>Fortunately, our main R&D efforts at Escape aimed to generate legitimate traffic against any API efficently.<p>That's how we developed Feedback-Driven API exploration, a new technique that quickly asses the underlying business logic of an API by analyzing responses and dependencies between requests. (see <a href="https://escape.tech/blog/feedback-driven-api-exploration/">https://escape.tech/blog/feedback-driven-api-exploration/</a>)<p>We originally developed this technology for advanced API security testing. But from there, it was super easy to also test the performance and the reliability of APIs.<p>How we ranked APIs?<p>Now that we have a scalable way to gather exciting data from public APIs, we need to find a way to rank them. And this ranking should be meaningful to developers when choosing their APIs.<p>We decided to rank APIs using the following five criteria:<p>- Security
- Performance
- Reliability
- Design
- Popularity<p>Security score is computed as a combination of the number of OWASP top 10 vulnerabilities, and the number of sensitive information leaks detected by our scanner<p>The performance score is derived from the median response time of the API, aka the P50<p>The reliability score is derived from the number of inconsistent server responses, either 500 errors or responses that are not conform with the specification<p>The Design score reflects the quality of the OpenAPI specification file. Having comments, examples, a license, and contact information improves this score<p>The popularity score is computed from the number of references to the API found online<p>If you are curious about your API's performance, you can ask us to index your own api for free at <a href="https://apirank.dev/submit" rel="nofollow">https://apirank.dev/submit</a>
Show HN: APIRank.dev – We crawled and ranked public APIs from the internet
tl;dr we at Escape (YC W23), we scanned 5651+ public APIs on the internet with our in house feedback driven API exploration tech, and ranked them using security, performance, reliability, and design criteria. The results are public on <a href="https://apirank.dev" rel="nofollow">https://apirank.dev</a>. You can request that we index your own API to the list for free and see how it compares to others.<p>Why we did that?<p>During a YC meetup I spoke with a fellow founder that told me how hard it was to pick the right external APIs to use within your own projects. I realized that most of what we build relies on public APIs from external vendors, but there was no benchmark to help developers compare and evaluate public APIs before picking one. So we decided to do it ourselves. Say hi to apirank.dev.<p>Why is ranking public APIs hard? Automating Public API technical assessment is a tough problem. First, we needed to find all the public APIs and their specifications - mostly OpenAPI files.<p>We used several strategies to find those:<p>- Crawl API repositories like apis.guru<p>- Crawl Github for openapi.json and openapi.yaml files<p>- A cool google dork<p>Those strategies enabled us to gather around ~20.000 OpenAPI specs.<p>Then lies the hard part of the problem:<p>We want to dynamically evaluate those APIs' security, performance, and reliability.<p>But APIs take parameters that are tightly coupled to the underlying business logic.<p>A naive automated way would not work: putting random data in parameters would likely not pass the API's validation layer, thus giving us little insight into the real API behavior.<p>Manually creating tests for each API is also not sustainable: it would take years for our 10-people team. We needed to do it in an automated way.<p>Fortunately, our main R&D efforts at Escape aimed to generate legitimate traffic against any API efficently.<p>That's how we developed Feedback-Driven API exploration, a new technique that quickly asses the underlying business logic of an API by analyzing responses and dependencies between requests. (see <a href="https://escape.tech/blog/feedback-driven-api-exploration/">https://escape.tech/blog/feedback-driven-api-exploration/</a>)<p>We originally developed this technology for advanced API security testing. But from there, it was super easy to also test the performance and the reliability of APIs.<p>How we ranked APIs?<p>Now that we have a scalable way to gather exciting data from public APIs, we need to find a way to rank them. And this ranking should be meaningful to developers when choosing their APIs.<p>We decided to rank APIs using the following five criteria:<p>- Security
- Performance
- Reliability
- Design
- Popularity<p>Security score is computed as a combination of the number of OWASP top 10 vulnerabilities, and the number of sensitive information leaks detected by our scanner<p>The performance score is derived from the median response time of the API, aka the P50<p>The reliability score is derived from the number of inconsistent server responses, either 500 errors or responses that are not conform with the specification<p>The Design score reflects the quality of the OpenAPI specification file. Having comments, examples, a license, and contact information improves this score<p>The popularity score is computed from the number of references to the API found online<p>If you are curious about your API's performance, you can ask us to index your own api for free at <a href="https://apirank.dev/submit" rel="nofollow">https://apirank.dev/submit</a>
Show HN: Plato – Airtable for your SQL database
Hi! I've been a member of HN for fifteen years so today I'm very excited to share Plato.<p>Plato is an Airtable-like interface for your Postgres or MySQL database. It's an admin panel for devs and non-devs alike to manage your DB. We see teams use Plato for customer support, customer success, ops, etc..<p>We built Plato because we think more people should be able to build and extend internal tools. We thought it was strange that even though low-code is supposed to democratize development, all of the low-code internal tool builders are marketed to engineers! Airtable is a familiar UI that fits the relational model well, so we've been inspired by their work. Even the engineers on our team use Plato quite a bit, since it's often easier than spinning up a SQL prompt.<p>Some features:<p>- Postgres and MySQL support<p>- Visual query controls (sorts, filters, hiding columns). No SQL.<p>- Joins by "expanding" foreign keys<p>- Virtual columns for tracking new data<p>- Auto-generated backlinks for one-to-many relationships<p>- Read-only locking for individual tables<p>- Virtual tables for sharing new views with your team<p>Plato today works on databases with a public IP (just whitelist our IP to connect), but we're soon rolling out an on-prem version. We can also set up an SSH tunnel for you if you contact us at team@plato.io.<p>We'd love to hear your feedback! Thanks.<p>- Michael
Show HN: Plato – Airtable for your SQL database
Hi! I've been a member of HN for fifteen years so today I'm very excited to share Plato.<p>Plato is an Airtable-like interface for your Postgres or MySQL database. It's an admin panel for devs and non-devs alike to manage your DB. We see teams use Plato for customer support, customer success, ops, etc..<p>We built Plato because we think more people should be able to build and extend internal tools. We thought it was strange that even though low-code is supposed to democratize development, all of the low-code internal tool builders are marketed to engineers! Airtable is a familiar UI that fits the relational model well, so we've been inspired by their work. Even the engineers on our team use Plato quite a bit, since it's often easier than spinning up a SQL prompt.<p>Some features:<p>- Postgres and MySQL support<p>- Visual query controls (sorts, filters, hiding columns). No SQL.<p>- Joins by "expanding" foreign keys<p>- Virtual columns for tracking new data<p>- Auto-generated backlinks for one-to-many relationships<p>- Read-only locking for individual tables<p>- Virtual tables for sharing new views with your team<p>Plato today works on databases with a public IP (just whitelist our IP to connect), but we're soon rolling out an on-prem version. We can also set up an SSH tunnel for you if you contact us at team@plato.io.<p>We'd love to hear your feedback! Thanks.<p>- Michael
Show HN: Construct Animate – our new browser-based animation tool
Show HN: Construct Animate – our new browser-based animation tool
Show HN: CodeGPT.nvim – ChatGPT plugin for Neovim
Show HN: CodeGPT.nvim – ChatGPT plugin for Neovim
Show HN: CodeGPT.nvim – ChatGPT plugin for Neovim
Show HN: CodeGPT.nvim – ChatGPT plugin for Neovim
Show HN: BBC “In Our Time”, categorised by Dewey Decimal, heavy lifting by GPT
I'm a big fan of the BBC podcast In Our Time -- and (like most people) I've been playing with the OpenAI APIs.<p>In Our Time has almost 1,000 episodes on everything from Cleopatra to the evolution of teeth to plasma physics, all still available, so it's my starting point to learn about most topics. But it's not well organised.<p>So here are the episodes sorted by library code. It's fun to explore.<p>Web scraping is usually pretty tedious, but I found that I could send the minimised HTML to GPT-3 and get (almost) perfect JSON back: the prompt includes the Typescript definition.<p>At the same time I asked for a Dewey classification... and it worked. So I replaced a few days of fiddly work with 3 cents per inference and an overnight data run.<p>My takeaway is that I'll be using LLMs as function call way more in the future. This isn't "generative" AI, more "programmatic" AI perhaps?<p>So I'm interested in what temperature=0 LLM usage looks like (you want it to be pretty deterministic), at scale, and what a language that treats that as a first-class concept might look like.
Show HN: BBC “In Our Time”, categorised by Dewey Decimal, heavy lifting by GPT
I'm a big fan of the BBC podcast In Our Time -- and (like most people) I've been playing with the OpenAI APIs.<p>In Our Time has almost 1,000 episodes on everything from Cleopatra to the evolution of teeth to plasma physics, all still available, so it's my starting point to learn about most topics. But it's not well organised.<p>So here are the episodes sorted by library code. It's fun to explore.<p>Web scraping is usually pretty tedious, but I found that I could send the minimised HTML to GPT-3 and get (almost) perfect JSON back: the prompt includes the Typescript definition.<p>At the same time I asked for a Dewey classification... and it worked. So I replaced a few days of fiddly work with 3 cents per inference and an overnight data run.<p>My takeaway is that I'll be using LLMs as function call way more in the future. This isn't "generative" AI, more "programmatic" AI perhaps?<p>So I'm interested in what temperature=0 LLM usage looks like (you want it to be pretty deterministic), at scale, and what a language that treats that as a first-class concept might look like.