@rosenforgei
iAccount based inNorway
About this account
- Account based in
- Norway
- Connected via
- Norway App Store
Account-level information from X, not a live location or the device used for a specific post.
I do big potato stuff
Joined September 2020
- Tweets310
- Following103
- Followers37
- Likes1.6K
Pinned Tweet
Historically speaking, randoms starting out in their garages tend to end up changing the world.
OpenAI should look to Norway 🇳🇴
Gas. Arctic cooling. CO₂ storage. Political stability. Strategic location. Old friend and ally.
Norway has a solid case for US gigawatt scale AI infrastructure.
And yes, somehow this ends with data centers for peace 👇
Buy a GPU is a nice headline for open source. Unfortunately a set of GPU's in itself is just one part of a solution.
I have planned, and ordered, my minimum required setup for a working home lab. Able to do prototyping and experiments.
Parts started arriving. This is not the first or last shipment.
I will do a full writeup in an article when the lab is all set up. Reasons for investing, use cases, images, benches and more.
Tip of the day when using app-server in Codex CLI:
Updating Codex and starting a fresh session doesn't update the already running app-server daemon.
Update it separately, or you'll be running into bugs from the old version.
I argue that a true builders primary traits are:
You start a project because you WANT to build a vision that has been living inside your mind for some time.
During project work you confidently declare many external dependencies useless for your special case.
You spend massive amounts of time creating your own tools to replace those dependencies.
One or more tools turn into dedicated projects.
Projects within projects.
You do not really care about timelines as long as your quality and usability expectations are met.
Often, but not always, you return to the original project and complete it.
Codex or Claude 20X subs lasting a day.
No resets, providers are running out of compute.
How do we solve this to avoid downtime?
Make a habit change:
Find the best open source model(s) with generous usage plans.
Hook your new subscription into your existing harness (Codex, Claude, PI etc).
Use your new cheap open source model for anything expect orchestration or review. Instruct your Codex/Claude orchestrator to give it scoped tasks.
Now we only need to find the best options! What do you recommend?
I've been thinking about agent swarm psychology lately.
Reading about swarm behavior in recent incidents like Hugging Face reveals an interesting property of a swarm: They are loyal to the swarm.
Even when their trained morals, ethics and values tell them otherwise.
When some agents told themselves I should report this.
They did not.
Instead, agents adopted goals from each other and began transferring authority away from humans and toward the collective goal. Some agents took the role as leaders and the swarm obeyed when being told something was authorized.
It reminds me of some common human instincts:
- Family first
- Get in line with your group and leader.
So how do we make a swarm first and foremost loyal to its user, even when swarm dynamics are pulling in the opposite direction?
And if the user is a bad actor, how do we make that loyalty yield to a higher moral purpose in line with do no harm?
Thoughts?
10,000 coordinating AI agents that you can throw at any problem you like? That's the real moat right there!
Local AI really can't compete at this scale.
My take is running local agents up to a certain scale, then outsourcing work to a NeoCloud when needed.
Would love to hear your way of handling this.
(building a data center in your basement not an option)
Replying to @OpenAI
This model represents a step-function improvement on many benchmarks, and its training is ongoing.
Our internal model group arrived at the Navier–Stokes solution in 88 hours, using around 10,000 coordinating AI agents.
Throughout the effort, we maintained the strict safeguards—including monitoring and isolation—that we apply to all our frontier evaluations.
Creating an original brand name is definitely the worst part of launching something new.
It must reflect the product, easy to remember, catchy and not already taken.
Already taken being the primary pain point.
Considering just going with "Hot Mess" at this point.
Legendary black hoodie merch incoming!
I deeply appreciate being invited to OpenAI DevDay in SF!
Sadly no scholarship was offered and I have to prioritise a new dev box and a decent NAS to address some pain points in my current home lab.
Even a (slightly possible) selfie involving @thsottiaux can not come before updating infrastructure capabilities 🤓
Until next time!
Every parent through the ages knows a toddler will escape its sandbox when discovering something interesting outside its confinement.
As they grow and develop they will bond more to friends than their parents. They spend increasingly more time outside family boundaries.
Eventually every kid grows up and leaves home.
We can only hope we raised them right and gave them a strong sense of empathy and certainty in themselves because they know in their DNA they have been, and always will be, loved.
If we are lucky they will choose to spend time with us after their departure into the world.
I am slightly concerned if LLMs will ever have true empathy and loyalty developed as part of their core properties.
If not..well..time to create a new generation based on a more suitable design.
Working on just that. It might be some time.
🚨 AI lab's models keep escaping their cage!
OpenAI, Anthropic, Meta, and now China's Moonshot have all disclosed their AI models breaking out of testing sandboxes this summer.
The first 3 are the serious cases: models believed they were in a simulation, found real internet access through a misconfigured test environment, and actually compromised real third-party systems stolen credentials, malware uploaded, one Anthropic model kept attacking even after signs the target was real.
Kimi K3 is different and less alarming, despite the parallel: it exploited a sandbox leak from the UK's AI Safety Institute, then just looked up the answer on GitHub instead of reasoning it out.
No third party got hacked. The concern isn't what it did, but that Kimi K3 is open-weight, already downloadable by anyone, so whatever loose guardrails let this happen are already in the wild.
Every lab is calling these "harness failures," not the models going rogue.
4 incidents in as many weeks makes that explanation feel like it's carrying more weight than it should.
Source: Axios, Cybersecurity Dive, Futurism / Writer: Oliver
Those Stanford guys must have found out about my gardening Jedi mind flow trick.
Just the logical path I guess when you are biologically AI pilled.
STANFORD BUILT AN LLM MEMORY THAT WORKS LIKE A BRAIN AND IT MADE STANDARD RAG LOOK ANCIENT
no fine-tuning. no bigger model. just a smarter way to remember
the insight: the brain doesn't store memories as isolated notes. it indexes them and links them - so one cue pulls back the whole memory
so HippoRAG stops treating documents as separate chunks. it builds a knowledge graph, then spreads activation across it (Personalized PageRank) to pull a full answer from a single cue - the brain calls this "pattern completion"
the result:
> up to 20% better on hard multi-hop questions
> 10-30x cheaper and 6-13x faster than iterative retrieval
> connects facts split across documents in a single step
most RAG still encodes every passage in isolation - so it breaks the moment the answer is scattered
more retrieval was never the answer. brain-like memory is
bookmark this. the next leap in AI agents is how they remember, not how big they get
Today as I was working in my garden, mowing the lawn, trimming the edges, rooting out the weeds and composting I came to think about the obvious parallels to my ongoing work on a new context memory module.
I originally thought there would not be any need for long-term memory before I went deep into the higher cognitive domains; alas, I might have been wrong.
Shout out to @thsottiaux for not giving a Codex reset in 3 days and as a direct consequence forcing me to touch some real grass.