Be a property owner and not a renter on the internet
Advocates of a more “owned” presence on the web argue that relying solely on platforms like Facebook, X, or YouTube leaves creators vulnerable to bans, algorithm changes, and loss of their audience, and instead promote buying a domain, hosting a personal site, and using email lists as portable, durable assets. Others counter that complete independence is illusory—most people still “rent” infrastructure from clouds, ISPs, and registrars—and that self‑hosting can be complex, hard to secure, and constrained by search rankings and spam filters. A parallel concern is that any public content, even on self‑hosted sites, is now routinely scraped for AI training, raising questions about consent, copyright, and whether sharing knowledge openly still feels worthwhile.
Scope of “Ownership” vs. Renting
- Many argue true “ownership” online is impossible: you rent domains, IP space, cloud services, and even ASNs from registries.
- Others distinguish between replaceable, commoditized services (VPS, CDN, registrar) and closed platforms (social networks) where you can’t migrate your audience.
- Some mock the “own, don’t rent” slogan as unrealistic unless you run your own hardware, ASN, fiber, even nation-state–level infrastructure.
Self‑Hosting, Homelabs, and Security
- Several run personal servers (often small PCs with Proxmox, VPNs, nftables, OPNSense, etc.) for blogs, DNS, mail.
- Others warn this “paints a target” on home networks; many users misconfigure port forwarding and expose everything.
- Recommendations include VPN-based access (e.g., WireGuard/Tailscale) and solid firewall fundamentals; self-hosting is seen as viable only for those who really know what they’re doing.
Cloud, Portability, and Lock‑in
- Common middle-ground view: using cloud is fine if you avoid lock-in and keep services portable (e.g., simple VPS, swappable CDN).
- Domain + portable stack is seen as the key: you can move hosts by restoring backups and updating DNS, unlike social accounts that can vanish without recourse.
- Some criticize recommendations to use large providers (AWS, Azure, Cloudflare) as undermining privacy and independence.
Email, Mailing Lists, and Deliverability
- Many endorse newsletters/mailing lists as more “ownable” than social followers.
- Concerns: big providers (e.g., Gmail) control spam filtering and can silently nuke deliverability.
- Rolling your own mail server is widely viewed as fragile; established newsletter services are reported to work better.
AI Training, Copyright, and Sharing
- Large subthread debates whether open content being used to train LLMs is acceptable or exploitative.
- One side: once content is public, its use for training is akin to human learning; trying to control downstream use is selfish or unrealistic.
- Opposing side: AI firms monetize others’ work at scale without consent or attribution, undermining creators’ livelihoods and incentives to share.
- Some discuss defensive techniques (e.g., adversarial image poisoning) and express a growing desire to share less or go private.
Adoption, Culture, and Discoverability
- Many enjoy running personal sites “just for fun” or as learning logs, but note most people prefer big social platforms.
- Discoverability is heavily dependent on search engines and ranking algorithms; several report high competition and slow/limited SEO gains.
- POSSE/IndieWeb ideas and cooperatives are mentioned as ways to blend independence with reach.