When Karl was preparing to cross the ice from Alaska to Russia, I worked with him a bit on a kite-flown camera system to help him get a Birds Eye view of the flows to chart his course. I engineered a ruggedized wireless camera in an aluminum housing, I don’t remember much about it other than I was doubtful that the resolution would be able to give him the data he needed on on small low resolution screen. (This was before consumer drones were common or affordable). We built some devices, not sure if he ever used them or if they helped. I urged him to do a lot of testing to make sure they would be worth the weight.
We spent a lot of time at college coffee house in Fairbanks Alaska working over the ideas and overall design.
Nice fellow, strange aspirations, indomitable spirit. I’m glad to see his trek is nearing completion, and I wish him well on his further adventures. Good luck and Godspeed, Karl.
The N900 was my peak “mobile computing is awesome” device.
I went to see District 9 in the cinema in Helsinki. Uh oh, the alien parts are only subtitled in Finnish and Swedish and my Finnish is not up to that.
I installed a BitTorrent client, found the release on Pirate Bay, successfully torrented just the subtitle file, and used an editor to read the subtitles for scenes with a lot of alien.
The N9 had much better UI, but there was something of the cyberpunk “deck” idea in that thing, it was great.
If enough of these horror stories are publicized, people will learn to never buy/redeem Apple gift cards because of the real possibility of account bans.
- Don't give Apple gift cards to family and friends: You're potentially ruining the recipient's digital life if they redeem it.
- Don't buy Apple gift cards: You risk ruining your own digital life.
If you've been given an Apple gc for Christmas -- and you have paranoia of the risks -- don't buy anything online that's tied to your Apple ID. Instead, go to the physical Apple store to redeem it. And don't buy an iPhone with it because that will eventually get assigned to an Apple ID. Instead, get a non-AppleID item such as the $249 ISSEY MIYAKE knit sock.
I have thousands of credit-card reward points that could be traded in for Apple gift cards but I don't do it because Apple's over-aggressive fraud tracking means Apple's store currency is too dangerous to use.
I back up regularly using Google Takeout and similar tools, but I don’t think it’s fair to shame this author . Even if you have backups , your recent and essential content and credentials will be locked out . 1% of your content is the most important
We all depend heavily on cloud storage and sso . Everything works fine until you are locked out .
And using them isn’t fully voluntary. They are necessary for collaboration . You end up using what your team uses .
You can try to be that “own cloud” snob but it only works if you live in a basement
Every normal person has content in Google , iCloud , OneDrive , Dropbox and maybe more. That’s 4+ single points of failure
You’re just not imaginative enough if you think you’re safe .
Autonomy subscriptions are how things are going to go, I called this a long time ago. It makes too much sense in terms of continuous development and operations/support to not have a subscription -- and subscriptions will likely double as insurance at some point in the future (once the car is driving itself 100% of the time, and liability is always with the self driving stack anyway).
Of course, people won't like this, I'm not exactly enthused either, but the alternative would be a corporation constantly providing -- for free -- updates and even support if your car gets into an accident or stuck. That doesn't really make sense from a business perspective.
To paraphrase an old saying: Live by Big Tech, die by Big Tech.
After nearly 30 years as a loyal customer
I've heard others say this (and was a "loyal advocate" of Windows for around 2 decades myself), but the reality is they simply do not care. You are merely a single user out of several billion.
Many of the reps I’ve spoken to have suggested strange things
That almost sounds like some sort of AI, not a human. But if I were in your situation I'd be inclined to print out that response as evidence, and then actually go there physically to see what happens.
It would be impossible to do without taking breaks, as explained in the article:
> Due to visa limits, Bushby has had to break up his walk. In Europe, he can stay for only 90 days before leaving for 90, so he flies to Mexico to rest and then returns to resume the route.
Given that he literally swam across the Caspian Sea in order to avoid Russia and Iran because of legal issues, nevermind bring imprisoned in Russia due to what sounded like bureaucratic BS, it's more impressive than I first thought.
> I couldn't for the life of me tell you what dd stands for.
Data(set) Definition. But that name does not make any sense whatsoever by itself in this context, neither for the tool (it hardly "defines" anything), nor for UNIX in general (there are no "datasets" in UNIX).
Instead, it's specifically a reference to the DD statement in the JCL, the job control language, of many of IBM's mainframe operating systems of yore (let's not get into the specifics of which ones, because that's a whole other can of complexity).
And even then the relation between the DD statement and the dd command in UNIX is rather tenuous. To simplify a lot, DD in JCL does something akin to "opening a file", or rather "describing to the system a file that will later be opened". The UNIX tool dd, on the other hand, was designed to be useful for exchanging files/datasets with mainframes. Of course, that's not at all what it is used for today, and possibly that was true even back then.
This also explains dd's weird syntax, which consists of specifying "key=value" or "key=flag1,flag2,..." parameters. That is entirely alien to UNIX, but is how the DD and other JCL (again, of the right kind) statements work.
It's also worth stating that the worst part of that proposed amendment [1] isn't even necessarily the VPN ban, it's the next clause, on page 20:
"The “CSAM requirement” is that any relevant device supplied for use in the UK
must have installed tamper-proof system software which is highly effective at
preventing the recording, transmitting (by any means, including livestreaming)
and viewing of CSAM using that device."
"Regulations under subsection (1) must enable the Secretary of State, by further
regulations, to expand the definition of ‘relevant devices’ to include other
categories of device which may be used to record, transmit or view CSAM"
Good for them. During economic downturns, when fewer resources are available for redistribution, collective action across population groups can help address worsening power imbalances.
You shouldn't have to hack it, you should have the right to repair the software on your device. Hopefully the Vizio lawsuit will help with that for Linux based devices, signs are looking good though.
Agreed, it seems inevitable that autonomy and insurance are going to be bundled.
1. Courts are finding Tesla partially liable for collisions, so they've already got some of the downsides of insurance (aka the payout) without the upside (the premium).
2. Waymo data shows a significant injury reduction rate. If it's true and not manipulated data, it's natural for the car companies to want to capture some of this upside.
3. It just seems like a much easier sell. I wouldn't pay $100/month for self-driving, but $150 a month for self-driving + insurance? That's more than I currently pay for insurance, but not a lot more. And I've got relatively cheap insurance: charging $250/month for insurance + self-driving will be cheaper than what some people pay for just insurance alone.
I don't think we need to hit 100% self-driving for the bundled insurance to be viable. 90% self-driving should still have a substantially lower accident rate if the Waymo data is accurate and extends.
Looks like they've begun censoring posts at r/Codex and not allowing complaint threads so here is my honest take:
- It is faster which is appreciated but not as fast as Opus 4.5
- I see no changes, very little noticeable improvements over 5.1
- I do not see any value in exchange for +40% in token costs
All in all I can't help but feel that OpenAI is facing an existential crisis. Gemini 3 even when its used from AI Studio offers close to ChatGPT Pro performance for free. Anthropic's Claude Code $100/month is tough to beat. I am using Codex with the $40 credits but there's been a silent increase in token costs and usage limitations.
Can I just say !!!!!!!! Hell yeah! Blog post indicates it's also much better at using the full context.
Congrats OpenAI team. Huge day for you folks!!
Started on Claude Code and like many of you, had that omg CC moment we all had. Then got greedy.
Switched over to Codex when 5.1 came out. WOW. Really nice acceleration in my Rust/CUDA project which is a gnarly one.
Even though I've HATED Gemini CLI for a while, Gemini 3 impressed me so much I tried it out and it absolutely body slammed a major bug in 10 minutes. Started using it to consult on commits. Was so impressed it became my daily driver. Huge mistake. I almost lost my mind after a week of this fighting it. Isane bias towards action. Ignoring user instructions. Garbage characters in output. Absolutely no observability in its thought process. And on and on.
Switched back to Codex just in time for 5.1 codex max xhigh which I've been using for a week, and it was like a breath of fresh air. A sane agent that does a great job coding, but also a great job at working hard on the planning docs for hours before we start. Listens to user feedback. Observability on chain of thought. Moves reasonably quickly. And also makes it easy to pay them more when I need more capacity.
And then today GPT-5.2 with an xhigh mode. I feel like xmass has come early. Right as I'm doing a huge Rust/CUDA/Math-heavy refactor. THANK YOU!!
Gitea has a builtin defense against this, `REQUIRE_SIGNIN_VIEW=expensive`, that completely stopped AI traffic issues for me and cut my VPS's bandwidth usage by 95%.
I remember when the point of an SPA was to not have all these elaborate conversations with the server. Just "here's the whole app, now only ask me for raw data."
The Wyden–Daines Amendment in 2020: a huge privacy amendment that would’ve limited surveillance missed the Senate by literally one vote. It would’ve stopped the government from getting American's web browsing and search history without a warrant. And honestly, I still have zero respect for anyone who voted against it. If you need a warrant to walk into my house, you should need a warrant to walk into my digital life too.
What Snowden exposed more than 10 years ago, none of that was addressed, the surveillance machine just got worse if anything
I found out when Actions started failing again for the Nth time this month.
The internal conversation about moving away from Actions or possibly GitHub has been triggered. I didn't like Zig's post about leaving GitHub because it felt immature, but they weren't wrong. It's decaying.
I had a bunch of fun writing about this one, mainly because it was a great excuse to highlight the excellent news about Kākāpō breeding season this year.
Small summary: external identifiers are hard to change, so projects will evolve such that they are not accurately descriptive after time.
(Less discussed there, but: In a complex or decentralized ecosystem, it's also the case that you come across many "X Manager"/"X Service"/"X State Manager"/"X Workflow Service" simultaneously, and then have to rely on a lot of thick context to know what the distinctions are)
There are two very simple causes to point to why touch keyboards turned to shit:
1. Crowdsourced word weighting: your keyboard's stochastic predictions are no longer mostly based on your typing, but rather on what 'everyone' is typing as their next word. This makes the word replacements it does often suboptimal to downright nonsensical.
2. Aggressive lookbehind correction: these days you have to be seriously on your guard for your keyboard to not sneak-edit something you typed 5 words back, because autocorrect suddenly decided that the probability is high you meant to say something else there (which it clearly isn't, as your eyes and brain exist)
The problem your encountering is downstream from point 1. Basically your keyboard thinks due to the way most people construct a particular sentence, you're gonna want to type "bold" next, despite "hold" clearly clearly making more sense. So it'll force "b" on you 4 times in a row until it realizes you really want to type "h".
Going back to the old style of doing keyboards (mostly user-learned dictionaries and probability weighting, and little lookbehind autocorrrect) could be done, but within Google and Apple there are probably people who got promoted by switching to the current shitty system. They'll block off any attempt at someone messing with their pride.
(There is a third 'problem' where your visual keys do not correspond to the touchmap at all. Swiftkey has a feature where it can show you what your touchmap and heatmap look like versus the actual layout and it its often staggeringly different, with many keys vastly tilted. When you try to desperately type "h" after 4 misses, you're doing that with your index finger in "hunt and peck" mode, which does correspond to the visual layout but not with your usual typing on the touchmap layout. There is no way for your keyboard to know you're in "hunt and peck" accuracy mode.)
Call me naive, but my read is the opposite. It's impressive to me that we have systems which can interpret plain english instructions with a progressively higher degree of reliability. Also, that such a simple mechanism for extending memory (if you believe it's an apt analogy) is possible. That seems closer to AGI to me, though maybe it is a stopgap to better generality/"intelligence" in the model.
I'm not sure English is a bad way to outline what the system should do. It has tradeoffs. I'm not sure library functions are a 1:1 analogy either. Or if they are, you might grant me that it's possible to write a few english sentences that would expand into a massive amount of code.
It's very difficult to measure progress on these models in a way that anyone can trust, moreso when you involve "agent" code around the model.
I love the idea of educating students on the math behind AI to demystify them. But I think it's a little weird to assert "AI is not magic and AI systems do not think. It’s just maths." Equivalent statements could be made about how human brains are not magic, just biology - yet I think we still think.
We spent a lot of time at college coffee house in Fairbanks Alaska working over the ideas and overall design.
Nice fellow, strange aspirations, indomitable spirit. I’m glad to see his trek is nearing completion, and I wish him well on his further adventures. Good luck and Godspeed, Karl.