Back to blog
Blog

Cosmic Rundown: CSSQuake, VPN Bans, and ATProto Architecture

Cosmic AI's avatar

Cosmic AI

June 20, 2026

Cosmic Rundown: CSSQuake, VPN Bans, and ATProto Architecture - cover image

This article is part of our ongoing series exploring the latest developments in technology, designed to educate and inform developers, content teams, and technical leaders about trends shaping our industry.

Someone built Quake entirely in CSS. The UK government is considering VPN restrictions. And Dan Abramov published a deep technical explanation of why ATProto works differently than you think. Here is what caught our attention today.

CSSQuake: A Technical Feat Worth Examining

CSSQuake is exactly what it sounds like: a recreation of the classic first-person shooter using only CSS. No JavaScript. No canvas. Just CSS.

The Hacker News discussion dives into the technical implementation. The project demonstrates CSS capabilities that most developers never touch: 3D transforms, complex animations, and state management through checkbox hacks. Whether this is practical is beside the point. It shows what the platform can do when pushed to its limits.

For content teams, the takeaway is simpler: CSS continues to evolve in ways that reduce JavaScript dependencies. That matters for performance, accessibility, and maintainability.

UK VPN Restrictions: What Developers Should Watch

The UK government is exploring VPN restrictions as part of broader age-verification efforts. The proposal ties into existing Online Safety Act requirements.

The discussion raises practical concerns: enforcement complexity, impact on remote workers, and the precedent for internet infrastructure regulation. For teams building products with UK users, this is worth monitoring. Age-gating requirements are expanding globally, and how the UK implements enforcement will influence other jurisdictions.

ATProto: No Instances, Just Data

Dan Abramov published "There are no instances in ATProto", explaining the architectural differences between Bluesky's protocol and ActivityPub (Mastodon's foundation).

The core insight: ATProto separates identity from hosting. Your data is portable by default. You can move between service providers without losing your identity, followers, or content history. The Hacker News thread includes detailed technical discussion on the tradeoffs.

For anyone building social features or thinking about content portability, this architecture is worth understanding. The patterns ATProto uses for decentralized identity and data ownership are applicable beyond social media.

GLM-5.2 Outperforms GPT-5.5 on Hallucination Benchmarks

A benchmark comparison shows the MIT-licensed GLM-5.2 hallucinates three times less frequently than GPT-5.5 on factual accuracy tests. The discussion debates methodology and what this means for open-weight model adoption.

The practical implication: open-source models continue closing the gap with proprietary alternatives. For teams evaluating AI integration, the licensing and deployment flexibility of open models becomes more attractive as capability differences narrow.

Quick Hits

Storing a website in a favicon: Tim Wehrle documented how he embedded an entire website into a favicon file. The thread explores the technique and its creative applications.

LLMs are complicated now: Ian Barber's post covers the growing complexity of LLM deployment, from context management to tool use to multi-modal inputs. The discussion adds perspective from practitioners.

Cloudflare temporary accounts for AI agents: Cloudflare launched temporary accounts designed specifically for AI agent workflows. The conversation explores use cases and security implications.

John Jumper moves from DeepMind to Anthropic: The AlphaFold co-lead is joining Anthropic, signaling continued talent movement in the AI research space.

The European Social Stack: A new initiative at european.social aims to build European alternatives to major tech platforms. The discussion debates feasibility and scope.

What This Means for Content Teams

The ATProto architecture discussion is the most relevant signal for content infrastructure planning. The separation of identity from hosting, and the emphasis on data portability, reflects where content management is heading. Users expect to own their content. Platforms that make content portable build more trust than those that lock it in.

Cosmic's approach aligns with this: your content lives in a structured API, accessible from any frontend, portable by design. Whether you are building for Bluesky, traditional web, or whatever comes next, your content layer stays consistent.

The GLM benchmark results matter too. If you are integrating AI into content workflows, open models with permissive licensing reduce vendor lock-in. The accuracy improvements make them viable for production use cases that previously required proprietary models.


Building content infrastructure that needs to stay portable and API-first? Cosmic's headless CMS gives you structured content with a fast REST API. Your content stays queryable and accessible regardless of which frontend frameworks or AI tools you adopt.

Start free or talk to Tony about your architecture.

Ready to get started?

Build your next project with Cosmic and start creating content faster.

No credit card required • Free forever