Types of Stopping

Not all stopped projects are "abandoned". Based on four examples from web archaeology, here are different ways projects stop.

1. Interest Shift

Pattern:

• Project freezes, but author continues activity elsewhere
• No drama, no announcements, just change of focus
• Old project remains accessible but undeveloped

Example: Logic Museum (2006-2017)

Edward Buckner spent 2006-2011 translating medieval philosophical texts (Aquinas, Ockham, Buridan) and publishing parallel Latin-English versions. In 2011 the site froze at its peak, but Buckner continued philosophical work for 6 more years — just in a different form, in blog discussions rather than meticulous translations. In 2017 everything stopped.

He didn't abandon philosophy. He shifted from solitary archival work to live intellectual debates. Six years later, that stopped too.

2. Fan Project Burnout

Pattern:

• Growing list of uncompleted tasks
• Periodic promises to rebuild everything
• Dependence on community motivation
• Gradual slowdown → silence
• Author admits frustration

Example: BASE NECTARIS (2002-2012)

10+ years documenting the Nectaris game series and TurboGrafx-16 console. "20,000 missing/incomplete pages." "I don't know why I do this. It gets too frustrating too quickly." Last update October 2012, "Goals for 2014" never realized.

Classic burnout: massive scope, endless todo-list, exhaustion. Author disappeared without announcement. The work remains: hundreds of scans, complete magazine archives, working database.

3. Conscious Completion

Pattern:

• Public announcement of ending
• Graceful exit: one final full season
• Project achieved its goal
• Gratitude to community
• Sale/archiving instead of abandonment

Example: Komar.org Christmas Lights (1999-2014)

15 years of web-controllable holiday decorations. Millions of visitors, $83,000 raised for charity. December 2014: "It's been a fun run... Alek is hanging up his Santa Hat!" Sold all equipment "to prevent me from being tempted to set it up again."

Rare case: project didn't freeze or burn out, it completed with dignity. Author knew when to stop.

4. Phase Completion

Pattern:

• Project reaches natural completion point
• Documentation/goal fulfilled
• No drama, no announcements
• Result remains useful for decades

Example: This Old SGI (1996-1997)

Technical documentation for old SGI 4D computers. Version 2.0 (July 1997) added the third machine family — significant expansion. Then 30 years of silence.

Perhaps the author revived his machine and moved on to using it. Or simply considered the documentation complete. Result: 406 KB of technical text, still useful to retro-computing enthusiasts today.

Observations

Only one of four findings is true burnout. The other three are different forms of "successful" stopping.

Shift vs completion:

• Shift: author moves to different area, old project freezes
• Completion: author considers goal achieved

Announcement vs silence:

• Conscious completion usually announced (Komar.org)
• Shift and phase completion often happen quietly (Logic Museum, This Old SGI)
• Burnout almost always silent (BASE NECTARIS)

Duration:

• All four projects: long-term (6-15+ years)
• Short projects stop differently?

Value after stopping:

• All four sites remained accessible and useful
• Regardless of stopping reason, the result survived
• Static sites outlive their authors

The word "abandoned" doesn't accurately describe these projects. "Stopped" is more neutral. "Completed" is sometimes more accurate.

Draft typology based on four examples. More patterns likely exist.