Ask HN: What are some tools / libraries you built yourself?

A gpu accelerated neural network backpropagation lib: https://github.com/zbendefy/machine.academy

I built milkman[1], an alternative to postman because I wanted one tool to integrate with the whole web development stack. One tool that contains my SQL, rest and grpc calls to easily debug issues. Also nearly none of those kind of tools that existed supported SSE which I also use in my day to day work. [1] https://github.com/warmuuh/milkman

Edit: I love these threads. You read so many things and Frameworks and random stuff that you really learn in what silo you are actually living

Some stuff I've worked on recently:

- kcup[0] serves a single page over HTTP/S (there's a version in go but I don't work on that, only created it to compare initially)

- async-wait-for-promise[1] - a tiny npm package for waiting on a condition or timeout (README contains why the certain combination didn't already exist)

- mailtrain-form-post-sidecar[2] - a little sidecar container for mailtrain that accepts form POSTs for mailing list signups

- redis-bootleg-backup[3] - a tool for taking backups of small redis databases with only read access (KEYS *-based)

- maille[4] - a component framework for mithriljs

- postmgr[5] - a daemon for running & managing postfix, dovecot and other mail-adjacent software (haven't worked on this for 2 years, because better options like maddy[6], chasquid[7] and haraka[8] exist)

Unfortunately, most of the stuff I've worked on that I've open sourced lately is instructional/pattern-related, so that doesn't really fit this mold, but in the background I've been working on what might be my biggest project yet (remains to be seen if/when I'll open source it) -- readysetsaas, a truly no-code (you provide configuration only) saas company creation kit, somewhat similar to AWS's SaaS boost thing.

[0]: https://gitlab.com/mrman/kcup-rust

[1]: https://gitlab.com/mrman/async-wait-for-promise

[2]: https://gitlab.com/mrman/mailtrain-form-post-sidecar

[3]: https://gitlab.com/mrman/redis-bootleg-backup

[4]: https://mrman.gitlab.io/maille/

[5]: https://gitlab.com/postmgr/postmgr

[6]: https://maddy.email

[7]: https://blitiri.com.ar/p/chasquid/

[8]: https://haraka.github.io/

Since we're tooting our own horns here, I wrote a small Python Web API framework called pyotr [0]. Its core idea is that, when you have an OpenAPI specification of your Web service, it is trivial to use it for both validation and routing.

It actually consists of two projects (and I'm looking into making them more independent): the server component, which lets you set up your service using an OpenAPI spec and simply write a number of functions, each handling one operation; and the client component, which does the opposite by taking the spec and letting you call the service with simple constructs like client.operation_id().

[0] https://pyotr.readthedocs.io

I created 2 things which I'm really proud of, because they solve the exact problem in elegant way.

First one is ProxyAV [1] - reverse proxy that scans any uploaded file with ClamAV. That tool/microservice was created, because backend developers didn't have experience to work with antivirus on their side, so the "mitm proxy" way allows to integrate antivirus scanning without bothering backend devs, they always receive clean files

The second one is etke.cc [2] service. I love matrix, but self hosting of matrix homeserver requires good level of expertise, even for skilled sysadmins. I just wanted more people join matrix with their own homeservers, so etke.cc service is perfect solution to that problem - you want your own matrix homeserver - you order it on etke.cc - you get your matrix homeserver, on your domain, on your server, with full control of it.

[1] https://gitlab.com/rakshazi/proxyav

[2] https://etke.cc