I've made a thing! A new version of an UUID encoding I came up with 12+ years ago. There might even be one or two people here who remember me giving my first Tech Talk at work about this back then.

Next to the PostgreSQL version that I shared, I always had implementations in the languages I worked with, and I improved the encoding a bit further in the last years, and just published an implementation in Go:

https://github.com/sdassow/go-sort64id

I just released the first major update for the ULID unique ID generation library in over 8 years! I’ve been following it as a user for years, having even forked it for ulidx when it wasn’t being maintained. It’s fulfilling to not only see it updated (as I use it a lot), but having done so myself.

If you’re building a new feature and are about to reach for an ID generator (like UUID), you might consider trying ULIDs instead: https://github.com/ulid/javascript

Using #sourcehut is a lesson in itself
for all keys you upload to builds page you get a UUID that you use to indicate which secrets you want to use on that particular build … because secrets are global to your account. #SSH keys get saved on the .ssh directory with filename of the #UUID (see example below), and for files you can provide both the filename that will be used and the permissions of the file (following the numeric style of *nix systems)

My favorite hobby: reading EDN spec and finding examples where practice diverges from theory.

E.g. did you know that

.1

parses as a symbol?

Or that

:/

and

:///

are both valid keywords but

://

isn’t?

Also this:

#uuid "f-7-1-a-8"

is a perfectly fine UUID.

Anyway, have a good weekend!

In Deutschland gibt ja mehrere hunderttausend Pegel an Flüssen Seen und Meer

Da ist eine #UUID wichtig um sie auseinander zu halten

z.B. Worms am Rhein :
844a620f-f3b8-4b6b-8e3c-783ae2aa232a

Aufreger am Morgen

How can one get the #UUID of a #tbeam if using an the android #meshtastic app to control the T-beam via bluetooth?