Jeff mentioned in his video that just loading the front page of CNN would take something like an hour and a half (20+ MB).
33.6Kbps is not practical for much on the modern Internet in 2026. As mentioned in a sibling comment, Starlink (even in standby mode) would be much better. lite.cnn.com would load in about 10 seconds which is pretty good, but there's not much else like it left anymore.
What's amazing is how great the Internet in the 1990s managed to be despite these limitations. Just like with RAM and disk space, developers back then had to be very mindful of bandwidth - today's devs (and agents) have the luxury of paying much less attention to that.
20+ mb is also the weight of rendering the HTML inside each client, instead of at the server. It is the weight of continuous disdain for users, and of 30 years of not giving a fuck about adding yet another abstraction layer and making it someone else's problem.
You can somewhat "fix" this by using your slow link to connect to a VPS somewhere that then connects to the Internet, either via links or a similar text-mode browser, or other bandwidth-saving gateway.
In the article and my pi-isp project, I use MacProxy Classic to strip heavy stuff from web pages through a local proxy service running on the Pi. This helps a lot, but if a page has 20 MB of resources, it can only do so much (without completely disabling JS and images).
There were proxies in the old day that would recompress images and do other things, but if the 20 MB is compressed javascript, there's not much you can do but hope it caches well.
That's a lot of stuff that I don't want to deal with or maintain. It's simply beyond the tolerance of my gumption, so it's not going to happen. :)
What can happen, instead: I can dream.
In this dream, the process of loading a web page identifies the viewing platform well-enough and the server delivers content that is shaped for it, so it can be downloaded quickly and displayed simply by the end-user device. It's not one-size-fits-all at all, or even one-size-fits-most: It's a pile of of simplistic HTML and maybe some minimal javascript and CSS that is meant for whatever the user is using right now.
In this way, the same layout jiggering, varnicating, and transfabulation is done as it is done today, but the work of doing so principally happens on the server instead of the client.
Also in this dream, I can hear people saying "But that's a can of worms!", and they're right. It's a damned mess -- but it's a mess either way. This just moves the mess from the client to the server.
I can also hear shouts of "But there will be hundreds or even thousands of layout paths!" And all I can think is: If there's a thousand unique device types hitting a given dynamic page, and that scales poorly with the server side doing the work, then that's a problem for the systems guys to direct instead of the web guys.
Which is fine: The web guys hacking away however they want is how we got into this mess of 20 megabyte Javascript downloads just-to-view-a-web-page to begin with. They've quite broadly proven that they're shit at this kind of work, and in my ideal world they'd be relieved of that duty.
(And yeah, to be sure: After I wake from this dream I'm still going to go outside and yell at the clouds, just as I do every day.)
This dream actually existing for a hot minute back in the day! There were a number of sites that would give you much different experiences based on your capabilities - and this continued into the mobile era - until Jobs screwed it up by shipping a desktop-capable web browser on a phone.
Fundamentally very similar to Tailscale. I've been using it for years and it has been flawless. It doesn't have as many bells and whistles as Tailscale but it does what it does very well.
If opinion polling were to be done on this issue, I bet we'd find that the general public would be almost unanimously united in agreement that elected officials should not get special treatment in the airport or when flying. Instead, they should be subjected to the same awful experience (that they all created) as the rest of us. If it were up to me, I'd even ban them from being eligible for TSA Precheck. Stand in the normal TSA line like everyone else.
After college I moved from the far western edge of one timezone to the far eastern edge of another zone. I grew up with 5-5:30pm sunsets in winter, and now I live with 4-4:30pm sunsets. I moved here 25 years ago, and every single year when November/December come around and I get those early sunsets I hate it. It's one of the reasons I'd like to move away from here.
I know it's just one person's opinion, but to me those extremely early sunsets in the middle of winter are a huge quality of life reduction.
I believe part of the problem is that if you're in the middle or western edge of your zone, the winter sunsets aren't so bad. I suspect a lot of people who would prefer DST year round live on the eastern edge.
I live in Atlanta (western edge of US Eastern time) and permanent DST sounds horrible - the sun would rise at 8:45 in early January. Honestly I'd prefer we be on permanent standard time. Call it permanent Central Daylight Time if you must.
On the other hand, I used to live in Boston (eastern edge of US Eastern time) and those 4:15 sunsets were pretty depressing. Permanent DST sounds reasonable there.
Nebula just had a major release that added IPv6 support for overlay networks. Hardly maintenance mode.
The main company working on it now seems to be adding all the fancy easy-to-use features as a layer on top of Nebula that they are selling. I personally appreciate getting to use the simple core of Nebula as open source. It seems very Unix-y to me: a simple tool that does one thing and does it well.
I've had gemini tell me "We are debugging this problem here in İstanbul" and talking about an istanbul evening, trying to give uplifting or familiar vibes while being creepy.
I think there was a setting about time and location which finally got rid of that behavior.
I got much better at this when my kids were born, because it was the only way I could get work done on some of my (computing) side projects. I went from having hours of uninterrupted "in the zone" time during evenings and weekends to having much less time overall, and what time I did have was broken into smaller chunks.
I got much more thoughtful about how I used my time and also got better at pre-planning what I had to do so as to make the best use of it. Mostly the key was to just try to tackle smaller tasks and accept that progress would be slow.
That's been exactly my experience as well. Sometimes doing a little research on a lunch break gives enough direction on how to spend available time later on my project.
Accepting that progress will be slow has been the most difficult adjustment, and applies to more than just side-projects. Choosing books or games also becomes a more strategic decision when what used to be a weekend sprint, turns into a several week marathon.
Pretty much all of these reliability reducers are manufacturers trying to eek a little more MPGs by throwing lots of complicated technology at the problem, which introduces a lot more failure points.
Headlights and taillights on my current vehicle are supposedly around $1500 each, mostly due to a bunch of sophisticated sensors being built in.
Back in the 80s headlights were standardized (in the US at least) - you either had rectangular or circular. They were available at every auto parts store. Now they're a special order item from the dealer.
New synthetic oils are very durable. They actually do last a long time.
There are oil tests that confirm this. Also, 10,000+ mile oil changes are not new, and there are tons of used vehicles on the market, running around with long oil change intervals, and high mileage.
> But the market has spoken! Users prefer Litestream. And honestly, we get it: Litestream is easier to run and to reason about. So we’ve shifted our focus back to it.
That makes sense to me. LiteFS used FUSE, which meant figuring out how to run and mount a custom filesystem. Litestream is a single compiled Go binary that you point at the SQLite database file (and accompanying WAL file).
Doesn't matter. Republican politicans and influencers (if separating the two still makes any sense) framed it as an attack by the "woke" and "radical left" on these fabled american values.
Not maybe so, it is what’s happening. Whether their stance reflects reality or not is not (is it ever with these people?) the point - they’re using it to stir the pot as usual.
Republican politicians and influencers frame everything as an "attack" by the "woke" and "radical left". It makes for a great preemptive distraction when they're actually responsible for most of those things. Bland gray/beige color schemes get decided in board rooms full of uninspiring executive-class types who can't think of anything but trying to cargo cult their way into making the Line go up.
33.6Kbps is not practical for much on the modern Internet in 2026. As mentioned in a sibling comment, Starlink (even in standby mode) would be much better. lite.cnn.com would load in about 10 seconds which is pretty good, but there's not much else like it left anymore.
What's amazing is how great the Internet in the 1990s managed to be despite these limitations. Just like with RAM and disk space, developers back then had to be very mindful of bandwidth - today's devs (and agents) have the luxury of paying much less attention to that.
reply