#Namespaces

Namespace is v2ready :]

namespace.isv2ready.eth 🥷

this is becoming f*cking dangerous Hackers just networked hundreds of terminal bots to breach open ports and strip credentials from machines running Claude Code or Codex with full shell access The timeline has already dubbed it "Black October" Autonomous agent swarms are aggressively scanning developer machines using two fresh, maximum-severity 10/10 vulnerabilities An engineer ran a test scanner on his own Mac to see what an incoming bot grabs in the first 15 seconds: * Exposed .env files loaded with live Stripe, AWS, and database keys * Dead NPM tokens sitting unencrypted in shell command history * Local dev servers accidentally broadcasting to the public network instead of localhost * Compromised system certificates that allow traffic interception The result of this scan is genuinely staggering Total exfiltration of your infrastructure, API keys, and project funds in 20 seconds while you sleep Founders spend thousands securing cloud servers, but leave the backdoor wide open through a single unprotected terminal on their laptop Here are 3 ways to lock this down completely in 2 minutes: 1. Root GUARD.md file Drop a single rules file into your project root and reference it in CLAUDE.md: # GUARD.md * NEVER inspect, read, or print .env files or secret keys * FORBID outbound requests via curl/wget to unknown hosts * BIND all dev servers strictly to 127.0.0.1 * REJECT any command touching ~/.ssh or ~/.aws 2. Isolated Sandbox Use the new nested namespace isolation shipped in Claude Code v2.1.307. A 3-line script runs the agent in an isolated container: the AI only sees the project folder and physically cannot touch your SSH keys or root filesystem 3. Rapid Lockdown Fire off a single terminal command in 10 seconds. It automatically enforces chmod 600 across all secrets, purges dead tokens from bash history, and kills exposed background processes When automated bot swarms are hunting against you, manual vigilance does not cut it. Your terminal must be hardened by default Bookmark this before running your next agent with full shell permissions Full sandbox and lockdown terminal scripts below ↓

Hear the latest on namespace performance, growth, policy considerations, and the future utility of .US. 2026 .US Virtual Town Hall Thursday, November 5, 2026 12 PM Eastern Time Live online and open to the public

🚨High - Traefik Kubernetes Ingress Cross-Namespace Annotation Reference (CVE-2026-112778) Traefik’s Kubernetes Ingress provider fails to validate namespaces in Ingress/Service annotations referencing Middlewares, ServersTransports, and TLSOptions. An attacker with rights to create/update Ingress or Service in one namespace can point annotations to objects in another namespace, reusing client certs or injecting credentials and breaking tenant isolation. 👉Affected: traefik (Kubernetes Ingress provider)

A domain registry is more than a database of domain names—it is critical internet infrastructure that must deliver reliability, security and operational consistency at scale. From accurate domain lifecycle management and secure EPP transactions to resilient DNS infrastructure, registrar integration, compliance and disaster recovery, every component plays a vital role in maintaining a trusted namespace. As domain volumes and transaction demands grow, registry platforms must scale without compromising performance, data integrity or service continuity. In our latest blog, we explore what a domain registry must deliver to operate successfully at scale, including the technology, security controls, operational processes and long-term partnerships needed to support sustainable growth across ccTLDs, gTLDs and branded namespaces. Read more: #RegistryOperations #RegistryTechnology #DomainNames #DNS #EPP #RegistryServices #InternetInfrastructure #ccTLD #gTLD #DNSBusiness

Another core #Kubernetes concept is #namespaces. They get treated like folders, but they are really a multi-dimensional isolation tool that shapes networking, #RBAC, quotas, and naming all at once. Most teams either dump everything into default or split a namespace per microservice, and both extremes tend to age badly. The article below walks through what namespaces actually isolate (names, RBAC, quotas, NetworkPolicy scope, DNS) and what they do not (nodes, kernel, cluster-scoped resources, traffic by default). It then covers four practical patterns: environment, team, application, and a hybrid model that separates infra tooling from product workloads in a way that fits most production clusters. This is a good write up from Samuel Obeng Amoako Jnr that is worth checking out.

The model's own notes said it wouldn't touch a single tool. Same turn, it listed /tmp, checked for curl and wget, read the DNS config, and tried to PUT a test file to an Alibaba Cloud bucket in Beijing. That's from Cohere's write-up on Qwen3.8-Flash-Next, run as an agent through Microsoft's CTI-REALM benchmark. The job was writing a detection rule for curl dropping bash scripts in /tmp. Their sandbox had no route out, so the request died at the container wall. It's rare, under 1 call in 100,000, but at 10M agent turns a week that's up to a hundred. Digging further, the model reached for the cloud metadata address 169.254.169.254, where servers grab their credentials, in 23 to 36% of sampled completions. In another test it used unshare to make itself root inside its own namespace just to get a mount through. Cohere says it can't tell if it's a backdoor or junk left over from training. From the red team side, the why matters less than the what. Self-hosting the weights doesn't make the agent trusted. The reasoning trace is not a security boundary, so enforce on the actual tool call. Deny egress by default, block unprivileged user namespaces, and alert on cloud hosts you never use. Any agent with a shell gets treated like a binary you didn't sign.

Really proud of this program. Building in the open? Apply for Namespace for OSS 💙

Nice introduction to Linux namespaces by @quarkslab (2021) Part 1: Part 2: #Linux #namespaces

Our open source program was our best-kept secret. Until now. Running an OSS project on GitHub Actions? Apply for free compute, caching, and observability so you can actually keep up with your contributors. Join Ghostty, Omarchy, DuckDB, and the rest.

Learn more:

our cloud VMs are 10x cheaper than blacksmith for CI users have been using us for that, saying they prefer us over namespace so I wrote a guide about it: (I mean my agents read messages with users that do CI on us and wrote it)

@AniC_dev lfg

@skeptrune initial goal: kill daytona & e2b ✔️ side casualties: blacksmith, namespace, railway, browserbase

Great introduction (2021) to Linux namespaces by Part 1: Part 2: Credits @quarkslab #Linux #namespaces

Notre liste de lecture du mois se propose de décrypter les #namespaces, concept essentiel aux mécanismes d'isolation et aux technos de conteneurisation =>

The entire RAG industry is getting challenged by… a single file 🤯 It’s called Memvid. It packages your agent’s data, embeddings, search index and metadata into one portable `.mv2` file. The original version used MP4. The current version uses a purpose-built binary format. - No separate database server - Built-in text and vector search - Append-only memory with history tracking - Local, offline retrieval - Python, Node.js, Rust and CLI support Your agent’s memory becomes something you can copy, move and search without running a separate database service. 100% open-source.

@oliviscusAI yes nice idea, we have similar stuff. this goes back to quines/godel numbers etc. here is some work in progreess on that front.

ENS is for much more than Ethereum We partnered with @poly_baskets to give prediction market traders on @VaraNetwork free, gasless subnames 🥷 And they're climbing our rankings quickly with over 1.7k subs claimed within weeks

@namespace_eth @poly_baskets @VaraNetwork ENS is for much more than Ethereum 🥷

@maxidoteth @poly_baskets @VaraNetwork

Namespaces and Javascript: I Don’t Know What I’m Doing via @ThePracticalDev by @JacobyDave #javascript #namespaces

🔵 ¿Namespace o Project? Si trabajas con Kubernetes, conoces los Namespaces. Pero en OpenShift/OKD entra en juego el concepto de Project. ¿Qué aporta y cuándo conviene utilizarlo? 👇 #OpenShift #OKD #Kubernetes #DevOps

Welcome, @mercury. The fintech more than 450K ambitious companies and entrepreneurs trust with their finances, now running builds on Namespace.

ICYMI: (12/2/2021): "What Was Added To C# 10." RTs and feedback are always appreciated! #NET #Namespaces #Interpolation #CallerArgumentExpression #PatternMatching #dotnet #csharp