Apple is fighting for TSMC capacity as Nvidia takes center stage

Photos capture the breathtaking scale of China's wind and solar buildout

25 Years of Wikipedia

Countless voiceless people sit alone every day and have no one to talk to, people of all ages, who don&#x27;t feel that they can join any local groups. So they sit on social media all day when they&#x27;re not at work or school. How can we solve this?

Ask HN: How can we solve the loneliness epidemic?

<a href="https:&#x2F;&#x2F;github.com&#x2F;internetarchive&#x2F;heritrix3" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;internetarchive&#x2F;heritrix3</a>

Inside The Internet Archive's Infrastructure

Claude is good at assembling blocks, but still falls apart at creating them

CVEs affecting the Svelte ecosystem

Design and Implementation of Sprites

First impressions of Claude Cowork

Found: Medieval Cargo Ship – Largest Vessel of Its Kind Ever

hi hn,i built openwork, an open-source, local-first system inspired by claude cowork.it’s a native desktop app that runs on top of opencode (opencode.ai).
it’s basically an alternative gui for opencode, which (at least until now) has been more focused on technical folks.the original seed for openwork was simple: i have a home server, and i wanted my wife and i to be able to run privileged workflows. things like controlling home assistant, or deploying custom web apps (e.g. our customs recipe app recipes.benjaminshafii.com), legal torrents, without living in a terminal.our initial setup was running the opencode web server directly and sharing credentials to it. that worked, but i found the web ui unreliable and very unfriendly for non-technical users.the goal with openwork is to bring the kind of workflows i’m used to running in the cli into a gui, while keeping a very deep extensibility mindset. ideally this grows into something closer to an obsidian-style ecosystem, but for agentic work.some core principles i had in mind:- open by design: no black boxes, no hosted lock-in. everything runs locally or on your own servers. (models don’t run locally yet, but both opencode and openwork are built with that future in mind.)
- hyper extensible: skills are installable modules via a skill&#x2F;package manager, using the native opencode plugin ecosystem.
- non-technical by default: plans, progress, permissions, and artifacts are surfaced in the ui, not buried in logs.you can already try it:
- there’s an unsigned dmg
- or you can clone the repo, install deps, and if you already have opencode running it should work right awayit’s very alpha, lots of rough edges. i’d love feedback on what feels the roughest or most confusing.happy to answer questions.

Show HN: OpenWork – an open-source alternative to Claude Cowork

Hi HN,My team and I are building Tabstack to handle the &quot;web layer&quot; for AI agents. Launch Post: <a href="https:&#x2F;&#x2F;tabstack.ai&#x2F;blog&#x2F;intro-browsing-infrastructure-ai-agents" rel="nofollow">https:&#x2F;&#x2F;tabstack.ai&#x2F;blog&#x2F;intro-browsing-infrastructure-ai-ag...</a>Maintaining a complex infrastructure stack for web browsing is one of the biggest bottlenecks in building reliable agents. You start with a simple fetch, but quickly end up managing a complex stack of proxies, handling client-side hydration, and debugging brittle selectors. and writing custom parsing logic for every site.Tabstack is an API that abstracts that infrastructure. You send a URL and an intent; we handle the rendering and return clean, structured data for the LLM.How it works under the hood:- Escalation Logic: We don&#x27;t spin up a full browser instance for every request (which is slow and expensive). We attempt lightweight fetches first, escalating to full browser automation only when the site requires JS execution&#x2F;hydration.- Token Optimization: Raw HTML is noisy and burns context window tokens. We process the DOM to strip non-content elements and return a markdown-friendly structure that is optimized for LLM consumption.- Infrastructure Stability: Scaling headless browsers is notoriously hard (zombie processes, memory leaks, crashing instances). We manage the fleet lifecycle and orchestration so you can run thousands of concurrent requests without maintaining the underlying grid.On Ethics: Since we are backed by Mozilla, we are strict about how this interacts with the open web.- We respect robots.txt rules.- We identify our User Agent.- We do not use requests&#x2F;content to train models.- Data is ephemeral and discarded after the task.The linked post goes into more detail on the infrastructure and why we think browsing needs to be a distinct layer in the AI stack.This is obviously a very new space and we&#x27;re all learning together. There are plenty of known unknowns (and likely even more unknown unknowns) when it comes to agentic browsing, so we’d genuinely appreciate your feedback, questions, and tips.Happy to answer questions about the stack, our architecture, or the challenges of building browser infrastructure.

HN

Apple is fighting for TSMC capacity as Nvidia takes center stage

Photos capture the breathtaking scale of China's wind and solar buildout

25 Years of Wikipedia

Ask HN: How can we solve the loneliness epidemic?

Inside The Internet Archive's Infrastructure

Claude is good at assembling blocks, but still falls apart at creating them

CVEs affecting the Svelte ecosystem

Design and Implementation of Sprites

First impressions of Claude Cowork

Found: Medieval Cargo Ship – Largest Vessel of Its Kind Ever

Show HN: OpenWork – an open-source alternative to Claude Cowork

Show HN: Tabstack – Browser infrastructure for AI agents (by Mozilla)

JuiceFS is a distributed POSIX file system built on top of Redis and S3

Claude Cowork runs Linux VM via Apple virtualization framework

Supply Chain Vuln Compromised Core AWS GitHub Repos & Threatened the AWS Console

Linux boxes via SSH: suspended when disconected

Pocket TTS: A high quality TTS that gives your CPU a voice

Go-legacy-winxp: Compile Golang 1.24 code for Windows XP

Data is the only moat

Why Senior Engineers Let Bad Projects Fail