A simple web we own
Calls to “own the web” by self-hosting simple personal sites on devices like Raspberry Pis resonate with many who are frustrated by corporate control, surveillance, and lock‑in on today’s internet. Commenters broadly support the ideal of user‑controlled publishing and federated or P2P alternatives, but argue that real obstacles lie in usability, discovery, moderation, security, and dependence on ISPs and backbone infrastructure. Several suggest the most impactful path is not just new hardware setups, but easier software, better standards (e.g. RSS‑like syndication), and economic or social incentives that can rival the attention and convenience offered by big platforms.
Identity, Moderation, and AI
- Some argue federated systems are bottlenecked by identity and moderation; without strong identity, spam and abuse are hard to manage.
- Others counter that AI agents are eroding identity as a reliable signal anyway; systems may have to judge content/actions instead of who posted.
- One concern: AI “launders” human ideas and hides the operator’s intent, making some users prefer original human expression over agent output.
- A radical view suggests accepting Sybil/bot swarms and designing systems where uniqueness has no value and only originality matters.
Hosting, Ownership, and Infrastructure
- Strong irony is noted: arguing for independence while hosting on a big corporate static hosting platform.
- Defenders say the key is owning content and domains; using corporate hosting as a replaceable convenience is acceptable if it’s portable.
- Critics reply that using a corporate subdomain weakens that claim, and many non‑giant alternatives exist.
- Home hosting raises issues: IP exposure, dynamic addresses, NAT, ISP hostility to servers, security of always-on devices, and the burden of fighting bots.
- Some propose tunnels/relays (overlay networks, reverse proxies) as a compromise, though others note that if you already pay for a VPS, simple hosting there may be easier.
Usability and Tooling
- Broad agreement that “simple to use” is the missing piece. Pi OS, Docker, and current homelab setups are seen as far beyond most people.
- Markdown itself is argued to be too technical; WYSIWYG editors, Word-style tooling, or folder-based CMSs are preferred.
- Several projects aim to simplify self-hosting (personal app platforms, git-backed CMSs, mobile apps that publish to static hosts), but all still have rough onboarding.
- Some see AI as a potential UX layer: users describe what they want and get custom apps/sites, though others doubt most people can even articulate requirements.
Discovery, Attention, and Incentives
- Many say publishing isn’t the real bottleneck; discovery, attention, and monetization are.
- People post to big platforms because that’s where friends and audiences already are, and because they get instant feedback (likes, comments).
- Personal sites often feel like “throwing work in the trash” without a discovery and interaction layer.
- Suggestions include reviving RSS with better directories, or building decentralized search, but scalability and spam/SEO-like gaming are concerns.
Structural Limits and Alternative Visions
- Several comments stress that ownership hits a wall at ISPs and backbone cables; control of physical infrastructure and state censorship remain fundamental constraints.
- Co-ops and new protocols (P2P networks, alternative naming/identity systems, mesh networks, overlay “new internets”) are seen as promising but politically and economically hard to scale.
- Some see the article as inspiring but technically and socially naive: running small static pages is easy; replacing today’s app- and video-centric, attention-driven web is the hard unsolved part.