😬 Apologies for way too much news on "people using AI for porn" this morning. (although... the identities of everyone buying AI porn accidentally exposed is interesting, LOL)
The vitriol, and - honestly - ignorance around LLM-based "AI" is starting to fill my feeds from normally sane and technologically literate people.
You should be able to see through the hype and misuse. LLMs aren't encyclopedias - they're tools that are able to manipulate data of various sorts in ways that are very similar to how humans do it.
Yes, I compare LLMs to human brains. It's not the same as saying they're conscious (yet) - but the way LLMs work is apparently in many ways similar to how our brains work.
One fascinating insight into that comes from research done on what happens to the ability of LLMs to recall information as they are exposed to large and larger corpuses. Apparently they're better at recalling the early and late information, whilst starting to lose some in the middle.
In human psychology we call that the primacy and recency effect - because our brains do the same.
LLMs are absolutely awesome for a wide variety of tasks (and we have by no means found them all). Every second you spend not understanding this is a second on the way to your own irrelevance (if these tools would aid someone in your chosen area of work) or to become a grumpy old person yelling at clouds.
LLaVA (Large Language-and-Vision Assistant) was updated to version 1.6 in February. I figured it was time to look at how to use it to describe an image in Node.js. LLaVA 1.6 is an advanced vision-language model created for multi-modal tasks, seamlessly integrating visual and textual data. Last month, we looked at how to use the official Ollama JavaScript Library. We are going to use the same library, today.
Basic CLI Example
Let’s start with a CLI app. For this example, I am using my remote Ollama server but if you don’t have one of those, you will want to install Ollama locally and replace const ollama = new Ollama({ host: 'http://100.74.30.25:11434' }); with const ollama = new Ollama({ host: 'http://localhost:11434' });.
To run it, first run npm i ollama and make sure that you have "type": "module" in your package.json. You can run it from the terminal by running node app.js <image filename>. Let’s take a look at the result.
Its ability to describe an image is pretty awesome.
Basic Web Service
So, what if we wanted to run it as a web service? Running Ollama locally is cool and all but it’s cooler if we can integrate it into an app. If you npm install express to install Express, you can run this as a web service.
The web service takes posts to http://localhost:4040/describe-image with a binary body that contains the image that you are trying to get a description of. It then returns a JSON object containing the description.
I guess making money somewhat honestly by having customers that actually pay for a service with at least some guarantees of privacy and safety is not as lucrative as having an open platform network where people are tricked into giving out all their data while they are spied upon for whatever reasons.
I just finished a productive Copilot session on a complex programming task. I came up with much of the algorithms, and wrote a lot of the code, and had to guide it a lot throughout, but credit where due, Copilot did make small but meaningful contributions along the way.
Overall, not a pair programmer but someone useful to talk to when WFH alone on complex tasks.
Enough for Copilot to earn a ✋🏽. And I like how it responded to that. It has got that part down. 😉
When you choose to use an #ML#LLM foundation model, you accept the risk management decisions made by the vendor without your input. Wonder what they are? Read this #MLsec paper from #IEEE computer.
The MLX is Apple's framework for machine learning applications on Apple silicon. The MLX examples repository provides a set of examples for using the MLX framework. This includes examples of:
✅ Text models such as transformer, Llama, Mistral, and Phi-2 models
✅ Image models such as Stable Diffusion
✅ Audio and speech recognition with OpenAI's Whisper
✅ Support for some Hugging Face models
Someone actually built a Chrome extension to "Hide annoying Google AI Overviews". LOL. Right now it only has 2,000 users, but I wouldn't be surprised if it reaches millions in a few months when SGE (Search Generative Experience) will be rolled out globally. https://chromewebstore.google.com/detail/hide-google-ai-overviews/neibhohkbmfjninidnaoacabkjonbahn Duckduckgo is also releasing similar tech using AI .
@nixCraft it would be better to prevent the LLM results from being generated altogether. That would not just save us from the #LLM crap but also prevent the #CO2 emissions being created at all (maybe).
•This• is the compelling #LLM use case for me. If I use a translator to write messages in French I'm not forced to come up with an initial attempt and I lose the learning aspect of that.
If instead I put something into ChatGPT and it not only corrects but explains what my mistakes were that's a huge win in terms of learning from your mistakes.
(I still don't trust the thing 100% but it's also not a high stakes situation – I'm not engaging in a nuclear arms treaty after all 😅)
Fix your shitty autocorrect! There’s no such thing at “there’re” so quit putting it into my content.
And how come I get a word suggestion as I type, I click on it, and an entirely different word is inserted that wasn’t even one of the options offered - sometimes not even an English word?!
If you pick up one of the #Nvidia Orin boards, definitely get an SSD to go along with it. While it can run off an SD card, you’re going to run out of space quickly, and you’ll see a performance hit on complex tasks (like running a local #LLM). #EdgeAI#ai
A thing that worries me a bit is with AI in rise so much, many people and companies talk about it like "their AI". Like it's their property and they own the code but it's not..
There are only a few companies on the planet who are "in control" of the code and data, those are the ones who "own AI", not the consumer
There is no "your AI", there is only "their AI" that you work with, don't forget that!
To those concerned about #slack now using your chats, including trade secrets, NDA stuff, etc., to train their #llm: #WTF did you expect using a third party with full content access to discuss those things? That they'd be gentlemen and not read your mail? That they somehow wouldn't try to find a way to monetize that juicy data? I am flabbergasted that people working for corporations just as immoral could have been that naive...