$ ls -la ~/blog

AT Protocol MCP Server

A comprehensive Model Context Protocol server that provides LLMs with direct access to the AT Protocol ecosystem, enabling seamless interaction with Bluesky and other AT Protocol-based social networks.

Live Demo

The convergence of artificial intelligence and next-generation social protocols represents a transformative opportunity in distributed systems architecture. Today, I’m introducing the AT Protocol MCP Server—a comprehensive Model Context Protocol implementation that enables LLMs to interact directly with the AT Protocol ecosystem, including Bluesky and other decentralized social networks built on this innovative protocol.

This project addresses a critical infrastructure gap: providing AI systems with standardized, secure access to the emerging landscape of decentralized social networks that prioritize user sovereignty, data portability, and algorithmic choice. Unlike traditional social platforms, AT Protocol’s architecture enables fundamentally different interaction patterns that align naturally with AI-powered analysis and automation.

This analysis builds upon Dan Abramov’s excellent explanation of AT Protocol in “Open Social”, examining the deeper technical architecture trade-offs and governance implications of decentralized social media infrastructure.

The intersection of artificial intelligence and systems security has reached a critical inflection point. As AI agents become increasingly capable of executing external tools and accessing system resources, the traditional security models that govern software execution are proving inadequate. Microsoft’s Wassette emerges as a groundbreaking solution that leverages WebAssembly’s sandboxing capabilities to create a secure, scalable runtime for AI tool execution through the Model Context Protocol (MCP).

Wassette represents a paradigm shift from the current landscape of MCP server deployment, where tools typically run with unrestricted system access, to a capability-based security model that provides fine-grained control over resource access. This architectural evolution addresses fundamental security concerns while maintaining the flexibility and extensibility that make MCP valuable for AI system integration.

ActivityPub MCP Server

A comprehensive Model Context Protocol server that enables LLMs to explore and interact with the Fediverse through standardized ActivityPub integration.

Live Demo

The intersection of artificial intelligence and decentralized social networks represents a fascinating frontier in modern software development. Today, I’m excited to introduce the ActivityPub MCP Server—a comprehensive Model Context Protocol implementation that enables LLMs like Claude to explore and interact with the Fediverse through standardized ActivityPub integration.

This project addresses a critical gap in AI tooling: the ability to discover, analyze, and interact with the rich ecosystem of decentralized social networks that comprise the Fediverse, including Mastodon, Pleroma, Misskey, and countless other ActivityPub-compatible platforms.

Electromagnetic Spectrum Explorer

Interactive web application for exploring the electromagnetic spectrum from radio waves to gamma rays with real-time visualization and comprehensive physics calculations.

Live Demo

The intersection of physics education and interactive web development presents unique challenges that extend far beyond traditional application design. Building an electromagnetic spectrum explorer requires not only technical proficiency in modern web frameworks but also deep understanding of fundamental physics principles, scientific data visualization patterns, and educational interface design. This project demonstrates how contemporary web technologies can transform abstract scientific concepts into tangible, interactive learning experiences.

OpenZIM MCP Server

Offline knowledge base access for AI models. A secure, high-performance MCP server that enables AI models to access and search ZIM format knowledge bases offline.

Live Demo

The dependency on persistent internet connectivity represents a fundamental architectural limitation in contemporary AI systems, creating single points of failure that compromise system reliability in distributed or resource-constrained environments. This realization led to the development of offline knowledge access patterns that enable AI assistants to maintain functionality across diverse operational contexts, from edge computing scenarios to air-gapped security environments.

Gopher MCP Server

A modern Model Context Protocol server for Gopher and Gemini protocols, enabling AI assistants to browse these classic internet protocols safely and efficiently.

Live Demo

The integration of legacy protocols with modern AI infrastructure reveals fundamental insights about system design philosophy and the evolution of network architectures. The gopher-mcp implementation demonstrates how protocols designed with minimalist principles can provide superior performance characteristics and operational simplicity compared to their contemporary counterparts—lessons that remain highly relevant for modern distributed systems engineering.

Having architected distributed systems across enterprise environments for over a decade, the Model Context Protocol represents a paradigm shift that addresses fundamental challenges in AI tooling infrastructure. Through the development of production-grade MCP servers including gopher-mcp and openzim-mcp, I’ve identified architectural patterns and implementation strategies that demonstrate MCP’s potential to revolutionize how AI systems interact with external resources.

Update (June 2025): I’ve split this comprehensive guide into two focused articles for better readability:

• Gopher MCP Server: Bringing 1991’s Internet to Modern AI - Focuses on the Gopher protocol, its history, and practical applications
• OpenZIM MCP Server: Offline Knowledge for AI Assistants - Covers offline Wikipedia access and ZIM format optimization

Having contributed to and maintained open source projects across enterprise and community environments for over a decade, I’ve observed that successful open source participation requires understanding both technical contribution patterns and community dynamics. The evolution from initial contributor to project maintainer reveals systematic approaches to building sustainable software communities and establishing technical leadership within distributed development environments.

Having architected static site solutions across enterprise environments for over a decade, I’ve witnessed the evolution of static site generators from simple Jekyll implementations to today’s sophisticated build systems. Zola represents a paradigm shift in this space—a tool that embodies the principles of systems engineering while maintaining the elegance that production environments demand. This analysis examines why Zola has emerged as the definitive choice for performance-critical static site generation.

The evolution of web development from static document delivery to complex application platforms represents one of the most significant architectural transformations in software engineering. Modern web applications serve as the foundation for critical infrastructure spanning financial systems, healthcare platforms, and enterprise software—requiring engineering practices that prioritize reliability, security, and performance at scale. The principles outlined here reflect lessons learned from building production systems that serve millions of users across diverse operational environments.

This post demonstrates the comprehensive image integration system implemented for this Zola-based blog, showcasing advanced features like responsive image delivery and performance optimization.

Welcome to a technical discourse platform dedicated to exploring advanced software engineering concepts, architectural patterns, and the systematic analysis of emerging technologies. This space serves as a repository for insights derived from years of production system development and the continuous pursuit of engineering excellence across diverse technical domains.

Every web developer has encountered the frustration of inconsistent metadata discovery across different websites and services. Where do you find a site’s security contact information? How do you discover OAuth endpoints? What about password change URLs for password managers? The web’s decentralized nature, while powerful, has historically led to fragmented approaches for exposing essential service metadata.

The Well-known URI standard, formalized in RFC 8615 by the Internet Engineering Task Force (IETF), provides an elegant solution to this fundamental problem. By establishing a standardized location for service metadata at /.well-known/, this specification enables consistent, predictable discovery of critical information across the entire web ecosystem.