Mauve 👁💜 @mauve@mastodon.mauve.moe

@tofu It's like if XMPP was JSON

@fleeky More like an octopus with many tentacles that have some specialized talent 🐙

High key considering reworking the LLM stuff in Agregore to be a protocol handler since injecting new JS APIs into iframes hasn't been working. 😅

Not sure what to make the URL scheme look like. The path should be ollama or openAI style, but what would I put in the hostname?

Love when my cats get their evening zoomies and sprint accross the entirety of my home and propel themselves over the bed. They're like torpedos which manage to use my stomach as a spring board for an extra boost.

BTW for folks into #localfirst #ai , come join the userless-agents Matrix channel to talk about approaches and use cases!

https://matrix.to/#/#userless-agents:mauve.moe

I wiped it. 🤪

I forgot my Apple password and now my mac mini is a locked box. 🙃

"reverse cyborg" is an exciting concept. Machines yearning to graft flesh onto their frame.

Squirming 🐍

Made another lil #agregore app today. This combines the web's SpeechSynthesis API with Agregore's LLM APIs to talk to a spooky LLM with it responding with a voice as well as text.

hyper://816idd9ddxq8asy68sya1y3du3nyipiszcr6tfyq66x47ha3jxuy/speak_ai.html

Make sure to set up Speech Syntehsis on your machine if it doesn't work initially. On linux I had to set up speech-dispatcher and espeak-ng. This should work fully offline, too!

IMO Ollama's streaming API is much nicer, but here's an example repo for streaming #OpenAI inference from a request with zero dependencies in #JavaScript.

https://github.com/RangerMauve/openai-streaming-generator

Using server sent events in an HTTP POST is the sort of evil I wouldn't even do. 🤪

NDJSON would have been nicer IMO

Merkle-DAGs are a neat concept. But honestly `last know writer + writer lamport clock` is a pretty good timestamp too.

I guess I'm thinking documents in a sort of tree like `root/page/section/subsection/paragraph0...n` where each leaf is a value + a clock for last write wins.

Writer set guarded by something like keyhive or a cheap append only set of public keys if you're lazy.

https://arxiv.org/pdf/2004.00107

https://www.inkandswitch.com/keyhive/notebook/

Even though last write wins registers are the most practical it feels like the biggest cop-out in terms of conflict resolution. I get vector clocks and merkle clocks are more expensive but it feels like we should care about clock drift and causality more. I guess GUN.js had it right all along with using wallclocks but ignoring updates too far in the future. :P