Our great sponsors
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Replaceator
Command line tool that generates files from a template file, a replace pattern (word) and a list of words
-
-
xbattbar3
A simple utility that shows how charged your device's battery is by displaying it as a colored line at the bottom of your screen. While the laptop is plugged in, the line is blue, and when it is on battery mode, it transitions smoothly from green to yellow (1/2) to red (empty).
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
I just open sourced (a few hours ago) the way I build the static pages for the documentation, blog, and website of my product.
https://github.com/uxtely/js-utils/tree/main/static-pages-bu...
Shpotify is a shell script that allows you to control Spotify from the command line: https://github.com/hnarayanan/shpotify
The first version of it I wrote in a couple of hours.
And then it went on to be quite popular and has lived a life of its own.
Looking back it's probably for those not using a good text editor + not knowing regex, but it was fun, and useful to me at the time.
https://github.com/BaptisteV/Replaceator/tree/master/Replace...
Around April 2020 I identified a project need for an "inverted search engine" - a system that would accept documents (recipe ingredient lines, like "three large onions") as input, and would match those against a dataset of terms (ingredient names, like "tofu" or "tomato").
That would have been possible with a feature like percolation[1] in Elasticsearch, but I felt that the overhead of maintaining state (percolator queries) by using a network service would be excessive and that building an in-process alternative would be feasible.
The result is hashedixsearch[2], a pure-Python search engine library with support for stemming, synonyms and a few other features[3] to support the use-case.
It builds upon inverted index support provided by the hashedindex[4] library.
[1] - https://www.elastic.co/guide/en/elasticsearch/reference/curr...
[2] - https://pypi.org/project/hashedixsearch/
[3] - https://github.com/openculinary/hashedixsearch/blob/6980ee63...
[4] - https://github.com/michaelaquilina/hashedindex/
Around April 2020 I identified a project need for an "inverted search engine" - a system that would accept documents (recipe ingredient lines, like "three large onions") as input, and would match those against a dataset of terms (ingredient names, like "tofu" or "tomato").
That would have been possible with a feature like percolation[1] in Elasticsearch, but I felt that the overhead of maintaining state (percolator queries) by using a network service would be excessive and that building an in-process alternative would be feasible.
The result is hashedixsearch[2], a pure-Python search engine library with support for stemming, synonyms and a few other features[3] to support the use-case.
It builds upon inverted index support provided by the hashedindex[4] library.
[1] - https://www.elastic.co/guide/en/elasticsearch/reference/curr...
[2] - https://pypi.org/project/hashedixsearch/
[3] - https://github.com/openculinary/hashedixsearch/blob/6980ee63...
[4] - https://github.com/michaelaquilina/hashedindex/
I depend on my battery monitoring tools every day (xbattbar[1] for X and wattbar[2] for Wayland), and each of those was written over about two days time.
However, the coolest thing would have to be the project I'm in the middle of now, but it requires some explanation. At Hackerspace.gent, the center of the lounge area is Bloembak[3], a 1x1m table with a 32x32 pixel display covering its surface. During a discussion at a local bar with its creator, I decided it would be absolutely brilliant to be able to run shaders on it. So in my spare time over the last week, I wrote an interpreter for SPIR-V shaders to check my understanding, and then over the course of about 2 days, I rewrote the entire thing to target LLVM. While it's not finished (I only implement ~2/3 of the opcodes in SPIR-V and 1/10 of GLSL.std.450), it's already sufficient to run quite a few shaders off shadertoy at a reasonable framerate.
[1] https://github.com/thequux/xbattbar3
This is my most recent effort which took a few hours.
K8s debugging thing which I affectionately call kubebkwd to contrast with kubefwd. Covers the main use case of telepresence that I was interested in - i.e. proxying to a local instance from a local k8s cluster like docker-desktop. Does it without any special localhost network configuration other than what is set up with docker-desktop or other local k8s environments by default and only makes changes in the cluster so hopefully will be more robust to host OS configuration than telepresence, which I've had problems with. But be warned it's quite hacky, barely tested and doesn't clean up after itself, here be dragons, etc. (just different ones).
https://github.com/captainbland/kubebkwd