Sabitlenmiş Tweet
pete
277 posts
pete
@1feck
building https://t.co/KqAbDPqoLI
San Francisco, CA Katılım Nisan 2013
159 Takip Edilen823 Takipçiler
pete retweetledi
Vmax is building an open-ended learning system that generates and optimizes itself on tasks that it creates, avoiding human bias that may corrupt optimal learning curricula.
In PopuLoRA, we instantiate this as co-evolving populations of LLMs performing asymmetric self-play.
GIF
English
@LinusEkenstam Here’s the list:
linus-sellout-tweets.com
English
This is how the algorithm can completely destroy your reach over night.
This is the last:
Left: 3 months
Right: 2 weeks
Super consistent 85-95% drop on all metrics.
everything after a viral post going ballistic, I tried everything, cool down, delete low quality posts, block bot accounts.
Kept posting after cool down, nothing really breaks through.
Short hot takes 🛑
Long form with good signal 🛑
Viral potential post 🛑
Core audience value post 🛑
What bothers me here is that 48h after posting a mega viral post I get suppressed back to the Stone Age.
This follow previous situations I’ve had with the grok powered algorithm. Where it feels like tweepCred falls far below a certain level, and you’re locked into a low reach prison with every effort to break out is making it harder and harder to do so.
I’m asking for transparency on what we can do as content creators when this happens. I don’t want to spam my way out of this. I’d like to know, if I did something wrong, how I can address it, take the responsibility of algorithmic suppression for what ever the length is.
But this limbo is most likely going to make me leave the platform.
Linus ✦ Ekenstam@LinusEkenstam
I’ve been here since 2007, 19 years. I’m about to give up on X. For the third time in <12 months my account is under immense algorithmic suppression. No reach. no nothing. I get punished for being a good person on the platform. In the past my account has been “miss labeled by grok” or “i did not do anything wrong, they did”. Stuff that’s been completely out of my control. This time feels just the same. Nothing breaks past the great algorithmus. I’m a premium+ user. I provide value and have posted tens of thousands of useful posts on here. Yet my account is pushed into “limbo” where posts get throttled down. Super low view count, and no clear pathway to get out of it. For the last 2 weeks, nothing gets close to reaching you, my followers. I’ve seen this before and I know the pattern far too well. It’s a place where many people basically throws in the towel. There is something seriously wrong with how the reach suppression works on here. I post daily, 3-6 times, it’s part of my routine, have been doing so for years. You build momentum, you provide value, and the cycle repeats, until, something breaks out of your network (OON reach) then the algorithm slams you with the biggest breaks ever, throwing your account into reverse. If @xai and @nikitabier is listening they should really think hard about why stuff like this happens to users that really want the best for this platform. At the very least, surface insights inside of creator tools area that shows if and when something has gone wrong or happened to your account that can inform us about wrong doings or simply surfaces issues. That way people like me that spends an unhealthy amount of time on here can better understand why I’m getting punished. I’m extra under the weather this time. It just zucks to be fair.
English
pete retweetledi
What is HQ 👇
Ecomm Cowboy@ecommcowboy
“Team AI is the next challenge.” @jacob_posel on HQ’s opportunity: “The biggest problem with AI right now is everyone is just doing their own things on their own computers. It’s siloed. It’s fragmented.” One person on your team creates a great skill. It lives on their laptop. No team-wide adoption. HQ is the shared context layer that fixes it.
English
pete retweetledi
Introducing HQ: the AI operating system for your company.
HQ lets your team share knowledge, skills, workflows and API access across the organization, so everyone works from the same foundation.
Team AI is still messy, and hard.
Individuals work in silos. There is no consistent knowledge base. Teams end up with 10 versions of the same skill, all performing at different levels. One person becomes 10x more effective, while everyone else is left trying to catch up.
HQ makes this simple.
Built on top of Codex and Claude Code, HQ sits directly inside your existing workflow. It helps manage your company's context layer, share skills, standardize workflows and control access, so people only see what they need to see.
We built HQ internally to solve a real problem. We use it every day. It has been incredible for enabling our power users, but just as importantly, it has helped the least technical members of our team become incredibly effective AI users.
HQ turns one person's breakthrough into everyone's baseline.
It is a powerful, elegant tool, and we are incredibly excited to share it with the public.
Book a demo below.
English
pete retweetledi
Imagine you're building a legal-tech agent that drafts LOIs, redlines contracts, and coordinates signatures.
You grab a harness, spin up a sandbox, and within a day you hit a wall:
– How do documents persist when the sandbox dies?
– How do you control which files an agent can read vs. edit?
– How do humans review and roll back changes?
Swap real-estate docs for case files, claims, audit reports, or pull requests — same problem.
A new agent stack is forming.
> Models handle intelligence.
> Harnesses handle orchestration.
> Sandboxes handle isolation.
The missing layer is storage — and existing solutions weren't designed for agent workloads.
So we built Mesa: a durable, POSIX-compatible filesystem with built-in version control, designed from the ground up for agents.
It supports isolated branches so agents can work in parallel without locks.
Sparse materialization of files means massive document sets load instantly.
Fine-grained history so every change is reviewable and auditable.
Design partners are already running it in production across legal, healthcare, GTM, business ops, and coding agents.
Private beta is open. If you're building enterprise agents that touch long-lived documents, join us 👇
English
pete retweetledi
pete retweetledi
I'm so excited to officially share what we've been cooking up at Mesa: the most powerful filesystem ever built for AI agents.
The dirty secret of every "production" AI agent today: the filesystem is held together with duct tape.
Teams are stitching together S3, GitHub, sandbox-local disks, and homegrown diff logic to give their agents something resembling persistent, versioned storage. None of it works.
S3 isn't designed for parallel agents - concurrent agent writes silently overwrite each other.
GitHub has the semantics but rate-limits you into the ground at agent scale and doesn't give you filesystem ergonomics.
Sandbox disks vanish the moment the container dies.
And your agents don't want to git clone and git push anyway. 𝗧𝗵𝗲𝘆 𝘄𝗮𝗻𝘁 𝘁𝗼 𝗿𝗲𝗮𝗱 𝗮𝗻𝗱 𝘄𝗿𝗶𝘁𝗲 𝗳𝗶𝗹𝗲𝘀. 𝗟𝗶𝗸𝗲 𝗲𝘃𝗲𝗿𝘆 𝗽𝗿𝗼𝗴𝗿𝗮𝗺 𝗲𝘃𝗲𝗿 𝘄𝗿𝗶𝘁𝘁𝗲𝗻.
So we built the missing layer.
Mesa is a durable, POSIX-compatible filesystem with version control built in. Branches, diffs, history, rollback, access control — every primitive a codebase has, for any file type, at agent scale. You mount it. Your agent uses it like a normal filesystem. We handle the rest.
Private beta is live. Link in comments.
English
pete retweetledi
Introducing Mesa: the most powerful filesystem ever built, designed specifically for enterprise AI agents.
Every team building agents eventually hits the same wall: where do the files live?
Not the chat history, the actual artifacts the agent works on.
> The contracts your agent redlined
> The claim files it updated
> The 200-page audit report it edited overnight while you were asleep
Today those documents live in a sandbox that dies in 30 minutes, an S3 bucket where concurrent writes clobber each other, or a GitHub repo that was never built to absorb agent-scale traffic.
So we built Mesa.
The world's first POSIX-compatible filesystem with built-in version control, designed from the ground up for agents. You mount it into your sandbox like any other filesystem. Your agent reads and writes files normally. Behind the scenes every change is versioned, branchable, reviewable, and rollback-able — like a codebase, for any file type.
Mesa provides
– Branches so agents work in parallel without locking
– Durable storage that survives sandbox death
– Sparse materialization so massive document sets load instantly
– Fine-grained access control per agent
– Full history for human review and audit
Design partners are running Mesa in production across legal, healthcare, GTM, business ops, and coding agents.
Private beta is open: link in the comments
English
@maddiedreese wow this reminded me I have a palm pre 2 that I never figured out how to boot up
English
pete retweetledi
Introducing create-xcode
create new Xcode (SwiftUI, UIKit, etc) apps from the command line.
zero-dependencies and runs on any computer, vm, or sandbox.
✋ Before: Open Xcode → ⇧⌘N → multi-step GUI
👉 After: npx create-xcode -y
English
