Finding popular keywords or tags is what twitter’s trends are (other than a means to manipulate public opinion and introduce artificial trends by paying good cash). While I think having a “trends” feature tends to introduce more problems than the value it provides for discovery, I wanted to figure out how I’d do it before deciding not to.
Elasticsearch aggregation to find most popular tags over time
Suunto 9 Baro first impressions
I wrote about how I was considering getting a new watch, and a while back I actually put that into action and got a Suunto 9 Baro. I wanted to try something not Garmin to have a more reliable point of view.
Getting the Suunto 9 Baro up and running wasn’t hard, but it wasn’t seamless either. I paired the device with my phone before installing the Suunto app, after which the app wasn’t able to “pair” with it. I had to unpair the smartwatch once and redo it from the app. Weird stuff.
It’s a very different beast from the Garmin Instinct. First of all, it’s much bigger, but I don’t think it’s too heavy or so big as to get in the way. It’s a full-fledged smartwatch with a touchscreen, so my first thing to do was to get a protective film so the glass doesn’t get all scratchy and/or smudgy. It also means that it can show notifications and stuff, which can get pretty noisy if there are too many. Of course it can be configured, but it has to be configured.
Dealing with circular dependencies in Clojure
While working on stuff (of course in Clojure), I kept running into problems with namespaces having circular dependencies. For example I’d have an
app.router namespace that defines the, uh, routes. I’d have an
app.url namespace that contains helper functions to generate absolute URLs based on route data (so it depends on
app.router). I’d have an
app.views namespace that uses those URL helpers (thus depending on
app.url), and these views would be referenced in the routes so
app.router would require
This completes the dependency circle and is the beginning of my journey. There are a bunch of ways to deal with circular dependencies in Clojure, but I won’t go in-depth about all of them.
A way to extract an image from Firefox
The problem I faced: I was scrolling through a hashtag‘s timeline in Tweetdeck, when I spotted a nice image. I wanted to retweet it, but that failed: turns out the tweet was deleted in the meanwhile. This usually means that either the artist themselves deleted the tweet for some reason, or it was stolen in the first place and (by some miracle) it was moderated.
In this case it seems to have been the latter, so finding the image through the author’s profile was not an option. As Tweetdeck displays images as CSS backgrounds in the timeline, right-click “Open image in new tab” was not an option. Since the tweet was deleted, its URL was invalidated too, so I couldn’t give that to Saucenao or similar to find matches either.
However, while digging through the Firefox Dev Tools, I noticed that the context menu when right clicking the URL of the
background-image had an item “Copy image data URL”. This turned out to be just what I needed.
Pasting the copied (data blob) URL to the address bar I got the image that I could magnify so that I could decipher the artist’s signature on it. (It turned out to have been a partial image so Saucenao couldn’t help either.) After a few tries I found the artist’s profile and there the original post. Yay.
Adding Grafana annotations based on Flux CD events
Earlier this year I wrote about adding Grafana annotations based on Argo CD events. Since this year I actually got around testing out Flux some more, it was natural to follow up with adding some Grafana annotations based on Flux events.
Clojure multimethods and derivation
I’ve known about Clojure multimethods of course, but I never really used them much. I didn’t really have data that I’d need polymorphism like multimethods to handle, and when I did need something like that I’d use protocols. However protocols dispatch based on class, so when I faced the problem of handling ActivityPub objects that are all maps, it was time for
defmulti to save the day.
Structured logging in Clojure
The first time I ran into “structured logging” was way, way back when I first started working on kitsune. Back then I went with the approach of using a Logback Formatter (the JacksonJsonFormatter) to log Clojure maps as JSON. This was nice because I didn’t have to do anything to “transform” the logs further, but had the quite significant downside that logs weren’t really human readable anymore. This plus that that log processors like Loki and CloudWatch can easily parse huge amounts of “traditional” text logs made me pretty much forget about structured logging until recently.
That is until in a thread on the clojurians slack about logging someone mentioned mulog, a structured logging library that caught my attention. I guess maybe from a traditional Clojure background it would’ve been natural to end up with taoensso/timbre at this point, but I never did that bit (though I do have it as an indirect dependency).
The Weave GitOps UI for Flux
Unlike Argo, Flux has no built-in UI. CD tools should be invisible most of the time, just quietly running in the back, getting changes in the cluster. This is fine for “most of the time” when there are no changes to the applications I’m making myself or the cluster itself. It can just look at the various helm charts and other (git) sources and deploying the changes as configured. It’s nice that I can be sure that my cluster has the latest possible versions of everything running within 10-15 minutes of release (depending on the Flux
interval configured) without ever touching
How do foreign keys work in MariaDB system versioned tables?
When I read about the system versioned (and bitemporal) tables in MariaDB, I was both surprised and delighted. This kind of data versioning is thought of as standard in the “immutable” databases that are big in Clojureland, such as Datomic and XTDB. On the other hand, these databases in Clojureland are usually EAVT based and not the “usual” relational kind. After a little thinking I could think of a bunch of really tricky issues that could arise from system versioning (eg having a by-default immutable log of all changes to some piece of data) in a relational context. The first being foreign keys.
If you create a foreign key in MariaDB without any further specifiers, it assumes
ON UPDATE RESTRICT ON DELETE RESTRICT, meaning no referenced key could be changed and no referenced row could be deleted. Just consider this: if there’s a row in some table referencing a row in another, system versioned table, can the row in the system versioned “parent” table be deleted? After all the referenced version of the row will still exist… Or in a similar scenario if the “child” row is system versioned and updated to now reference a different row, will both of those referenced rows be
RESTRICTed? After all, both referencing rows will still exist… Of course I had to try.
Hot reloading and reitit in the frontend
Ever since I first ran into the Metosin libraries, I’ve been using many of them. One of the most known and used of those is probably reitit, a routing library that can be used both on the server and in the browser. Recently I’ve had more opportunities using ClojureScript in the browser, and I noticed something that was confusing for a few moments.
Tagsale anime art beer blog clojure code coffee deutsch emo english fansub filozófia food gaming gastrovale geek hegymász jlc kaja kultúra language literature live magyar movie másnap politika rant sport suli szolgálati közlemény travel társadalom ubuntu university weather work zene érettségi 日本 日本語 百名山 艦これ 軽音