I am actively looking for ways to get paid for my work on , and . Any advice welcome.


I am too lazy to do some command-line-fu based on aria2c, split, and nomunofu, so I rented another server at online.net with a big enough disk to hold the flat wikidata files and the database for 40 euros. When the database will be ready, I will upload it to archives.org.

This morning I managed to create a portable and self-contained tarball with everything required to run the thing on amd64, thanks to .

In two hours, I will be able to start the import process on the server.

I am very excited about this spin-off called nomunofu: github.com/amirouche/nomunofu

I am trying to load in the database it will at least take a month, since I don't have a big enough server, I am "streaming" the import process.

I feel the need to cycle back to the work. With the work I have done on I got new insights and new perspectives for datae.

My goal was to work on babelia at least until the end of the year. I am also very excited with the idea to poke again around , and versioned data.

I have finished procrastinating by doing things that are NOT part of my main focus namely .

What will happen next? Who knows?!

Time for coding ! The plan for today is:

- Get together a (basic) pre-fork thread HTTP server,

- Read more about SPARQL 1.1 semantic,

- Maybe start the frontend stuff.

I figured a new way to store history significance in .

What I will explain starts with `history-` in the following file git.sr.ht/~amz3/chez-scheme-ar

Right now the code does store the DAG history in a triplestore and CACHE history significance of each branch in a branch specific tuple to avoid to do multiple calls to the database to rebuild the history of the whole branch and hence be able to recompute history significance measure of each change, for every time travelling query...

stores changes, add and deletion, between versions of the and possibly use a snapshot to speed up querying of the last version (aka. the HEAD). To resolve conflicts between branches, it seems there is not other way but to copy the relevant changes in a merge commit.

I have been working almost all day on the functional database, I was talking previously named . Unlike what is written in the README. I think, that my future self will not commit to build a competitor, instead I will enjoy the full shenanigan of and try to build something that requires less frontend work.

Functional CafΓ©

functional.cafe is an instance for people interested in functional programming and languages.