Hacking a Philips Sonicare Toothbrush
29 by PikelEmi | 7 comments on Hacker News.
Tuesday, May 30, 2023
New top story on Hacker News: Show HN: I open sourced the QR designer from my failed startup
Show HN: I open sourced the QR designer from my failed startup
27 by koch | 4 comments on Hacker News.
My designer is somewhat special, if I do say so myself, as it allows you to put arbitrary designs in the middle area of the QR while still being totally scannable.
27 by koch | 4 comments on Hacker News.
My designer is somewhat special, if I do say so myself, as it allows you to put arbitrary designs in the middle area of the QR while still being totally scannable.
Monday, May 29, 2023
Sunday, May 28, 2023
Saturday, May 27, 2023
Friday, May 26, 2023
Thursday, May 25, 2023
New top story on Hacker News: Show HN: Hacker News in Slow Italian - AI-generated podcast (with code)
Show HN: Hacker News in Slow Italian - AI-generated podcast (with code)
13 by lakySK | 9 comments on Hacker News.
There are plenty of podcasts to listen to some slow basic Italian, but often they just talk about random things I'm not that interested in. Nothing a few hours of tinkering with Python cannot solve these days! Introducing Hacker News in Slow Italian. Each episode is generated automatically, using GPT4 API to summarise the top articles on Hacker News and then fed to Play.ht for text-to-speech. The (very short) code is available on Github: https://ift.tt/puSh8Ox
13 by lakySK | 9 comments on Hacker News.
There are plenty of podcasts to listen to some slow basic Italian, but often they just talk about random things I'm not that interested in. Nothing a few hours of tinkering with Python cannot solve these days! Introducing Hacker News in Slow Italian. Each episode is generated automatically, using GPT4 API to summarise the top articles on Hacker News and then fed to Play.ht for text-to-speech. The (very short) code is available on Github: https://ift.tt/puSh8Ox
Wednesday, May 24, 2023
New top story on Hacker News: Ask HN: How does archive.is bypass paywalls?
Ask HN: How does archive.is bypass paywalls?
33 by flerovium | 25 comments on Hacker News.
If it simply visits sites, it will face a paywall too. If it identifies itself as archive.is, then other people could identify themselves the same way.
33 by flerovium | 25 comments on Hacker News.
If it simply visits sites, it will face a paywall too. If it identifies itself as archive.is, then other people could identify themselves the same way.
Tuesday, May 23, 2023
DeSantis Set to Announce 2024 Run on Twitter With Elon Musk
By BY SHANE GOLDMACHER, MAGGIE HABERMAN, RYAN MAC AND NICHOLAS NEHAMAS from NYT U.S. https://ift.tt/ZhuWKSk
via IFTTT
New top story on Hacker News: Show HN: Accelerated Docker builds on your local machine with Depot (YC W23)
Show HN: Accelerated Docker builds on your local machine with Depot (YC W23)
23 by jacobwg | 13 comments on Hacker News.
Hello HN! We just launched a new feature we built at Depot that accelerates Docker image builds on your local machine in a team environment, and we wanted to share some of the details with you all. The launch blog post: https://ift.tt/F54gbse Depot is a hosted container build service - we run fully managed Intel and Arm remote build machines in AWS, with large instance sizes and SSD cache disks. The machines run BuildKit, the build engine that powers Docker, so generally anything you can `docker build`, you can also `depot build`. Most people use Depot in CI, and you could also run `depot build` from your local machine as well. That would perform the build using the remote builder, with associated fast hardware and extra fast datacenter network speeds. But then to download the container back to your local machine, BuildKit would transfer the entire container back for every build, including base image layers, since BuildKit wasn’t aware of what layers already existed on your device. The new release fixes this! To make it work, we replaced the BuildKit `--load` by making the Depot CLI itself serve the Docker registry API on a local port, then asking Docker to pull the image from that localhost registry. The CLI in turn intercepts the requests for layers and fetches them directly using BuildKit’s content API. This means Docker only asks for the layers it needs! This actually speeds up both local builds, where you only need to download changed layers, as well as CI where it can skip building an expensive tarball of the whole image every time! We ran into one major obstacle when first testing: the machine running the Docker daemon might not be the same machine running the `depot build` command. Notably, CircleCI has a remote Docker daemon, where asking it to pull from localhost does not reach the CLI’s temporary registry. For this, we built a "helper" container that the CLI launches to run the HTTP server portion of the temporary registry - since it’s launched as a container, it does run on the same machine as the Docker daemon, and localhost is reachable. The Depot CLI then communicates with the helper container over stdio, receiving requests for layers and sending their contents back using a custom simple transport protocol. This makes everything very efficient! One cool part about the remote build machines: you can share cache with anyone on your team who has access to the same project. This means that if your teammate already built all or part of the container, your build just reuses the result. This means that, in addition to using the fast remote builders instead of your local device, you can actually have cache hits on code you haven’t personally built yet. We’d love for you to check it out, and are happy to answer any questions you have about technical details! https://ift.tt/FH56oe4
23 by jacobwg | 13 comments on Hacker News.
Hello HN! We just launched a new feature we built at Depot that accelerates Docker image builds on your local machine in a team environment, and we wanted to share some of the details with you all. The launch blog post: https://ift.tt/F54gbse Depot is a hosted container build service - we run fully managed Intel and Arm remote build machines in AWS, with large instance sizes and SSD cache disks. The machines run BuildKit, the build engine that powers Docker, so generally anything you can `docker build`, you can also `depot build`. Most people use Depot in CI, and you could also run `depot build` from your local machine as well. That would perform the build using the remote builder, with associated fast hardware and extra fast datacenter network speeds. But then to download the container back to your local machine, BuildKit would transfer the entire container back for every build, including base image layers, since BuildKit wasn’t aware of what layers already existed on your device. The new release fixes this! To make it work, we replaced the BuildKit `--load` by making the Depot CLI itself serve the Docker registry API on a local port, then asking Docker to pull the image from that localhost registry. The CLI in turn intercepts the requests for layers and fetches them directly using BuildKit’s content API. This means Docker only asks for the layers it needs! This actually speeds up both local builds, where you only need to download changed layers, as well as CI where it can skip building an expensive tarball of the whole image every time! We ran into one major obstacle when first testing: the machine running the Docker daemon might not be the same machine running the `depot build` command. Notably, CircleCI has a remote Docker daemon, where asking it to pull from localhost does not reach the CLI’s temporary registry. For this, we built a "helper" container that the CLI launches to run the HTTP server portion of the temporary registry - since it’s launched as a container, it does run on the same machine as the Docker daemon, and localhost is reachable. The Depot CLI then communicates with the helper container over stdio, receiving requests for layers and sending their contents back using a custom simple transport protocol. This makes everything very efficient! One cool part about the remote build machines: you can share cache with anyone on your team who has access to the same project. This means that if your teammate already built all or part of the container, your build just reuses the result. This means that, in addition to using the fast remote builders instead of your local device, you can actually have cache hits on code you haven’t personally built yet. We’d love for you to check it out, and are happy to answer any questions you have about technical details! https://ift.tt/FH56oe4
Monday, May 22, 2023
Sunday, May 21, 2023
Saturday, May 20, 2023
Friday, May 19, 2023
Thursday, May 18, 2023
Wednesday, May 17, 2023
New top story on Hacker News: Show HN: Speeding up the code-test cycle for Java developers
Show HN: Speeding up the code-test cycle for Java developers
27 by artpar | 1 comments on Hacker News.
Hello HN, I am Parth. In my experience, the current form of testing automation takes too long. To solve this, I am creating a developer tool to speed up the code-test cycle for Java developers. It has two main parts: Direct Invoke - lets you call any Java function directly, without the need to execute the whole call hierarchy. (e.g. an HTTP endpoint) In my normal coding workflow, I use the “Evaluate Expression” feature inside IntelliJ IDE. I usually put a breakpoint somewhere in the code and after hitting the breakpoint by calling an HTTP api, let the execution remain paused while I explore and see the return values of functions. “Evaluate Expression” was quite useful in exploring new codebases and checking return values of my own functions as a sanity test. The direct invoke feature implements the same functionality without needing to hit a breakpoint. Now, I can just navigate to any function in the editor and execute it. The parameter values are input as JSON and deserialize to an object of the required class instances. Atomic Run - lets you hot-reload the code changes and highlights the difference in the return values of the changed function before and after the hot-reload. I feel Atomic Run has the potential of replacing unit test cases, but there is a long way to go. I am thinking of implementing - Option for mocking dependency calls: We want to give the developer more control over the testing environment by allowing them to mock downstream dependency calls. - Customizing assertions: Not all differences in return values indicate breaking changes. Assertions should be flexible to accommodate non-breaking changes. - Workflow to save this data to a file (thinking something like JSON based fixtures): making it easier to organize and reuse test data. This plugin is still in the early stages, so we'd appreciate your help in ironing out any bugs you come across. Get in touch with me on my discord channel. To try it out, install Unlogged from the IntelliJ Marketplace and start your java application using the java agent (the plugin has instructions to download) Link to try the plugin: https://ift.tt/5zlNHTW
27 by artpar | 1 comments on Hacker News.
Hello HN, I am Parth. In my experience, the current form of testing automation takes too long. To solve this, I am creating a developer tool to speed up the code-test cycle for Java developers. It has two main parts: Direct Invoke - lets you call any Java function directly, without the need to execute the whole call hierarchy. (e.g. an HTTP endpoint) In my normal coding workflow, I use the “Evaluate Expression” feature inside IntelliJ IDE. I usually put a breakpoint somewhere in the code and after hitting the breakpoint by calling an HTTP api, let the execution remain paused while I explore and see the return values of functions. “Evaluate Expression” was quite useful in exploring new codebases and checking return values of my own functions as a sanity test. The direct invoke feature implements the same functionality without needing to hit a breakpoint. Now, I can just navigate to any function in the editor and execute it. The parameter values are input as JSON and deserialize to an object of the required class instances. Atomic Run - lets you hot-reload the code changes and highlights the difference in the return values of the changed function before and after the hot-reload. I feel Atomic Run has the potential of replacing unit test cases, but there is a long way to go. I am thinking of implementing - Option for mocking dependency calls: We want to give the developer more control over the testing environment by allowing them to mock downstream dependency calls. - Customizing assertions: Not all differences in return values indicate breaking changes. Assertions should be flexible to accommodate non-breaking changes. - Workflow to save this data to a file (thinking something like JSON based fixtures): making it easier to organize and reuse test data. This plugin is still in the early stages, so we'd appreciate your help in ironing out any bugs you come across. Get in touch with me on my discord channel. To try it out, install Unlogged from the IntelliJ Marketplace and start your java application using the java agent (the plugin has instructions to download) Link to try the plugin: https://ift.tt/5zlNHTW
Tuesday, May 16, 2023
Monday, May 15, 2023
Sunday, May 14, 2023
New top story on Hacker News: Unofficial Turkish Election Results Show an Erdogan Lead
Unofficial Turkish Election Results Show an Erdogan Lead
4 by solar_warehouse | 1 comments on Hacker News.
4 by solar_warehouse | 1 comments on Hacker News.
Saturday, May 13, 2023
Friday, May 12, 2023
Thursday, May 11, 2023
Wednesday, May 10, 2023
Tuesday, May 9, 2023
New top story on Hacker News: Show HN: Engineering Book Club
Show HN: Engineering Book Club
3 by miguelbemartin | 1 comments on Hacker News.
An online community that enjoys reading and discussing engineering books together.
3 by miguelbemartin | 1 comments on Hacker News.
An online community that enjoys reading and discussing engineering books together.
Monday, May 8, 2023
Sunday, May 7, 2023
Saturday, May 6, 2023
Friday, May 5, 2023
Job gains in April reverse cooling trend.
By BY LYDIA DEPILLIS from NYT Business https://www.nytimes.com/live/2023/05/05/business/jobs-report-economy-april/us-employers-added-253000-jobs-in-april?partner=IFTTT
via IFTTT
Thursday, May 4, 2023
Wednesday, May 3, 2023
Federal Reserve Raises Interest Rates by Another Quarter Point
By BY THE NEW YORK TIMES AND THE ASSOCIATED PRESS from NYT Business https://ift.tt/OMHhI1A
via IFTTT
What to See in N.Y.C. Galleries in May
By BY ROBERTA SMITH, MARTHA SCHWENDENER, JOHN VINCLER, TRAVIS DIEHL AND ARTHUR LUBOW from NYT Arts https://ift.tt/e0RBlQo
via IFTTT
