25 Years of LinkaGoGo: Servers Under Desks, Domain Disasters, and a Billion Bookmarks
LinkaGoGo celebrates its 25th anniversary this month, having evolved significantly since its launch in 2001. Originally started from a home server, it faced numerous challenges including domain issues and infrastructure upgrades. Today, it boasts over four million users and a billion bookmarks, demonstrating its resilience and adaptability over the years.
- ▪LinkaGoGo was launched in May 2001 from a home server connected to a residential cable line.
- ▪In 2007, the domain registrar RegisterFly collapsed, temporarily suspending LinkaGoGo's domain but allowing the site to continue operating under a different domain.
- ▪By 2014, LinkaGoGo moved to DigitalOcean due to flood risks and noise complaints from running servers in a basement.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/linkagogo/25-years-of-linkagogo-servers-under-desks-domain-disasters-and-a-billion-bookmarks-d4 |
| Publication time | Sun, 17 May 2026 01:23:33 +0000 |
| Retrieval time | 2026-05-17T01:40:19.096Z |
| Last seen | 2026-05-17T01:40:19.096Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | pZ6g3VJ0pWGP |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3894940) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Henry van den Broek for LinkaGoGo Posted on May 17 25 Years of LinkaGoGo: Servers Under Desks, Domain Disasters, and a Billion Bookmarks #anniversary #history #linkagogo #bookmarking LinkaGoGo turns 25 this month. The web has changed beyond recognition since 2001, but the problem it solves hasn't: you find something worth keeping, and you want it to still be there when you need it. Here's the full story of how it survived — floods, ransom registrars, noise complaints, and all.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).