Theres transport and context management. A cross agent status cache with semaphore over a testing harness driving a browser that can rewind and retry is much easier for agents to drive from mcp than selenium or whatever is fashionable these days. Didn't replace unit testing per se but to rca and fix it's a much better tool.
Exactly! Swagger descriptions+GUI[1], HATEOAS[2], and JSONAPI[3] all coming together in jubilous harmony if MCP pulled its head out of the sand, but instead we get the XKCD#927[4] situation.
I also have two X220 machines, and I use them more than the X200 now. They still work perfectly, while my X200 is getting flakey. (Although with its SSD and 8GB of RAM, it runs Alpine very well indeed and could be a daily driver.)
The X220 has a slightly shallowed screen; that's a weakness. But mine are 100% usable: between them, I run Haiku, FreeBSD, OpenBSD, Ubuntu, and Pop OS, and all of them go like stink and are daily-drivable on this 2011 hardware.
I have an X230 which was upgraded with a quad-core CPU (i7-3612qe), 16gb RAM, SSD, and 1080p screen, and it makes a pretty decent around-the-house laptop. I'd rate it pretty highly; it's not quite as fast as my 6th gen X1 Carbon but the X1 is starting to get quite flaky.
If that is good enough, I will put up with a bad screen.
Good speakers is very nice to have, I admit, but I do not do podcasts or videos. I do listen to the radio a lot, however.
I do not own a single laptop with 32GB RAM. That I don't care about. My desktop does, but the biggest laptops are 24GB, which was massively cheaper. Most are 16GB which I find enough for even quite intensive use.
"Best build quality" is the most important part. If you never got to handle one you are missing out. Glass and Solid milled aluminum. Silicone wrist pads and grip. 4:3 screen ratio. high quality keyboard. Rock solid 360 screen hinge.
Hardware is essentially a high end cellphone from 2016, which isn't a powerhouse but still does everything I would ask of a chromebook in 2026. Batteries are all generally going well.
Repair-ability is a challenge, but I want to work on that. You can mod it to run windows or linux. Stock it runs chromeos, linux subsystem, and android apps. It has a "feature" where if you keep in developer mode it auto-wipes itself if anybody else tries to boot it (hitting anything but the un-indicated ctrl-d at the boot screen initiates powerwash). Great for international travel.
It isn't a good choice for "power" but dominates every other aspect of "being a good laptop". It was too expensive for the chromebook market back then, but now you can pick them up for $200 and hand them to your parents and stop getting asked to fix their computer.
Ownership of namespaces is such a hard problem, our society has had to form global organizations and some of our most secure distributed systems to make it happen.
Working in the p2p space, scalable namespace ownership that doesn't get instantly ruined by perverse incentives is the holy grail. I don't think it is actually tractable in any "central authority free" system. Don't get me started on blockchains that tether names to the most perverse systems available and call it victory.
Given that this system already uses DNS for namespacing of user identifiers (via instances), it seems like it could use DNS for namespacing of channels too
My personal p2p pet project (not ready yet) just accepts namespace chaos bc it doesn't consider any existing infrastructure reliable or safe. https://github.com/BrendanBenshoof/sneakernet
The real problem is that DNS essentially "outs you" as interacting with a particular user. Literally advertises it to your DNS server. It's a very unsafe name management solution in a privacy centric system.
The problem would be cross-platform support. In the end the capsule file is the standalone binary similar to a PDF or a Word document, you only need the viewer app to open any capsule file.
you can trivially bake X binaries if you have the viewer app for each platform. This is the normal way to distribute software for cross-platform support.
I might just be hyper-defensive to any sort of vendor lock-in like a "viewer app".
Strangely, I think it does "care" or at least would perform caring.
Capitalism doesn't care what you feel. LLMs are just a distillation of the entire human written corpus, there is a lot of "caring" in there. Companies are simply spinning out threads of behavior from the corpus that serve them instead of serving all of us.
The most powerful change I have run into is: "Positive phrasing" as a default, prefer to tell the model what they should do, and why. Not a prohibition on a behavior.
When you say "don't do x" you are just pre-seeding the model with "x" and the prohibition mitigates that some, but not as much as never having put "x" in the context in the first place.
"Do Y, for these reasons" can be shaped to achieve what you mean by "Don't do X"
"Don't do X" leads to "Wait, I need to make sure I didn't X" and "Let's look up X to make sure I don't do that." And each time the odds of X happening keeps going up, not down.
I just want it to be more commonly understood that enslavement is perfectly legal and enshrined in the 13th amendment. We have a million, mostly black, perfectly legal slaves in the US right now.
My experience is that the LLM will be less creative than the human in this situation. Necessity is the mother of invention. Prison is a special sort of neolithic age.
Just generate CLI tools, with docs, from MCP servers on demand.
reply