Open source spinoffs from Tarsnap: https://www.tarsnap.com/open-source.html scrypt: Because the world didn't have any strong password-based key derivation functions. spiped: Because using stunnel or ssh tunnelling to connect to servers is gross . kivaloo: Because I wanted a high performance KV store optimized for small values (e.g. 40 bytes) rather than larger "items" (each containing multiple key-value pairs) or "bl…
Can you elaborate on what makes stunnel or ssh tunneling "gross"? Is it the network overhead they add or is it the complexity of the protocol, or is it something else?
Ask HN: What are some tools / libraries you built yourself?
271–280 of 617 posts
Re: Ask HN: What are some tools / libraries you built yourself?
#272I wrote a Python library for model based systems engineering, because existing tools (e.g. Simulink) don't coexist nicely with mainstream version control systems, and don't generally have such a nice interface for system level meta-programming and design optimisation.
Re: Ask HN: What are some tools / libraries you built yourself?
#273Re: Ask HN: What are some tools / libraries you built yourself?
#274Last year I built Recut[0], a native Mac app that helps speed up video editing by automating the rough-cut process. It finds silence, gaps, and pauses and removes them, creating a cut list that you can import into editors like ScreenFlow, Final Cut, Premiere and Resolve. Here’s the Show HN [1] from a couple months ago. I built it because I was making screencasts and cutting out silence + mistakes was 90% of my editin…
Re: Ask HN: What are some tools / libraries you built yourself?
#275I've written jql[0], an alternative to jq with much less syntax (being lispy) and much easier to use for me. The project may seem dead to some, but I'm using it daily, it's just finished. [0]: https://github.com/cube2222/jql
Re: Ask HN: What are some tools / libraries you built yourself?
#276Re: Ask HN: What are some tools / libraries you built yourself?
#277> Checkbot is a Chrome extension that tests 100s of pages at a time to find critical SEO, speed and security problems before your users do. Test unlimited sites as often as you want including local development sites to find and eliminate broken links, duplicate content, invalid HTML/CSS/JavaScript, insecure pages, redirect chains and 50+ other common website problems.
I build this to automate audits I kept having to do manually while doing frontend work. I also liked the idea of it helping to teach people about web best practices, so tried to make it easy to use with minimal jargon explanations (see https://www.checkbot.io/guide/).
It written with Vue + TypeScript + Firebase + Paddle.
There's a free tier with no sign-up required - give it a quick try on one of your own pages and it'll usually find something to fix you didn't know about.
Re: Ask HN: What are some tools / libraries you built yourself?
#278Re: Ask HN: What are some tools / libraries you built yourself?
#279Re: Ask HN: What are some tools / libraries you built yourself?
#280It's a Python library giving utilities to handle data in Continual Learning, a subfield of Machine/Deep-learning where data comes incrementally. It's made to be super simple to understand, and can be used in fast prototyping on a notebook to large codebase.
There are others actors in the field that came atfer us and do more ads about their slightly similar library, but we manage to produce something useful to many PhD students, so that's a win for me.