IdeaWell

Project ideas from Hacker News discussions.

Where did the old web go? We followed 657,607 links to find out

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

3 Core Themes from the Hacker News Discussion

1. Widespread link decay

"76.7% no longer returned a loading page. After removing repeated destinations, 78.7% of the 492,620 distinct crawlable URLs still did not load." – tdx

The analysis shows that the vast majority of URLs stored by the original 0.mk service are now dead or blocked, underscoring how quickly web content disappears.

2. Ultra‑short domain availability (e.g., .mk)

"The name of the .mk domain consists of a minimum of 1 (one) and a maximum of 63 characters." – neom

Discussion points out that certain top‑level domains, like .mk, permit registration of very short names, contrary to the assumption that single‑character domains are universally reserved.

3. Concerns about AI‑generated content and transparency

"The ENTIRE thing is AI generated. I'm not talking about the article. I'm talking about the entire \"product\"." – randomblock1

Community members highlight the irony and risk of an entire service being AI‑driven, questioning reliability, authenticity, and potential for abuse.

🚀 Project Ideas

Generating project ideas…

LinkVerse AI

Summary

  • AI‑driven service that continuously monitors shortened URLs, detects dead or blocked destinations, and automatically redirects users to archived snapshots or alternative sources.
  • Eliminates the frustration of “did not load” links while preserving the original sharing intent of community‑driven shorteners.

Details

Key Value
Target Audience Developers, forum moderators, and anyone who uses short‑link services (e.g., 0.mk).
Core Feature Real‑time link health API with automatic fallback to Wayback Machine, domain backups, or community‑curated mirrors.
Tech Stack Backend: Python/FastAPI; Crawler: Scrapy; Storage: S3 + Cloudflare R2; AI routing: LLM‑based destination inference; Frontend: React.
Difficulty Medium
Monetization Revenue-ready: SaaS subscription (Starter $10/mo, Pro $30/mo, Enterprise custom).

Notes

  • Directly addresses the 76‑78 % “did not load” rate highlighted by the 0.mk backup analysis.
  • HN commenters lamented link rot and the difficulty of preserving content; a tool that fixes it would be immediately valuable.
  • Potential for integration with existing short‑link platforms (e.g., API hooks) and for monetizing through premium analytics on broken‑link trends.

MkArchive

Summary

  • A decentralized, .mk‑domain‑based link shortener that stores the content hash of the destination URL on IPFS, ensuring longevity and eliminating reliance on a single host.
  • Users can create short links that survive domain changes, server downtime, or spam‑filter blocks.

Details

Key Value
Target Audience Tech‑savvy users, community archivists, and anyone wanting permanent short links (e.g., local forums, MUD communities).
Core Feature Generate short URLs that resolve to IPFS CIDs; optional “pin” service for paid users to keep content online.
Tech Stack Frontend: Vue.js; Backend: Node.js + Express; IPFS pinning: Pinata/Infura; Storage: Filecoin; Domain registration: .mk bulk purchase.
Difficulty High
Monetization Hobby

Notes

  • Leverages the observation that .mk domains are cheap and can be bulk‑registered (~$1‑$2 each).
  • Community members could host pinning nodes to fund storage, echoing the “no revenue” challenge but with a distributed model.
  • HN users interested in preserving “old web” artifacts would see a practical, permanence‑focused alternative to 0.mk.

WebMuseum.io

Summary

  • A curated, searchable archive of “old web” community artifacts (forum backups, MUD logs, image host snapshots) with a focus on preserving content that vanished after 2014.
  • Offers a clean UI, full‑text search, and an API for researchers and nostalgia‑driven users.

Details

Key Value
Target Audience Digital historians, retro‑gaming communities, archivists, and former forum participants.
Core Feature Bulk ingest of publicly available backups (e.g., .mk corpus), deduplication, metadata tagging, and public browsing interface.
Tech Stack Backend: Go (Gin); Database: PostgreSQL; Search: Elasticsearch; Frontend: Next.js; Hosting: Vercel + Wasm for compression.
Difficulty High
Monetization Revenue-ready: API tier $20/mo (10k requests), Premium $100/mo (unlimited + custom datasets).

Notes

  • Addresses the loss of 0.mk’s 657k links and the broader issue of missing community archives mentioned by HN commenters.
  • Provides tangible utility (searchable history) while respecting copyright through public‑domain or permission‑granted data.
  • Could attract sponsorship from nostalgia‑focused startups or academic projects interested in web heritage.

Read Later