Microsoft’s July 13 Office certificate deadline is not a data-loss scare. It is an inventory problem. Old Office apps, unsupported macOS/iPadOS versions, and stale check-ins hurt admins. What to check now: joshie.com/office-mac-ipad-j…

Summon for CT 🎉🎉

This is gonna be 🍌🍌🍌 🚀

WWDC got me. I tried to install macOS 27, then remembered my 2019 MacBook Pro is Intel. Oof. I wrote about the personal upgrade and the fleet lesson: Intel Macs, Rosetta, app readiness, and hardware refresh plans. joshie.com/my-2019-macbook-p…

Microsoft’s June patch release is noisy enough that the CVE count stops being useful. I wrote about how I’d triage it: exposure first, pilot groups, proof of install/restart, third-party apps, and the exceptions hiding outside the happy path. joshie.com/microsoft-june-20…

Windows 10 EOS does not mean every old PC needs replacing. Browser-first roles may fit ChromeOS Flex if the model is certified, the workload is tested, and management is planned. joshie.com/before-replacing-…

Chrome 149 shipped with 429 security fixes. For endpoint admins, the question is: which devices actually updated? I wrote about the report I would want first: version, last check-in, update path, and intentional holds. joshie.com/chrome-149-browse…

Hermes Agent v0.16.0 - “The Surface Release” Changelog below:

Resuming a session or doing `hermes -c` to reopen the most recent session will now relaunch it in the dir it was launched in originally

Microsoft’s 2011 Secure Boot certs start expiring in June 2026. I would not treat this as just another patching item. Inventory the fleet: firmware, Secure Boot state, UEFICA2023Status, errors, BitLocker/recovery readiness, pilots, and exceptions. joshie.com/secure-boot-certi…

Googlebook may end up being a fun device category. Fine. For endpoint admins, the useful question is whether it fits the management stack they already use or creates another weird corner of the fleet. joshie.com/googlebook-endpoi…

Big news from FileWave: founder Nurdan Eris has returned as CEO, with Nikola Gander joining as Co-CEO to lead our next phase of growth. We’re doubling down on secure, sovereign, cross-platform endpoint management. The best of FileWave is still ahead. hubs.ly/Q04j1vrG0

Last night I did the thing you’re probably not supposed to do casually: I shut down my working OpenClaw setup and moved over to Hermes. This started because I saw the @NetworkChuck video about OpenClaw -> Hermes, got curious, watched a few more videos, and then ended up going down the rabbit hole on Hermes. One of the migration videos made me a little nervous, honestly. Not because the process looked impossible, but because this is one of those tools that slowly becomes part of how you work. Breaking it would be annoying. So I took it carefully. First step: full backup of my entire ~/.openclaw directory, including the projects sitting under the old OpenClaw workspace. Then I ran the Hermes migration command. The pleasant surprise was that my API keys and Telegram bot config came across cleanly enough that I could keep using the same bot, just backed by Hermes instead of OpenClaw. The cleanup work was mostly what you’d expect: - old paths like ~/.openclaw/workspace/projects needed to become ~/HermesWorkspace/projects - a few tools had hardcoded assumptions that needed updating - LaunchAgents needed path fixes - one daily process needed adjustment - a couple recurring workflows needed sanity checks As of now, I’m about 99% migrated and using Hermes full time all day today. I didn’t switch just because it was the next shiny thing. Hermes actually existed before OpenClaw, even though OpenClaw got more of the early attention. What pulled me in was Hermes’s self-improvement model, skill building, and the way it curates memory instead of just piling context into a junk drawer. Also, on the same Mac, with the same GPT-5.5 model, Hermes feels faster and less bloated in actual use. I wrote up the more technical version here: joshie.com/migrating-from-op… Short version: back up first, migrate second, then audit anything that still assumes ~/.openclaw exists.

Thank you @Tesla for listening and making the FSD reporting dialog a million times less annoying. 2026.2.9.10 version came last night. I still don't think the prompt was the right way to go but at least now it doesn't block my view of the screen.

This is bananas. I get image gen via OAuth now. 🦞🎉❤️

Dist 20,13,19,21,11 Victor 12 Large Brush fire In the area of Dennison rd and Fire tower rd. Weatherly 2302hrs Per 2005 dispatch 13,19,21,11 for brush trucks

Amazing

Supporting multiple platforms is easy to claim. Operating them consistently is harder. Our latest blog looks at why multi-platform strategies break down in hybrid IT environments — and what real control actually requires. Read more: hubs.ly/Q04cCd4b0 #UEM

Does the CCS to NACS adapter now fit on a Cybertruck? shop.tesla.com/product/ccs1-… there is an image there of it in a CT. Anyone have the latest adapter? Just curious because in the images in the shop it clearly shows a CT with it.

Hey @elonmusk, I really hope you see this message and look into it. I think every 2024 Foundation Series Cybertruck and all Cybertrucks after should get the 7 year / 70,000 mile high priced propulsion related warranty retroactively applied. A lot of early Foundation Series owners had their trucks plagued with issues. Many of us still believe in the future of the truck and we're holding on to ours and encouraging others to buy. Early FS owners didn't get free Supercharging like later FS owners did. And now with this extended warranty for 2026 Cybertrucks and newer, that's why you're seeing comments about early owners feeling like they got screwed. No customer should ever feel like that after a purchase. I personally had 2 Cybertrucks with PCS and other major failures that made the vehicle completely inoperable. I still kept my truck because it's the best truck ever made and Tesla has fixed the reliability issues on newer models. Other automakers frequently extend warranty coverage retroactively through Warranty Extension Programs or Special Coverage when widespread issues come up. Tesla should do the same. This would show future customers that Tesla stands behind every single product they sell, no matter what. The Tesla I've come to know has always taken care of its customers. I truly hope you do right by early Cybertruck owners too. @cybertruck @Tesla @tesla_na