Rawer

Under Construction

there are many to-dos

#

Semem

a new subproject seeded

The stuff below got messed up.

Recovered enough to continue, but to clear my head, a little timesaver -

hmm, wait - need a cat of my nginx sites-enabled...

There are #:todo bits I need to pull out of the past few day's entries here to go in their correct todo areas...

Today, something like :

  1. #:todo #:semem #:spike
  2. #:todo /home/danny/github-danny/hyperdata/workspaces/transmissions/todo/next-steps.md
  3. #:todo Verbo photo
  4. #:todo carving prep
  5. #:todo 1-page docs (Transmissions urgent)

I need to be keeping ClaudioB informed of what I'm working on, so around those #:transmissions next steps I need to bear that in mind. Also notes on AI tools I'm using/trying :

  • OpenAI API
  • Claude projects + API
  • Mistral API
  • cline
  • aider
  • []

etc.

Grr, lost a lot of time with node module stupidity.

#:todo add rule to #:um - failure is part of the process, but a goal is that things shouldn't fail more than once for the same reason

A thought crossed my mind on dogwalk, must-have base functions for processors :

message = expandLD(message, options); // enlarge the Logical Dimension/Linked Data
message = contractLD(message, options);
message = expandLM(message, options); // enlarge the Language Model dimension
message = contractLM(message, options);

Semem

#:semem

This morning Google's 'Discover' (on Chrome on Android) shortcircuited my morning reading in bed with a link to this from MarkTechPost : Meet Memoripy: A Python Library that Brings Real Memory Capabilities to AI Applications which led me to this on GitHub :

Memoripy is a Python library designed to manage and retrieve context-aware memory interactions using both short-term and long-term storage. It supports AI-driven applications requiring memory management, with compatibility for OpenAI and Ollama APIs. Features include contextual memory retrieval, memory decay and reinforcement, hierarchical clustering, and graph-based associations.

Long story short, it gives me a nice inroad into the practicals of the hybrid SPARQL+vector store bits high on my todo list.

First job, give this a place of its own. I've got lots of material related to the hybrid store scattered around, best I make an anchor. I've made a GitHub repo, now pop that in here :

cd /home/danny/github-danny/hyperdata/packages
git submodule add https://github.com/danja/semem.git semem

I'll put dev notes & docs as they emerge over on #:hyperdata.

First I need a plan, then port Memoripy from Python into Javascript.

#

Fool Danny

"Doctor doctor! It hurts when I do this...

I've had a recurring problem with npm installs etc, because in the bunch of submodules I have below hyperdata/packages I have hyperdata-static which currently needs to be pinned to node v16. Anything nearby chokes on node-gyp rebuild. In an idiot-party with Claude, ended up destroying hyperdata-static without fixing the gyp issue.

Stop doing that.

Continuing from /home/danny/github-danny/hyperdata/docs/postcraft/content-raw/journal/2024-11-18.md

# packages/hyperdata-desktop copied elsewhere first, just in case
cd ~/github-danny/hyperdata/
git submodule deinit -f packages/hyperdata-desktop
git rm -f packages/hyperdata-desktop
git commit -m "Removed submodule"
rm -rf .git/modules/packages/hyperdata-desktop

Hmm -

...
fatal: could not migrate git directory from '/home/danny/github-danny/hyperdata/packages/hyperdata-desktop/.git' to '/home/danny/github-danny/hyperdata/.git/modules/packages/hyperdata-desktop': Directory not empty
...

Dunno, try :

cd ~/github-danny/hyperdata/packages/semem
npm cache clean --force
rm -rf node_modules
npm install jasmine --save-dev
npm WARN ignoring workspace config at /home/danny/github-danny/hyperdata/packages/semem/.npmrc

ffs.

npm cache clean --force
rm -rf node_modules
nvm use default
npm install -g node-gyp
 npm install jasmine --save-dev

Finally!

I can't be arsed fixing hyperdata-desktop right now. Back to what I was trying to do 12 hours ago...

#

In Cline

Needs templates - plop

src/applications/postcraft

I want to be able to add further content group blocks into manifest.ttl files

danny.ayers.name/manifest.ttl

/home/danny/github-danny/postcraft/danny.ayers.name/public/home

#

Pingy-ping

While tidying up the other day I found an old phone. I wasn't sure whether or not to throw it, so put it on to charge. Broken screen. Now it keeps going pingy-ping.

  1. #:todo /home/danny/github-danny/hyperdata/workspaces/transmissions/todo/next-steps.md
  2. #:todo Verbo photo
  3. #:todo carving prep
  4. #:todo 1-page docs (Transmissions urgent)

AGAIN

But I have got past the annoying restructure problem with Transmissions, so can move on.

  • aider
  • cline
  • continue

APIs Qwen2.5 Tools: A 14B and 32B parameter model designed for general tool use and task completion

Qwen2.5 Coder Tools: A 1.5B and 7B parameter model specifically optimized for coding tasks

Qwen2.5 Tools: https://ollama.com/hhao/qwen2.5-tools

Qwen2.5 Coder Tools: https://ollama.com/hhao/qwen2.5-coder-tools

https://www.reddit.com/r/ClaudeAI/comments/1g3fhcp/save_money_on_claude_with_new_qwen25_specialized/


#

Brrr

NOTE TO SELF : GRDDL

it's chilly

four times I've changed the date in this' filename. It is still chilly

Aside from some priority #:todos I won't forget, I have :

  1. #:todo /home/danny/github-danny/hyperdata/workspaces/transmissions/todo/next-steps.md
  2. #:todo Verbo photo
  3. #:todo carving prep
  4. #:todo 1-page docs (Transmissions urgent)

No. 1. here is :

Restructure

A #:transmissions processor that changes the shape of a (JSON) message.

Notes in Transmissions Journal #:todo link, today in : /home/danny/github-danny/hyperdata/workspaces/transmissions/journal/2024-11-15.md

I need to use Restructure in two places right away :

  1. render messages from Claude's conversations.json
  2. get README.mds from all my GitHub repos
  3. tidy up #:postcraft, sort out publishing things.

For 1. I also needed a JSONWalker.

I got hopelessly confused...

I've spent way too long on these as necessary tasks, but it has useful as a learning experience.

At many points I was tempted to simply hack the code for 1. & 2. but at some point last week I broke the #:postcraft transmission in the parts that involve restructuring, so INSERT TOKI PONA

strange, the message is sometimes undefined...

Transmissions

I'm so desperate to automate this thing! My current process with Claude is close, just needs a little bit more push...

What I'm lacking in the #:transmissions dev is immediacy and integration, like you get in Smalltalk. MORE - it's not engaging me. I need to be told why I should do something.

Near future, I'll have #:hyperdata-desktop for that. In the interim...

I guess I should try Cline.