det.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon Server des Unterhaltungsfernsehen Ehrenfeld zum dezentralen Diskurs.

Administered by:

Server stats:

1.7K
active users

#Devlog

15 posts12 participants0 posts today
Continued thread

Permacommons #devlog 2025-08-19

This took a while to get working, but in my quest to automate all the things I managed to end up with a publish workflow for the `chabeau` crate that seems fairly sane.

1) Stage release on a release branch, using "cargo release"
2) If all checks pass, merge into main (protected branch)
3) Check on main detects new tag & publishes crate (assuming final pre-publication checks are happy)

Concurrency group ensures it only runs once.

Noice! Noticed my postgres instance was using 80% cpu, created a new index, changed the query a bit, and now it is using 0.2%! Damn... that's awesome! Going to let this table grow and see how this will scale.

Hi everybody. I think there's one more topic I haven't touched on yet, which also belongs in our series on raymarching technology. It's about creating arbitrary shapes using planes with various positions and rotations. So let's take a look at how we can compute the rendering of the so-called Platonic solids. #Godot #Godot4 #GodotEngine #GodotTips #shaders #devlog #indiedev
youtube.com/watch?v=xRMrwlOGfYE

a nice procedural way to generate palettes from a subset of colors could be to do a delaunay triangulation of them in YUV (or any better perceptual space), and then use the resulting edges to build gradients. the number of colors of each gradient should be proportional to the edge length.

Continued thread

Fixed my very first "buffer underflow" since the 90s 😅, refactored and improved code readability, doc comments, etc. I'm quite happy with the current status.

Next step: adding the logging system and removing all the debugging prints. Maybe I'll continue later, who knows... 🤓 😆

Permacommons #devlog 2025-08-13

Today was a bit of a side-quest into "how to print a version string".

The behavior I ended up with is:
- For dev builds, print detailed git version info
- For "cargo install" builds, print only basic build info
- Ensure we preserve support for VERGEN_IDEMPOTENT (suppress dates entirely) and SOURCE_DATE_EPOCH (reproducible builds).

(Still TBD: official release artifacts)