835 lines
54 KiB
HTML
835 lines
54 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="UTF-8">
|
||
<meta
|
||
name="viewport"
|
||
content="width=device-width, initial-scale=1.0, minimum-scale=1.0">
|
||
<meta
|
||
http-equiv="X-UA-Compatible"
|
||
content="ie=edge">
|
||
<meta
|
||
name="theme-color"
|
||
content="#fff"
|
||
id="theme-color">
|
||
<meta
|
||
name="description"
|
||
content="AKLabs">
|
||
<link
|
||
rel="icon"
|
||
href="/">
|
||
<title>News - 2026 - Week 3</title>
|
||
|
||
|
||
<meta
|
||
property="og:title"
|
||
content="News - 2026 - Week 3">
|
||
|
||
|
||
<meta
|
||
property="og:url"
|
||
content="https://aklabs.net/2026/01/23/News-2026-Week-3/index.html">
|
||
|
||
|
||
<meta
|
||
property="og:img"
|
||
content="/images/akesterson.webp">
|
||
|
||
|
||
|
||
<meta
|
||
property="og:type"
|
||
content="article">
|
||
<meta
|
||
property="og:article:published_time"
|
||
content="2026-01-23">
|
||
<meta
|
||
property="og:article:modified_time"
|
||
content="2026-01-23">
|
||
<meta
|
||
property="og:article:author"
|
||
content="Andrew Kesterson">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<link rel="preload" href="//at.alicdn.com/t/font_1946621_i1kgafibvw.css" as="style" >
|
||
<link rel="preload" href="//at.alicdn.com/t/font_1952792_89b4ac4k4up.css" as="style" >
|
||
<link rel="preload" href="/css/main.css" as="style" >
|
||
|
||
<link rel="modulepreload" href="//instant.page/5.1.0">
|
||
|
||
<link rel="stylesheet" href="/css/main.css">
|
||
|
||
<link rel="stylesheet" href="//at.alicdn.com/t/font_1946621_i1kgafibvw.css">
|
||
|
||
<link rel="stylesheet" href="//at.alicdn.com/t/font_1952792_89b4ac4k4up.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="/js/lib/lightbox/baguetteBox.min.css">
|
||
|
||
<script>
|
||
function loadScript(url, cb) {
|
||
var script = document.createElement('script');
|
||
script.src = url;
|
||
if (cb) script.onload = cb;
|
||
script.async = true;
|
||
document.body.appendChild(script);
|
||
}
|
||
function loadCSS(href, data, attr) {
|
||
var sheet = document.createElement('link');
|
||
sheet.ref = 'stylesheet';
|
||
sheet.href = href;
|
||
sheet.dataset[data] = attr;
|
||
document.head.appendChild(sheet);
|
||
}
|
||
function changeCSS(cssFile, data, attr) {
|
||
var oldlink = document.querySelector(data);
|
||
var newlink = document.createElement("link");
|
||
newlink.setAttribute("rel", "stylesheet");
|
||
newlink.setAttribute("href", cssFile);
|
||
newlink.dataset.prism = attr;
|
||
document.head.replaceChild(newlink, oldlink);
|
||
}
|
||
</script>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<script>
|
||
function prismThemeChange() {
|
||
if(document.getElementById('theme-color').dataset.mode === 'dark') {
|
||
if(document.querySelector('[data-prism]')) {
|
||
changeCSS('/js/lib/prism/prism-tomorrow.min.css', '[data-prism]', 'prism-tomorrow');
|
||
} else {
|
||
loadCSS('/js/lib/prism/prism-tomorrow.min.css', 'prism', 'prism-tomorrow');
|
||
}
|
||
} else {
|
||
if(document.querySelector('[data-prism]')) {
|
||
changeCSS('/js/lib/prism/prism-defauult.min.css', '[data-prism]', 'prism-defauult');
|
||
} else {
|
||
loadCSS('/js/lib/prism/prism-defauult.min.css', 'prism', 'prism-defauult');
|
||
}
|
||
}
|
||
}
|
||
prismThemeChange()
|
||
</script>
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="/js/lib/prism/prism-line-numbers.min.css">
|
||
|
||
|
||
|
||
<script>
|
||
// control reverse button
|
||
var reverseDarkList = {
|
||
dark: 'light',
|
||
light: 'dark'
|
||
};
|
||
var themeColor = {
|
||
dark: '#1c1c1e',
|
||
light: '#fff'
|
||
}
|
||
// get the data of css prefers-color-scheme
|
||
var getCssMediaQuery = function() {
|
||
return window.matchMedia('(prefers-color-scheme: dark)').matches ? 'dark' : 'light';
|
||
};
|
||
// reverse current darkmode setting function
|
||
var reverseDarkModeSetting = function() {
|
||
var setting = localStorage.getItem('user-color-scheme');
|
||
if(reverseDarkList[setting]) {
|
||
setting = reverseDarkList[setting];
|
||
} else if(setting === null) {
|
||
setting = reverseDarkList[getCssMediaQuery()];
|
||
} else {
|
||
return;
|
||
}
|
||
localStorage.setItem('user-color-scheme', setting);
|
||
return setting;
|
||
};
|
||
// apply current darkmode setting
|
||
</script>
|
||
|
||
<script>
|
||
var setDarkmode = function(mode) {
|
||
var setting = mode || localStorage.getItem('user-color-scheme');
|
||
if(setting === getCssMediaQuery()) {
|
||
document.documentElement.removeAttribute('data-user-color-scheme');
|
||
localStorage.removeItem('user-color-scheme');
|
||
document.getElementById('theme-color').content = themeColor[setting];
|
||
document.getElementById('theme-color').dataset.mode = setting;
|
||
prismThemeChange();
|
||
} else if(reverseDarkList[setting]) {
|
||
document.documentElement.setAttribute('data-user-color-scheme', setting);
|
||
document.getElementById('theme-color').content = themeColor[setting];
|
||
document.getElementById('theme-color').dataset.mode = setting;
|
||
prismThemeChange();
|
||
} else {
|
||
document.documentElement.removeAttribute('data-user-color-scheme');
|
||
localStorage.removeItem('user-color-scheme');
|
||
document.getElementById('theme-color').content = themeColor[getCssMediaQuery()];
|
||
document.getElementById('theme-color').dataset.mode = getCssMediaQuery();
|
||
prismThemeChange();
|
||
}
|
||
};
|
||
setDarkmode();
|
||
</script>
|
||
|
||
|
||
|
||
<link rel="preload" href="/js/lib/lightbox/baguetteBox.min.js" as="script">
|
||
<link rel="preload" href="/js/lib/lightbox/baguetteBox.min.css" as="style" >
|
||
|
||
|
||
<link rel="preload" href="/js/lib/lozad.min.js" as="script">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<meta name="generator" content="Hexo 6.0.0"><link rel="alternate" href="/atom.xml" title="AKLabs" type="application/atom+xml">
|
||
</head>
|
||
|
||
<body>
|
||
<div class="wrapper">
|
||
|
||
<nav class="navbar">
|
||
<div class="navbar-logo">
|
||
<a class="navbar-logo-main" href="/">
|
||
|
||
<span class="navbar-logo-dsc">AKLabs</span>
|
||
</a>
|
||
</div>
|
||
<div class="navbar-menu">
|
||
|
||
<a
|
||
href="/now"
|
||
class="navbar-menu-item">
|
||
|
||
~/.plan
|
||
|
||
</a>
|
||
|
||
<a
|
||
href="/archives"
|
||
class="navbar-menu-item">
|
||
|
||
Archive
|
||
|
||
</a>
|
||
|
||
<a
|
||
href="/categories"
|
||
class="navbar-menu-item">
|
||
|
||
Categories
|
||
|
||
</a>
|
||
|
||
<a
|
||
href="/about"
|
||
class="navbar-menu-item">
|
||
|
||
About
|
||
|
||
</a>
|
||
|
||
<a
|
||
href="/consulting"
|
||
class="navbar-menu-item">
|
||
|
||
Consulting
|
||
|
||
</a>
|
||
|
||
<a
|
||
href="/contact"
|
||
class="navbar-menu-item">
|
||
|
||
Contact
|
||
|
||
</a>
|
||
|
||
<button
|
||
class="navbar-menu-item darknavbar navbar-menu-btn"
|
||
aria-label="Toggle dark mode"
|
||
id="dark">
|
||
<i class="iconfont icon-weather"></i>
|
||
</button>
|
||
<button
|
||
class="navbar-menu-item searchnavbar navbar-menu-btn"
|
||
aria-label="Toggle search"
|
||
id="search">
|
||
<!-- <i
|
||
class="iconfont icon-search"
|
||
style="font-size: 1.2rem; font-weight: 400;">
|
||
</i> -->
|
||
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" role="img"
|
||
class="iconify iconify--ion" width="28" height="28" preserveAspectRatio="xMidYMid meet" viewBox="0 0 512 512">
|
||
<path fill="none" stroke="currentColor" stroke-miterlimit="10" stroke-width="28"
|
||
d="M256 80a176 176 0 1 0 176 176A176 176 0 0 0 256 80Z"></path>
|
||
<path fill="none" stroke="currentColor" stroke-miterlimit="10" stroke-width="28"
|
||
d="M232 160a72 72 0 1 0 72 72a72 72 0 0 0-72-72Z"></path>
|
||
<path fill="none" stroke="currentColor" stroke-linecap="round" stroke-miterlimit="10" stroke-width="28"
|
||
d="M283.64 283.64L336 336"></path>
|
||
</svg>
|
||
</button>
|
||
</div>
|
||
</nav>
|
||
|
||
<div
|
||
id="local-search"
|
||
style="display: none">
|
||
<input
|
||
class="navbar-menu-item"
|
||
id="search-input"
|
||
placeholder="请输入搜索内容..." />
|
||
<div id="search-content"></div>
|
||
</div>
|
||
|
||
<div class="section-wrap">
|
||
<div class="container">
|
||
<div class="columns">
|
||
<aside class="left-column">
|
||
|
||
<div class="card card-author">
|
||
|
||
<img
|
||
src="/images/akesterson.webp"
|
||
class="author-img"
|
||
width="88"
|
||
height="88"
|
||
alt="author avatar">
|
||
|
||
<p class="author-name">Andrew Kesterson</p>
|
||
<p class="author-description"><center><i>"Love God. Live Righteously. Die Well."</i> <br/> <br/> <a target="_blank" rel="noopener" href="https://github.com/akesterson">GitHub</a> || <a target="_blank" rel="noopener" href="https://www.linkedin.com/in/andrewkesterson/">LinkedIn</a> <br/> </center></p>
|
||
<div class="author-message">
|
||
<a
|
||
class="author-posts-count"
|
||
href="/archives">
|
||
<span>24</span>
|
||
<span>Posts</span>
|
||
</a>
|
||
<a
|
||
class="author-categories-count"
|
||
href="/categories">
|
||
<span>11</span>
|
||
<span>Categories</span>
|
||
</a>
|
||
<a
|
||
class="author-tags-count"
|
||
href="/tags">
|
||
<span>0</span>
|
||
<span>Tags</span>
|
||
</a>
|
||
</div>
|
||
|
||
</div>
|
||
<div class="sticky-tablet">
|
||
|
||
|
||
<article class="display-when-two-columns spacer">
|
||
<div class="card card-content toc-card">
|
||
<div class="toc-header">
|
||
<i
|
||
class="iconfont icon-menu"
|
||
style="padding-right: 2px;">
|
||
</i>TOC
|
||
</div>
|
||
<ol class="toc"><li class="toc-item toc-level-2"><a class="toc-link" href="#This-is-why-we-can%E2%80%99t-have-nice-things"><span class="toc-text">This is why we can’t have nice things</span></a></li><li class="toc-item toc-level-2"><a class="toc-link" href="#AI-Slop"><span class="toc-text">AI Slop</span></a></li><li class="toc-item toc-level-2"><a class="toc-link" href="#Authoritarian-Boot-Stomping"><span class="toc-text">Authoritarian Boot Stomping</span></a></li><li class="toc-item toc-level-2"><a class="toc-link" href="#Misc-Technology"><span class="toc-text">Misc Technology</span></a></li><li class="toc-item toc-level-2"><a class="toc-link" href="#Of-Monsters-DevOps-and-Programming"><span class="toc-text">Of Monsters, DevOps, and Programming</span></a></li><li class="toc-item toc-level-2"><a class="toc-link" href="#Express-Yourself"><span class="toc-text">Express Yourself</span></a></li></ol>
|
||
</div>
|
||
</article>
|
||
|
||
|
||
<article class="card card-content categories-widget">
|
||
<div class="categories-card">
|
||
<div class="categories-header">
|
||
<i
|
||
class="iconfont icon-fenlei"
|
||
style="padding-right: 2px;">
|
||
</i>Categories
|
||
</div>
|
||
<div class="categories-list">
|
||
|
||
<a href="/categories/Books/">
|
||
<div class="categories-list-item">
|
||
Books
|
||
<span class="categories-list-item-badge">14</span>
|
||
</div>
|
||
</a>
|
||
|
||
<a href="/categories/Faith/">
|
||
<div class="categories-list-item">
|
||
Faith
|
||
<span class="categories-list-item-badge">6</span>
|
||
</div>
|
||
</a>
|
||
|
||
<a href="/categories/Outdoors/">
|
||
<div class="categories-list-item">
|
||
Outdoors
|
||
<span class="categories-list-item-badge">1</span>
|
||
</div>
|
||
</a>
|
||
|
||
<a href="/categories/Philosophy/">
|
||
<div class="categories-list-item">
|
||
Philosophy
|
||
<span class="categories-list-item-badge">1</span>
|
||
</div>
|
||
</a>
|
||
|
||
<a href="/categories/Leadership/">
|
||
<div class="categories-list-item">
|
||
Leadership
|
||
<span class="categories-list-item-badge">8</span>
|
||
</div>
|
||
</a>
|
||
|
||
<a href="/categories/History/">
|
||
<div class="categories-list-item">
|
||
History
|
||
<span class="categories-list-item-badge">1</span>
|
||
</div>
|
||
</a>
|
||
|
||
<a href="/categories/Liberal-Education/">
|
||
<div class="categories-list-item">
|
||
Liberal-Education
|
||
<span class="categories-list-item-badge">1</span>
|
||
</div>
|
||
</a>
|
||
|
||
<a href="/categories/Technology/">
|
||
<div class="categories-list-item">
|
||
Technology
|
||
<span class="categories-list-item-badge">7</span>
|
||
</div>
|
||
</a>
|
||
|
||
<a href="/categories/Current-Events/">
|
||
<div class="categories-list-item">
|
||
Current-Events
|
||
<span class="categories-list-item-badge">2</span>
|
||
</div>
|
||
</a>
|
||
|
||
<a href="/categories/Technology/Current-Events/">
|
||
<div class="categories-list-item">
|
||
Technology/Current-Events
|
||
<span class="categories-list-item-badge">1</span>
|
||
</div>
|
||
</a>
|
||
|
||
<a href="/categories/Technology/Current-Events/Philosophy/">
|
||
<div class="categories-list-item">
|
||
Technology/Current-Events/Philosophy
|
||
<span class="categories-list-item-badge">1</span>
|
||
</div>
|
||
</a>
|
||
|
||
</div>
|
||
</div>
|
||
</article>
|
||
|
||
<article class="card card-content tags-widget">
|
||
<div class="tags-card">
|
||
<div class="tags-header">
|
||
<i
|
||
class="iconfont icon-biaoqian"
|
||
style="padding-right: 2px;">
|
||
</i>hot tags
|
||
</div>
|
||
<div class="tags-list">
|
||
|
||
</div>
|
||
</div>
|
||
</article>
|
||
|
||
|
||
</div>
|
||
</aside>
|
||
<main class="main-column">
|
||
|
||
<article class="card card-content">
|
||
<header>
|
||
<h1 class="post-title">
|
||
News - 2026 - Week 3
|
||
</h1>
|
||
</header>
|
||
<div class="post-meta post-show-meta">
|
||
<time datetime="2026-01-23T12:00:51.000Z">
|
||
<i
|
||
class="iconfont icon-calendar"
|
||
style="margin-right: 2px;">
|
||
</i>
|
||
<span>2026-01-23</span>
|
||
</time>
|
||
|
||
<span class="dot"></span>
|
||
|
||
<a
|
||
href="/categories/Technology/"
|
||
class="post-meta-link">
|
||
Technology
|
||
</a>
|
||
|
||
<a
|
||
href="/categories/Technology/Current-Events/"
|
||
class="post-meta-link">
|
||
Current Events
|
||
</a>
|
||
|
||
<a
|
||
href="/categories/Technology/Current-Events/Philosophy/"
|
||
class="post-meta-link">
|
||
Philosophy
|
||
</a>
|
||
|
||
|
||
|
||
<span class="dot"></span>
|
||
<span>4.6k words</span>
|
||
|
||
</div>
|
||
|
||
</header>
|
||
<div
|
||
id="section"
|
||
class="post-content">
|
||
<p>Here’s my thoughts on news across the internet this week. It’s worth what you paid for it.</p>
|
||
<h2 id="This-is-why-we-can’t-have-nice-things"><a href="#This-is-why-we-can’t-have-nice-things" class="headerlink" title="This is why we can’t have nice things"></a>This is why we can’t have nice things</h2><p>If you didn’t know yet, apparently 12-15% of Americans are taking Ozempic for weight loss. And according to <a target="_blank" rel="noopener" href="https://www.travelweekly.com/Travel-News/Airline-News/Weight-loss-pills-could-fuel-airline-savings">a study by equity researchers at Jefferies</a>, the major airlines could apparently save money on fuel if we (as passengers) simply weighed less. I wonder if they will start offering GLP-1s from the beverage cart. “Coffee? Peanuts? Ozempic?” The best part about it is that we know that, regardless of what we as passengers do, and regardless of how much money the Airlines are making, any changes that come from this won’t benefit us - the passengers. The enshittification of everything has extended to airlines as well, and air travel has gotten exclusively worse over the last 30 years. Maybe if we all starve ourselves and live on a steady diet of ozempic, we can finally fit into an airline seat - though I expect that if we all get skinnier, the seats will too, and they’ll find some way to cram some poor skinny bastard between the window and the lavatory to get one extra ticket on the plane, and the weight savings are gone. We all know how this actually works.</p>
|
||
<p>If you can’t afford or don’t have access to ozempic, another good option for weight loss is available: parasites and bacterial infections that will make it impossible to keep food down or to keep yourself hydrated. They’re easy to get if you just start drinking dirty water. Dehydration, parasites and malnutrition go hand in hand in third world countries and their people are all really skinny. And, through a bizarre set of futurist legalistic golden handcuffs, <a target="_blank" rel="noopener" href="https://worksinprogress.co/issue/the-gold-plating-of-american-water/">American municipalities may be approaching a time when we have managed to price ourselves out of clean drinking water for the average citizen</a>. Imagine a future where we have engineered a system, through technological advances and legal regulation, wherein our citizens are too poor for clean water and sanitation services. </p>
|
||
<center>
|
||
<img alt="A resident of Flint, Michigan, digging for clean water" src="/images/lovelyfilth.jpeg"/>
|
||
<i>A Flint, Michigan resident digs for clean water</i>
|
||
</center>
|
||
|
||
<p>Nobody likes to talk about it much, but we (native westerners, at least) are so busy in our modern lives of optional starvation where we work multiple jobs to afford basic access to clean water, and so depressed at the state of things, and so isolated from each other, that we are not having enough babies. <a target="_blank" rel="noopener" href="https://publichealth.jhu.edu/2026/is-the-us-birth-rate-declining">It’s been in decline for about two decades now</a>, and it’s not a uniquely American phenomenon (Japan has been facing this crisis head-on for a full generation before us), but now we’re seeing some unexpected (though unsurprising) side effects of it here in the west. <a target="_blank" rel="noopener" href="https://www.bloomberg.com/graphics/2026-college-enrollment-cliff/">A bloomberg article reports</a> that many colleges are closing because there simply aren’t enough students to fill them. Now some of this might be due to the decline in the popularity of college education (since my generation, the zoomers, and gen Alpha have figured out that it has largely become a scam and does not guarantee you a better future), but the article posits that at least some amount is due to falling birth rates. Regardless, because of the declining student pool, apparently there has never been a better time to try to go to college; the remaining students are allowed to cut all kinds of corners so the colleges can keep their numbers up at all but the most elite institutions. But for those students who are in the colleges that are closing will probably not re-enroll, which is tragic, because studies show that those students typically end their college careers with the institution that closes.</p>
|
||
<p>If you DO have children (which I strongly recommend you DO), and they manage to maintain access to clean drinking water long enough to grow to adulthood (have lots of kids - it increases the chances that one will grow to adulthood), and they can stay skinny enough to book a flight on a private spaceflight, they may be able to get a job at the WalMart or Starbucks on the space station. <a target="_blank" rel="noopener" href="https://www.technologyreview.com/2026/01/12/1130697/10-breakthrough-technologies-2026/">MIT released a list of the most influential technologies in <em>current year</em></a>, and one thing they list is … commercial space stations. A California company, <a target="_blank" rel="noopener" href="https://www.vastspace.com/">Vast Space</a>, is launching a space station in May of this year via a SpaceX rocket. You can pay to live on this station for 10 days, assisting with conducting research, and testing drugs. (And who doesn’t want to pay to be a space guinea pig?! Not to be confused with <a target="_blank" rel="noopener" href="https://forgottenrealms.fandom.com/wiki/Miniature_giant_space_hamster">miniature giant space hamsters</a> or <a target="_blank" rel="noopener" href="https://www.youtube.com/watch?v=Nv9CkjkOyzo">rodents of unusual size</a>.) Future commercial space stations are designed to look like boutique hotels, and multiple companies will be launching them within the next few years. On a long enough timeline, there will be a wide variety of options to offer the experience to varying economic classes. I wonder what the Motel Six of space stations will be. At least they’ll leave the light on for you. And there will probably be a Starbucks nearby.</p>
|
||
<center>
|
||
<img alt="Fight Club : Planet Starbucks" src="/images/fightclubstarbucks.jpg"/>
|
||
<i>Planet Starbucks</i>
|
||
</center>
|
||
|
||
<h2 id="AI-Slop"><a href="#AI-Slop" class="headerlink" title="AI Slop"></a>AI Slop</h2><p>I’m told that going to space and spending extended time there can lead to some kind of space mania. If you’re too poor to be able to afford some private space travel, don’t worry, you can go crazy right here at home thanks to our latest technological marvel, the Large Language Model. <a target="_blank" rel="noopener" href="https://mkultra.monster/ai/2026/01/18/i-experimented-on-myself-with-ai/">cmdr-nova experimented on themselves so you don’t have to</a>, and they report a highly successful experiment in which they induced AI psychosis in themselves by regularly engaging with their personal AI as if it were a friend and confidant. They point out the dangers of isolation, and how reliance on AI can increase this, and how quickly it can all spiral out of control. Like many things, it can be too late before you spot it. This may sound silly, but: do you have some friends that have suddenly fallen off the radar? Reach out to them. Go physically find them. Get some coffee with them. Spend some time with them. They might not be alright. <em>Are you alright?</em></p>
|
||
<p>I think that LLMs are actually in some kind of uncanny valley space right now. If we hadn’t gotten used to interacting with each other through text several decades ago, they might seem more creepy than they do, and the effects of AI psychosis might be easier to stave off. Would we be okay with a real person behaving like an AI does? I am not sure. But <a target="_blank" rel="noopener" href="https://aclanthology.org/2025.emnlp-main.1237/?ref=foommagazine.org">A report in ACL Anthology</a> shows that LLMs show some resemblance to our own smartmeat - at least to certain brain regions, but there’s not a lot of resemblance. Just enough to make it worth commenting on. They do make the assumption that, given the current rate of technological advance continues, this resemblance will likely only become stronger over time. So this means that, as LLMs become an increasingly large part of our world, we are starting to actually live inside of a construct of this artificial brain. As the report says, “However, if such comparisons are valid, then they would suggest, somewhat dramatically, that we are increasingly surrounded by a synthetic braintech. A technology not just as capable as the human brain, in some ways, but actually made up of similar components.” I don’t think I like that.</p>
|
||
<p>Speaking of things I don’t like, and things that seem almost intelligent but aren’t really, <a target="_blank" rel="noopener" href="https://thenewstack.io/the-future-of-ai-in-sre-preventing-failures-not-fixing-them/">whoever is writing these AI SRE articles over at The New Stack</a> doesn’t really understand SRE. They (and by “they” I mean “several authors who write these articles”, as I have witnessed it from several authors, not just the one I linked) keep saying “SRE is moving away from reaction and towards prevention, and AI will get us there!”, or “SRE needs to remember context, guardrails and business rules as they try to use AI to move from reaction to prevention”. And they’re saying it like ANY of these are new concepts. Hogwash! These are the very same problems SRE has been grappling with since the beginning. Don’t believe me? <a target="_blank" rel="noopener" href="https://sre.google/sre-book/table-of-contents/">Go read the Google SRE book</a> - they literally wrote the book. When has SRE NOT been about preventing problems in the first place - doesn’t anyone remember SLOs and Error Budgets? When has SRE NOT been about providing context around operations? When has any of this been unique to the age of AI? These authors keep reducing the traditional SRE role down to (forgive me, ops friends) an operations person staring at Nagios screens. Who are these people and how are they given a platform to spew their nonsense from? It’s offensive.</p>
|
||
<p>Thankfully, not EVERY New Stack author writing on this topic is a midwit. <a target="_blank" rel="noopener" href="https://thenewstack.io/ai-sre-roundtable-the-creation-of-a-new-category/">Mr LaGreco, for example, has a much more realistic take on the whole thing</a>. Ironically, he’s one of the few authors on their website in recent memory, who wrote about SRE, who didn’t have “SRE” in his job title soup in his author bio. SREs, check on your friends, cause a bunch of them are out here doing your entire career field dirty. And when you wonder “Why did everyone think AI could replace us here?”, you’ll have those folks to blame.</p>
|
||
<center><img alt="You played yourself" src="/images/playedyourself.jpeg"/></center>
|
||
|
||
<p>Although we all know that eventually the only way for AIs and humans to operate successfully in the same space will be … for humans to stop operating, and just let AI do everything, because we are too unpredictable. <a target="_blank" rel="noopener" href="https://www.msn.com/en-us/news/us/officials-showed-off-a-robo-bus-in-dc-it-got-hit-by-a-tesla-driver/ar-AA1UmQno">A recent incident in DC involving a human crashing into an autonomous vehicle</a> makes this point very well. At some point, a room full of insurance company execs, dept of transportation officials, and robotics experts will ask themselves, “With autonomous vehicles emerging, how can we make the road safe?”. The room will descend into silence for a moment, before the AI assistant will speak from the conference room speaker. “Remove all the humans from the roadway, of course.” And there will be much back-patting and congratulating.</p>
|
||
<p>The big problem we have to get over is that we simply can’t trust AI. Diving into development topics for a moment, <a target="_blank" rel="noopener" href="https://thenewstack.io/enabling-autonomous-agents-with-environment-virtualization/">there’s some work to be done wherein autonomous AI agents developing systems need to be given synthetic virtual environments where they can test their work</a>. I fundamentally agree with the need for this, and think it will probably improve the quality of output from the average AI agent, but there’s still a fundamental trust question: how can we trust that the AI has actually executed the tests it is reporting, and who designed the test? Was the test designed by more AI? What’s to stop AI from hallucinating literally everything? For right now there is no good way for a human to get out of the verification loop, because unless we are able to implicitly trust an AI, the way that we would implicitly trust a human, we cannot escape the need to have someone looking over the AI’s shoulder, who understands what it is doing well enough to know if it’s tests are valid, if its controls are being adhered to, and whether it is hallucinating or outright lying to you. Pretending otherwise is blind foolishness.</p>
|
||
<center>
|
||
<i>
|
||
"You are confused because you do not understand Tao. <br/>
|
||
Only a fool expects rational behavior from his fellow humans. <br/>
|
||
Why do you expect it from a machine that humans have constructed? <br/>
|
||
Computers simulate determinism; only Tao is perfect."<br/>
|
||
<br/>
|
||
<a target="_blank" rel="noopener" href="https://www.mit.edu/~xela/tao.html">The Tao of Programming, 4.2</a><br/><br/>
|
||
</i>
|
||
</center>
|
||
|
||
<p>Meanwhile, if you aren’t getting a job, AI may be the reason why, and it may be because (ironically) AI doesn’t trust you enough. <a target="_blank" rel="noopener" href="https://yro.slashdot.org/story/26/01/21/1841214/ai-company-eightfold-sued-for-helping-companies-secretly-score-job-seekers?utm_source=rss1.0mainlinkanon&utm_medium=feed">A company called Eightfold has been sued for helping companies score job seekers with AI</a>. Although, to be honest, I’m not sure how far this case is going to go; To be clear, job seekers have always been scored by lots of metrics that they know about like credit scores and references and length of experience at prior jobs and skill trees etc etc. What we object to is being scored by a secret agent that we have no knowledge of using metrics we have no control over and which it may not have permission to access. But I don’t think the legal precedent here is going to be good: employers are free to score you internally how ever they want, as long as they’re doing it the same to everyone, and not violating any laws in the process. Still, I have this idea that we can improve the hiring experience by extending the idea of the Web of Trust to resumes, job histories, professional networks, resumes and applicant tracking systems. I need to put an RFC out about it. </p>
|
||
<p>Speaking of trust issues and AI, I reported last week that Apple is upset about slow adoption of iOS 26. Apparently that failure wasn’t enough for them, and <a target="_blank" rel="noopener" href="https://9to5mac.com/2026/01/21/apple-reportedly-replacing-siri-interface-with-actual-chatbot-experience-for-ios-27/">in iOS 27 they’re replacing Siri with an AI chatbot</a>. It’s good to have some things determined ahead of time, for example, that I won’t be installing iOS 27 on my device. I have a rooted android which, if a few things pan out, I’ll be transitioning back over to soon.</p>
|
||
<p><a target="_blank" rel="noopener" href="https://slashdot.org/story/26/01/21/2055248/nova-launcher-gets-a-new-owner-and-ads?utm_source=rss1.0mainlinkanon&utm_medium=feed">Speaking of mobile phone updates, novalauncher is getting ads</a>. The app was recently acquired, and apparently the app needs “a sustainable business model”. I don’t get it. The app is written. The features are shipped. Don’t get me wrong, <i>though a program be but three lines long, some day it must be maintained</i>. But how much maintenance is needed? And of that maintenance, how much is needed only because new OS versions keep changing shit? Does it really justify sending ads to your users? I am not a novalauncher user, so maybe I just don’t get it, but this seems like it should be a non-issue.</p>
|
||
<h2 id="Authoritarian-Boot-Stomping"><a href="#Authoritarian-Boot-Stomping" class="headerlink" title="Authoritarian Boot Stomping"></a>Authoritarian Boot Stomping</h2><p>Meanwhile, in Ireland, <a target="_blank" rel="noopener" href="https://www.theregister.com/2026/01/21/ireland_wants_to_give_police/">The authoritarians continue to wage war against effective encryption</a> by insisting they be given back doors to encryption and be allowed to deploy and use spyware against their own citizens. But they insist it’s okay and that you should totally trust them, bro, there’ll be a robust legal framework. (Don’t trust them, there won’t be a robust legal framework, and if there is, it will protect the state, not the people.)</p>
|
||
<p>In a great example of why you shouldn’t trust anyone (let alone the state) with a spy apparatus, <a target="_blank" rel="noopener" href="https://yro.slashdot.org/story/26/01/17/0718211/what-happened-after-security-researchers-found-60-flock-cameras-livestreaming-to-the-internet?utm_source=rss1.0mainlinkanon&utm_medium=feed">a hilarious (and depressing) incident involving 60 Flock traffic cameras</a> shows both a lack of capability and a vicious response when told about it. Researchers found 60 flock cameras that were unsecured and livestreaming to the internet, and when they tried to tell big brother about the problem, they got fired, harassed, deplatformed, and maybe arrested. <i>“If you want a picture of the future, imagine a boot stamping on a human face - forever” –George Orwell</i> … and it will be televised, apparently, through incompetence rather than intentional malice.</p>
|
||
<p>Speaking of people getting punished for observing and recording things left in plain sight, Anna’s Archive (<a target="_blank" rel="noopener" href="https://open-slum.pages.dev/">go here to find a working link to the site</a>) has been <a target="_blank" rel="noopener" href="https://torrentfreak.com/u-s-court-order-against-annas-archive-spells-more-trouble-for-the-site/">ordered to take down everything that they copied through scraping publicly available content</a>. The court says they violated ToS by <a target="_blank" rel="noopener" href="https://torrentfreak.com/annas-archive-scraped-worldcat-to-help-preserve-all-books-in-the-world-231003/">creating this archive (which was done with the intent of preserving all the books in the world as a public digital archive)</a>. You know, a ToS - Terms of Service - thing you have to click “I Agree” to before installing some software. It creates a legal agreement between you the user and them the provider stipulating what is and is not acceptable use. What’s interesting here is that there was never an agreement between the site operators at Anna’s Archive and the content providers, so no ToS was established. The ruling here sets new precedent in US law, in that you can be punished for violating the rules in a Term of Service to which you never actually agreed. They can say “these are our rules, and even though you never agreed, and even though we can’t prove you knew those rules, and even though we left the content available in such a way that you stumbling upon it would violate our rules, you have done wrong and owe us damages”. Absolute madness, and another symptom of the death of the commons.</p>
|
||
<p>Maybe we just have the wrong authoritarians in charge. It’s easy to think that we would do it differently. If only I was the benevolent dictator for life, things would be great. One thing I know for sure, <a target="_blank" rel="noopener" href="https://news.slashdot.org/story/26/01/22/006212/america-is-slow-walking-into-a-polymarket-disaster?utm_source=rss1.0mainlinkanon&utm_medium=feed">if I was in charge, financial speculation would be illegal</a>. It is the source of many great catastrophes in our society, and will definitely be the source of many more. Indeed, we are slow walking into a polymarket disaster.</p>
|
||
<center><img alt="Dr Horrible would do things differently" src="/images/horrible-rule.jpg"/></center>
|
||
|
||
<h2 id="Misc-Technology"><a href="#Misc-Technology" class="headerlink" title="Misc Technology"></a>Misc Technology</h2><p>But, alas, we are not authoritarians in the position to apply the boot to the face, so let’s focus on what’s within our own scope.</p>
|
||
<p>If you want to keep your smart dishwasher, pet IoT device, or even your fleet of 60 Flock cameras away from the internet, Dog with a Dev blog has an outstanding write-up on <a target="_blank" rel="noopener" href="https://blog.cani.ne.jp/2026/01/17/all-it-took-was-broken-firmware.html">how they isolated their IoT devices onto their own network subnet within their home</a>. Most people will not be willing to go to this much trouble, and I prefer to simply not own IoT devices, but if you have them, this is well worth the time.</p>
|
||
<p>If you’re an administrator of any systems that use Net-NTLMv1 password hashes, or if you’re a malevolent actor trying to break into such a system, then you are in odd company today, as <a target="_blank" rel="noopener" href="https://cloud.google.com/blog/topics/threat-intelligence/net-ntlmv1-deprecation-rainbow-tables">Google has just released 8 trillion precomputed NTLMv1 password hashes</a>. This makes the job of cracking simple passwords in this schema much easier (12 hours on commodity hardware), and makes the task of migrating away from this password scheme much more imperative. “While tools to exploit this protocol have existed for years, they often required uploading sensitive data to third-party services or expensive hardware to brute-force keys.” Basically Google is saying “we don’t like this scheme, you aren’t retiring it fast enough, so we’re going to show you how bad it is by helping out every bad guy by removing one of the big barriers to entry”. I honestly think that this is a really irresponsible response to the problem, and anyone who can trace a system intrusion back to a broken NTLMv1 hash (if such a positive identification was even possible) should be able to hold Google at least partially responsible. NTLMv1 is weak and we all know it, in the same way that we know that the average residential lock is weak and that there are actually only a few million variations of key to the average home’s front door lock; but that doesn’t make it okay to release a tool that can rapidly try every possible key combination in a matter of minutes, and then smugly say “We told you your locks are shit, and now you are in even more danger, so change them”. Maybe I’m alone in this, but I really think poorly of them for this.</p>
|
||
<p>Speaking of things that you can only do on really expensive hardware, like brute forcing effective encryption, <a target="_blank" rel="noopener" href="https://www.nvidia.com/en-us/products/workstations/dgx-spark/?utm_source=the+new+stack&utm_medium=referral&utm_content=inline-mention&utm_campaign=tns+platform">NVidia has released some new DGX Spark workstations</a> that look like they can do some really really neat stuff for a single developer without having to resort to cloud resources or even resources racked in the datacenter. There’s a price tag, to be sure, but high end developer workstations have always been expensive. These NVidia DGX Spark systems are comparable (and likely exceed) current high-end macbooks and mac studio systems (which are the only ones I’m comparing here because Apple Silicon has a unified memory architecture while PC does not), and offer as good or better performance on AI workloads. Honestly the price point is kind of crazily affordable in terms of what it can do. I wonder if we’ll start seeing companies ship these to their developers instead of commodity macbooks? Excuse me, I need to write an email…</p>
|
||
<p>One of the good things about the current AI arms race is that we are seeing innovation in computing for the first time in quite a while, although that innovation tends to be new takes on old problems. <a target="_blank" rel="noopener" href="https://thenewstack.io/why-d-matrix-bets-on-in-memory-compute-to-break-the-ai-inference-bottleneck/">A company called d-Matrix is trying something new to solve the old problem of reducing the time spent accessing and operating on memory</a>. For decades we tried to make compute faster by moving more and more memory onto the processor in the form of larger and larger caches. This allowed us to spend less and less time fetching from memory and writing back to memory, as we could cache entire pages physically next to the processor circuitry, reducing time spent off-die. But d-Matrix is asking why not just take some portion of the compute circuitry, and embed it directly with the memory? … Interesting idea, I’m honestly really curious to see how it plays out, and how it works in practice.</p>
|
||
<p>On the other end of the spectrum, the children yearn for the old ways, and <a target="_blank" rel="noopener" href="https://tilde.club/">people are discovering shared hosting on unix servers with shell accounts over at tilde.club</a>. Those of us who remember getting online back in the 90s will remember your local ISP giving you a shell account on a UNIX (or Linux) box running a web server, and a <code>~/public_html/</code> directory where you could upload a little website. Apparently this is being rediscovered, as everything old is new again. People are excited about being able to log on to the system, learn shell, and publish websites, without having to change their OS. This is their first exposure to shell for many of them. And the service has a built-in IRC server for chat inside the terminal, which - again - is nothing new for us old hands, but I love that people are discovering this. Things like this always get me so excited! I love seeing people discover the technology and the internet and the culture that still exists underneath the monster that has grown out of our good intentions, and I wish I had the attention available to participate in something like this and mentor some of these folks. I suppose I’m unwilling to sacrifice other things to devote attention to such an effort. But I’m thrilled to see that it’s alive and well and people are excited by it.</p>
|
||
<center>
|
||
<img alt="Steve Wozniak teaching elementary students about computers" src="/images/woz-teaching-kids.webp"/><br/>
|
||
<i>Steve Wozniak teaching elementary students about computers in 1995</i>
|
||
</center>
|
||
<br/>
|
||
|
||
<h2 id="Of-Monsters-DevOps-and-Programming"><a href="#Of-Monsters-DevOps-and-Programming" class="headerlink" title="Of Monsters, DevOps, and Programming"></a>Of Monsters, DevOps, and Programming</h2><p>Speaking of the monsters that grew out of our good intentions, apparently the curl bug report policy has been changed. They were inundated with AI slop bug reports, so they had to <a target="_blank" rel="noopener" href="https://curl.se/.well-known/security.txt">adopt a new security bug reporting statement</a>. What caught my attention though was <a target="_blank" rel="noopener" href="https://news.ycombinator.com/item?id=46718329">a comment on the hackernews story</a> raises the question of whether or not our current “open source ecosystem” is an accurate representation of what the founders originally envisioned. Maybe it’s not? Is it better, worse? Should we go back to posting tarballs on our websites and taking patches by email? Sometimes, I think, maybe, because the older ways of doing it kept out the riffraff. One commenter sums it up nicely by saying “Bitching is free and easier than making pull requests”. At the same time, just because we wrote something once, that doesn’t mean we’re going to commit to maintaining it forever. Sometimes the butterfly flaps its wings, and ripples go out …. is the butterly responsible for continuous flapping to change ripples for everyone who sees it?</p>
|
||
<p>Speaking of web tools and code, <a target="_blank" rel="noopener" href="https://astro.build/blog/astro-6-beta/">Astro 6 just dropped</a>. Astro is (yet another) web framework (as if we didn’t already have enough). What sets Astro apart? <i>“If you need a website that loads fast with great SEO, then Astro is for you.”</i> I don’t really have a bone to pick with Astro (<a target="_blank" rel="noopener" href="https://www.cloudflare.com/press/press-releases/2026/cloudflare-acquires-astro-to-accelerate-the-future-of-high-performance-web-development/">and apparently Cloudflare recently bought them so they’re doing quite well</a>), they just happened to pop up on my radar, and while reading the article, a continuous itch resurfaced about what it’s like working with anything on the modern web. The itch applies particularly to my own website here, and its own use of a small microblogging framework named <a target="_blank" rel="noopener" href="https://hexo.io/">hexo</a>. Honestly, the more I think about it, the more I want to throw everything out and go to bare HTML. I’m kind of sick to death of frameworks, although hexo <em>mostly</em> stays out of my way. I just get so tired of working through someone else’s vision and interface to your browser to express my ideas and say what I want to say. It’s all so tiresome. And there’s a new framework every day, it seems like. Why? <em>“We’re a generation of programmers raised by frameworks. I’m not sure another framework is the answer to our problems.” – Chuck Palahniuk, probably.</em> </p>
|
||
<p>In Kubernetes news, <a target="_blank" rel="noopener" href="https://kubernetes.io/blog/2026/01/22/headlamp-in-2025-project-highlights/">Headlamp is part of the UI SIG now</a>. Which is nice, because the kubernetes interface is pretty shit for users (it was never actually meant for humans), and not even that great for developers (though we can figure it out). <a target="_blank" rel="noopener" href="https://kubernetes.io/blog/2026/01/21/introducing-checkpoint-restore-wg/">Kubernetes is also going to be able to snapshot containers</a>, the same way we’ve been snapshotting VMs, and suspending/hibernating bare metal to disk. Remember when containers were small, lightweight, and the idea of snapshotting one was silly? Yeah …. me too. There is nothing new under the sun, and kubernetes will kill docker right after docker containers kill VMs right after VMs kill bare metal right after bare metal kills the mainframe, but not before docker containers in kubernetes implement a checkpoint feature like VMs have. It’s turtles all the way down, and we keep solving the same problems over and over again by throwing on new shit that does the old shit. NYET! Rifle is fine!</p>
|
||
<h2 id="Express-Yourself"><a href="#Express-Yourself" class="headerlink" title="Express Yourself"></a>Express Yourself</h2><p><a target="_blank" rel="noopener" href="https://shellsharks.com/pesos">Mike Sass posits that we should use 3rd party platforms to originate our content</a>, and our own websites should serve as archives or mirrors. He thinks this “PESOS” model is better than the POSSE model (Publish Own Site, Syndicate Elsewhere). I obviously don’t agree, but I suppose it’s worth considering. He’s solving a different problem: he wants his content to remain if the services go away, while POSSE users want to <em>own our content</em> and <em>control how that content is presented</em>, while having the option to leverage third party services to give others the opportunity to see and experience our content. While there is a productive merit in the PESOS philosophy, I find it fundamentally at odds with my own, and cannot endorse it.</p>
|
||
<p><a target="_blank" rel="noopener" href="https://sonechka.bouvardia.blue/blog/modern-art-is-fun">Sonechka, on their personal blog, makes the point that art must be fun</a>. I agree. I think this extends to scientific ‘arts” as well like programming - if there is an “art” of computer programming, then this statement is equally valid for your programs: <i>“Make art that is a waste of time, that no one wants to buy or sell. Make art that is useless and make art that is meaningless; art that is fun.”</i> Do it because you love it, not because you think it can be monetized or profitable or even that the time is productive. Experience joy in the interaction between you and the system, and in the creative act, as the ultimate goal is not to be productive, but to express yourself.</p>
|
||
<center><iframe width="560" height="315" src="https://www.youtube.com/embed/OFyZ4HiLbl0?si=BhO_8-fmX-AWbB1B" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></center>
|
||
|
||
</div>
|
||
<div>
|
||
|
||
</div>
|
||
</article>
|
||
<div class="nav">
|
||
|
||
|
||
<div class="nav-item-next">
|
||
<a
|
||
href="/2026/01/19/This-Old-Tool-cmdarg/"
|
||
class="nav-link">
|
||
<div>
|
||
<div class="nav-label">Next</div>
|
||
|
||
<div class="nav-title">This Old Tool : cmdarg </div>
|
||
|
||
</div>
|
||
<i class="iconfont icon-right nav-next-icon"></i>
|
||
</a>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<div
|
||
class="card card-content toc-card"
|
||
id="mobiletoc">
|
||
<div class="toc-header">
|
||
<i
|
||
class="iconfont icon-menu"
|
||
style="padding-right: 2px;">
|
||
</i>TOC
|
||
</div>
|
||
<ol class="toc"><li class="toc-item toc-level-2"><a class="toc-link" href="#This-is-why-we-can%E2%80%99t-have-nice-things"><span class="toc-text">This is why we can’t have nice things</span></a></li><li class="toc-item toc-level-2"><a class="toc-link" href="#AI-Slop"><span class="toc-text">AI Slop</span></a></li><li class="toc-item toc-level-2"><a class="toc-link" href="#Authoritarian-Boot-Stomping"><span class="toc-text">Authoritarian Boot Stomping</span></a></li><li class="toc-item toc-level-2"><a class="toc-link" href="#Misc-Technology"><span class="toc-text">Misc Technology</span></a></li><li class="toc-item toc-level-2"><a class="toc-link" href="#Of-Monsters-DevOps-and-Programming"><span class="toc-text">Of Monsters, DevOps, and Programming</span></a></li><li class="toc-item toc-level-2"><a class="toc-link" href="#Express-Yourself"><span class="toc-text">Express Yourself</span></a></li></ol>
|
||
</div>
|
||
|
||
</main>
|
||
<aside class="right-column">
|
||
<div class="sticky-widescreen">
|
||
|
||
|
||
<article class="card card-content toc-card">
|
||
<div class="toc-header">
|
||
<i
|
||
class="iconfont icon-menu"
|
||
style="padding-right: 2px;">
|
||
</i>TOC
|
||
</div>
|
||
<ol class="toc"><li class="toc-item toc-level-2"><a class="toc-link" href="#This-is-why-we-can%E2%80%99t-have-nice-things"><span class="toc-text">This is why we can’t have nice things</span></a></li><li class="toc-item toc-level-2"><a class="toc-link" href="#AI-Slop"><span class="toc-text">AI Slop</span></a></li><li class="toc-item toc-level-2"><a class="toc-link" href="#Authoritarian-Boot-Stomping"><span class="toc-text">Authoritarian Boot Stomping</span></a></li><li class="toc-item toc-level-2"><a class="toc-link" href="#Misc-Technology"><span class="toc-text">Misc Technology</span></a></li><li class="toc-item toc-level-2"><a class="toc-link" href="#Of-Monsters-DevOps-and-Programming"><span class="toc-text">Of Monsters, DevOps, and Programming</span></a></li><li class="toc-item toc-level-2"><a class="toc-link" href="#Express-Yourself"><span class="toc-text">Express Yourself</span></a></li></ol>
|
||
</article>
|
||
|
||
|
||
<article class="card card-content">
|
||
<div class="recent-posts-card">
|
||
<div class="recent-posts-header">
|
||
<i
|
||
class="iconfont icon-wenzhang_huaban"
|
||
style="padding-right: 2px;">
|
||
</i>Recent Posts
|
||
</div>
|
||
<div class="recent-posts-list">
|
||
|
||
<div class="recent-posts-item">
|
||
<div class="recent-posts-item-title">2026-01-23</div>
|
||
<a href="/2026/01/23/News-2026-Week-3/"><div class="recent-posts-item-content">News - 2026 - Week 3</div></a>
|
||
</div>
|
||
|
||
<div class="recent-posts-item">
|
||
<div class="recent-posts-item-title">2026-01-19</div>
|
||
<a href="/2026/01/19/This-Old-Tool-cmdarg/"><div class="recent-posts-item-content">This Old Tool : cmdarg</div></a>
|
||
</div>
|
||
|
||
<div class="recent-posts-item">
|
||
<div class="recent-posts-item-title">2026-01-16</div>
|
||
<a href="/2026/01/16/News-2026-Week-2/"><div class="recent-posts-item-content">News-2026-Week-2</div></a>
|
||
</div>
|
||
|
||
<div class="recent-posts-item">
|
||
<div class="recent-posts-item-title">2026-01-10</div>
|
||
<a href="/2026/01/10/libakerror/"><div class="recent-posts-item-content">libakerror</div></a>
|
||
</div>
|
||
|
||
</div>
|
||
</div>
|
||
</article>
|
||
|
||
|
||
</div>
|
||
</aside>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<footer class="footer">
|
||
<div class="footer-container">
|
||
<div>
|
||
<div class="footer-dsc">
|
||
<span>
|
||
Copyright ©
|
||
|
||
|
||
-
|
||
2026
|
||
|
||
</span>
|
||
|
||
<a
|
||
href="mailto:andrew@aklabs.net"
|
||
class="footer-link">
|
||
Andrew Kesterson
|
||
</a>
|
||
<br/>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="footer-dsc">
|
||
|
||
Powered by
|
||
<a
|
||
href="https://hexo.io/"
|
||
class="footer-link"
|
||
target="_blank"
|
||
rel="nofollow noopener noreferrer">
|
||
Hexo
|
||
</a>
|
||
|
||
|
||
<span> | </span>
|
||
|
||
|
||
Theme -
|
||
<a
|
||
href="https://github.com/theme-kaze"
|
||
class="footer-link"
|
||
target="_blank"
|
||
rel="nofollow noopener noreferrer">
|
||
Kaze
|
||
</a>
|
||
|
||
</div>
|
||
|
||
|
||
|
||
|
||
</footer>
|
||
|
||
|
||
<a
|
||
role="button"
|
||
id="scrollbutton"
|
||
class="basebutton"
|
||
aria-label="回到顶部">
|
||
<i class="iconfont icon-arrowleft button-icon"></i>
|
||
</a>
|
||
|
||
<a
|
||
role="button"
|
||
id="menubutton"
|
||
aria-label="menu button"
|
||
class="basebutton">
|
||
<i class="iconfont icon-menu button-icon"></i>
|
||
</a>
|
||
<a
|
||
role="button"
|
||
id="popbutton"
|
||
class="basebutton"
|
||
aria-label="控制中心">
|
||
<i class="iconfont icon-expand button-icon"></i>
|
||
</a>
|
||
<a
|
||
role="button"
|
||
id="darkbutton"
|
||
class="basebutton darkwidget"
|
||
aria-label="夜色模式">
|
||
<i class="iconfont icon-weather button-icon"></i>
|
||
</a>
|
||
<a
|
||
role="button"
|
||
id="searchbutton"
|
||
class="basebutton searchwidget"
|
||
aria-label="搜索">
|
||
<i class="iconfont icon-search button-icon"></i>
|
||
</a>
|
||
|
||
|
||
|
||
<script>
|
||
var addImgLayout = function () {
|
||
var img = document.querySelectorAll('.post-content img')
|
||
var i
|
||
for (i = 0; i < img.length; i++) {
|
||
var wrapper = document.createElement('a')
|
||
wrapper.setAttribute('href', img[i].getAttribute('data-src'))
|
||
wrapper.setAttribute('aria-label', 'illustration')
|
||
wrapper.style.cssText =
|
||
'width: 100%; display: flex; justify-content: center;'
|
||
if (img[i].alt) wrapper.dataset.caption = img[i].alt
|
||
wrapper.dataset.nolink = true
|
||
img[i].before(wrapper)
|
||
wrapper.append(img[i])
|
||
var divWrap = document.createElement('div')
|
||
divWrap.classList.add('gallery')
|
||
wrapper.before(divWrap)
|
||
divWrap.append(wrapper)
|
||
}
|
||
baguetteBox.run('.gallery')
|
||
}
|
||
</script>
|
||
<script>
|
||
loadScript(
|
||
"/js/lib/lightbox/baguetteBox.min.js",
|
||
addImgLayout
|
||
)
|
||
</script>
|
||
|
||
|
||
|
||
<script src="/js/main.js"></script>
|
||
|
||
|
||
<script>
|
||
var addLazyload = function () {
|
||
var observer = lozad('.lozad', {
|
||
load: function (el) {
|
||
el.srcset = el.getAttribute('data-src')
|
||
},
|
||
loaded: function (el) {
|
||
el.classList.add('loaded')
|
||
},
|
||
})
|
||
observer.observe()
|
||
}
|
||
</script>
|
||
<script>
|
||
loadScript('/js/lib/lozad.min.js', addLazyload)
|
||
</script>
|
||
|
||
<script src="//instant.page/5.1.0" type="module"
|
||
integrity="sha384-by67kQnR+pyfy8yWP4kPO12fHKRLHZPfEsiSXR8u2IKcTdxD805MGUXBzVPnkLHw"></script>
|
||
|
||
<script>
|
||
var googleAnalytics = function () {
|
||
window.dataLayer = window.dataLayer || []
|
||
function gtag() {
|
||
dataLayer.push(arguments)
|
||
}
|
||
gtag('js', new Date())
|
||
gtag('config', 'G-S3YLF516N6')
|
||
}
|
||
</script>
|
||
<script>
|
||
loadScript(
|
||
'https://www.googletagmanager.com/gtag/js?id=' +
|
||
'G-S3YLF516N6',
|
||
googleAnalytics
|
||
)
|
||
</script>
|
||
|
||
|
||
</body>
|
||
</html>
|