This blog is running on a recycled Google Pixel 5 (2024)

Current setup and performance

  • Commenters confirm the blog is still served from the Pixel 5, on a residential ISP IP, fronted by nginx on another machine.
  • Despite HN front‑page traffic and no CDN or reverse‑proxy caching, readers report the site is fast and stable.
  • Others note they’ve similarly self‑hosted on old laptops or netbooks for years without issues.

Networking: Ethernet vs Wi‑Fi, and ISP rules

  • The author chose USB‑Ethernet for bandwidth consistency because their Wi‑Fi is flaky; some speculate Wi‑Fi power‑saving and higher latency would hurt tail performance.
  • There’s debate over Android USB‑Ethernet support: some claim Pixel 5 doesn’t support it, others say modern Android phones generally do.
  • Several people note ISP ToS (e.g. prohibiting servers on residential lines), but say enforcement usually only happens with heavy upload usage.
  • DNS is handled via residential IP + dynamic DNS or scripts updating DNS on IP changes.

Software stack, Android behavior, and security

  • Hugo is run via hugo serve inside Termux; nginx on another box terminates TLS and reverse‑proxies to the phone.
  • Termux keeps processes alive via a persistent notification and adjusted phantom‑process limits.
  • Some praise Termux; others warn packages are brittle and prefer running a full Linux distro in an emulated/contained environment for reliability.
  • Security concerns center on Android EOL (Pixel 5 is out of support). Mitigations suggested: minimal stack, small attack surface, or alternative OSes like postmarketOS on supported devices.

Power efficiency, “off‑grid”, and environment

  • Many highlight phones as ultra‑low‑power ARM servers with built‑in “UPS,” often more efficient than x86 boxes idling at tens of watts.
  • There’s disagreement on impact: some estimate large kWh and CO₂ savings; others compute actual dollar and emissions savings and call them modest.
  • “Off‑grid” terminology is debated: some find it funny for an internet‑connected device; others defend “electrical‑grid‑off” as meaningful, especially with solar + battery setups.

Battery safety and longevity

  • Multiple commenters worry about “spicy pillow” (swollen Li‑ion) risks when a phone runs 24/7.
  • Suggested mitigations: dummy batteries or battery‑less powering, smart plugs or timers, limiting charge to ~80%, periodic charge cycles, fire‑resistant enclosures, avoiding heat and full‑time 100% charge.

Reuse vs recycle and broader reuse ideas

  • Long subthread debates whether “recycled” vs “reused/repurposed” is the correct term; consensus leans that reuse has higher environmental value than material recycling.
  • Many advocate using old phones and tablets as micro‑servers, dashboards, photo frames, test devices, Elixir clusters, or “serverized” boards, lamenting OEM locks that hinder such reuse.