Hosting a Website on a Disposable Vape
Posted4 months agoActive4 months ago
bogdanthegeek.github.ioTechstory
excitedpositive
Debate
20/100
Novel HardwareEmbedded SystemsWeb Hosting
Key topics
Novel Hardware
Embedded Systems
Web Hosting
A developer hosted a website on a disposable vape, showcasing creative repurposing of hardware, with the community discussing its feasibility and previous iterations of the project.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
40m
Peak period
4
5-6h
Avg / period
1.9
Comment distribution15 data points
Loading chart...
Based on 15 loaded comments
Key moments
- 01Story posted
Sep 15, 2025 at 9:13 AM EDT
4 months ago
Step 01 - 02First comment
Sep 15, 2025 at 9:53 AM EDT
40m after posting
Step 02 - 03Peak activity
4 comments in 5-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 15, 2025 at 8:54 PM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45249287Type: storyLast synced: 11/22/2025, 11:47:55 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
Edit: we created a new copy of this submission at https://news.ycombinator.com/item?id=45252817 and moved the comments there.
I'm suddenly randomly curious about the backend (or frontend?) tools y'all folks use to do this sorta thing here on HN (and to manage the site in general). Is it web-based like the site itself, or CLI? GUI even? I presume the whole thing is mostly database-driven "under the hood" like a lotta these kinda sites, yeah?
As an ex-web designer, it's always fascinated me; the many different approaches people have come up with to managing various web properties, despite the core similarities underlying them all.
Edit: we created a new copy of this submission at https://news.ycombinator.com/item?id=45252817 and moved the comments there.
The site then went down due HN's traffic load. (I guess a vape-hosted website isn't "web scale").
The author shared the blog post, but we didn't see it. It was only much later (7 hours ago), that dmazin submitted the blog post as this submission. (No criticism, they were just being helpful and posting the blog post so the community could see it).
Out of fairness to the original submitter and author, we've created a new copy of their submission, set the blog post as the URL and moved the comments there. That way it gets its full chance at front page exposure, and the project creator gets the credit and karma, which they are entitled to, having submitted it first.