How I am prototyping playing around with #ActivityPub this time (with bonus #OCaml) for databases:
Basically I'm building a thin shim over the database API layer. This is both remarkably easy and remarkably weird in OCaml, so it makes for a good learning experience and gets me a little more comfortable with modules.
The first pass I'm just writing the basics with #sqlite3, later I'll go through and modify it to work with #PSQL and/or other options.
I really end up frustrated by both extremes of operator overloading in languages and language cultures.
Both the Java approach of "NEVER OVERLOAD THE OPERATORS" as well as the approach favored in #haskell and #ocaml of NO GODS NO MASTERS OPERATOR OVERLOADING FOR ALL.