Anonymous Blogging VPS - Host Without Revealing Your Identity

Anonymous blogging requires more than a pseudonym. If you host your blog on a service that has your credit card on file, a subpoena can link your credit card to your pseudonym. If your blog is on WordPress.com, Substack, or Medium, those US companies comply with legal data requests. True anonymous blogging requires infrastructure where your identity is genuinely unknown to the provider. The required conditions: the hosting provider has no real identity information for you (no name, no credit card, no phone number), payment is via untraceable cryptocurrency, your server management connections come through Tor (so your home IP is not logged), and your writing style and content do not reveal your identity (OPSEC). Anubiz Host satisfies the first three conditions. OPSEC (operational security in your writing) is your responsibility.

WordPress is the most practical blogging platform for anonymous use because it is self-hosted (you control all data) and has the largest ecosystem of themes and plugins. On your Anubiz Host Iceland VPS: ```bash apt update && apt install nginx mysql-server php8.1-fpm php8.1-mysql php8.1-gd php8.1-curl unzip -y # Secure MySQL mysql_secure_installation # Create database mysql -u root -p -e "CREATE DATABASE blogdb; CREATE USER 'bloguser'@'localhost' IDENTIFIED BY 'STRONG_PASSWORD'; GRANT ALL ON blogdb.* TO 'bloguser'@'localhost';" # Download WordPress wget https://wordpress.org/latest.tar.gz && tar xf latest.tar.gz cp -r wordpress /var/www/html/blog chown -R www-data:www-data /var/www/html/blog ``` Configure Nginx for your domain. Register a domain name anonymously (domain registrar accepting crypto with WHOIS privacy - ENS/Ethereum Name Service for .eth domains, or traditional registrar with WHOIS privacy and crypto payment). Set up TLS via Let's Encrypt. Your blog now runs on infrastructure with no identity data except the domain registration (use WHOIS privacy or anonymous registrar).

WordPress has a database and active code execution surface. A static site (just HTML files) has a smaller attack surface and simpler hosting. Hugo or Jekyll generate static HTML from markdown content. Static blog workflow: write content in markdown on your local Tails OS or air-gapped machine, generate static HTML using Hugo, upload to your VPS via SCP through Tor, Nginx serves the static files. No database, no PHP - much smaller attack surface. Hugo installation and site generation: ```bash # On your local machine (not the VPS): # Install Hugo, create site hugo new site myblog && cd myblog git clone https://github.com/adityatelange/hugo-PaperMod themes/PaperMod # Create content/posts/first-post.md # Build hugo # Upload to VPS (through SSH over Tor) rsync -av --delete public/ user@YOUR_VPS_IP:/var/www/html/blog/ ``` This workflow keeps your writing off the server until publish time, minimizing exposure.

Your blog domain should not be registered under your real name. Options from most to least anonymous: 1. ENS (.eth domain): Ethereum Name Service domains require only an Ethereum wallet (generate anonymously). No registrar KYC. No WHOIS. Content hosted via IPFS. Very technical to set up. 2. Crypto-accepting traditional registrar with WHOIS privacy: Namecheap, Porkbun, and others accept Bitcoin and include WHOIS privacy. Use a Monero-to-BTC swap to distance payment from identity. 3. Standard registrar with WHOIS privacy: Less anonymous (credit card links to identity) but WHOIS privacy protects from casual discovery. Motivated investigators can pierce WHOIS privacy via registrar subpoena. For most anonymous bloggers, option 2 provides sufficient protection. Option 3 protects you from harassment but not from determined government investigation.