November 29, 2025
Tape vs. Boom
An Update on the Farphone's Battery
Old phone turned web server sparks battery panic and punchlines
TLDR: A DIYer removed the battery from an old phone powering a website after commenters warned about fire risk. The crowd split between alarmed anecdotes of swollen laptops and veteran tinkerers insisting 24/7 plugged-in gear is fine, turning a tiny tweak into a big safety debate.
An old Fairphone-turned-web server just got a spicy safety makeover: the builder yanked the battery and taped the charging cable after folks on lobste.rs and Hacker News warned about lithium batteries living on the charger forever. Cue the comment war. The skeptics fired first: “For how long?” asked conradev, basically predicting this cable-powered miracle is on borrowed time. Telaneo waved the caution flag, saying some older devices assume a fresh battery and can behave badly when it’s worn out. Then came the horror stories: lisper dropped a chilling tale of MacBook batteries swelling enough to warp the case—twice. Meanwhile, the chill crew rolled in: joecool1029 claimed years of running phones plugged in 24/7 as Wi‑Fi hotspots (an “AP,” a tiny router) with no drama, joking that compiling Gentoo—nerd-speak for heavy software building—roasts laptop batteries more than any charger ever could. One commenter even asked if different battery chemistry was used, which had everyone side-eyeing the idea of a homebrew battery swap. French blogger Korben amplified the story, but the real show is the thread: fear vs. flex, doom vs. duct tape, with the DIY’er thanking the crowd for preventing a “server explosion.”
Key Points
- •The website is hosted on an old Fairphone 2 smartphone.
- •Community feedback on Lobste.rs and Hacker News highlighted fire risks from keeping lithium batteries plugged in continuously.
- •The author removed the Fairphone 2’s battery and secured the micro‑USB cable to supply power.
- •The phone booted in about 40 seconds without the battery, and the web server resumed operation.
- •The project is credited to Louis Merlin and shared under a CC BY-NC-SA 4.0 license.