Jump to content

Meta: Difference between revisions

From Archive
Created page with "= Meta = ''How this archive works, why it exists, and how to navigate it'' == What This Is == Personal knowledge base running MediaWiki at `archive.ejfox.com`. Not a blog - those are polished artifacts. This is a living dump of evolving thoughts, technical notes, and cross-referenced ideas. === Blog vs Archive === * '''Blog''' - Cohesive artifacts frozen in time, images, interactives * '''Archive''' - Info dump, post bin, stuff that used to be gists == Structure ==..."
 
No edit summary
 
(One intermediate revision by the same user not shown)
Line 7: Line 7:
Personal knowledge base running MediaWiki at `archive.ejfox.com`. Not a blog - those are polished artifacts. This is a living dump of evolving thoughts, technical notes, and cross-referenced ideas.
Personal knowledge base running MediaWiki at `archive.ejfox.com`. Not a blog - those are polished artifacts. This is a living dump of evolving thoughts, technical notes, and cross-referenced ideas.


=== Blog vs Archive ===
'''Blog vs Archive:'''
* '''Blog''' - Cohesive artifacts frozen in time, images, interactives
* Blog = frozen artifacts with images/interactives
* '''Archive''' - Info dump, post bin, stuff that used to be gists
* Archive = info dump, post bin, ex-gists


== Structure ==
== Structure ==


* '''[[Technical]]''' - CLI workflows, APIs, scripts, solutions
* [[Technical]] - CLI workflows, APIs, scripts, solutions
* '''[[Dataviz]]''' - D3 experiments, Observable notebooks, techniques   
* [[Dataviz]] - D3 experiments, Observable notebooks, techniques   
* '''[[Journalism]]''' - Methods, sources, investigations, published work
* [[Journalism]] - Methods, sources, investigations, published work
* '''[[Projects]]''' - Work logs, collaboration notes, active stuff
* [[Projects]] - Work logs, collaboration notes, active stuff


Cross-links create connections. Search finds forgotten solutions.
Cross-links create knowledge networks. Categories auto-cluster. Search finds forgotten solutions.


== Usage Patterns ==
== MediaWiki Advantages ==


=== Personal Reference ===
* '''Revision history''' - Every edit timestamped, diffable, API-accessible
"How did I solve X six months ago?" Full-text search across all technical solutions, project notes, and methodology docs.
* '''Templates''' - Standardized project info, live API data, status indicators
* '''Categories''' - `[[Category:Active]]` enables complex queries
* '''Special pages''' - `Special:WantedPages` finds knowledge gaps automatically
* '''Talk pages''' - Meta-commentary separate from main content
* '''Mobile editing''' - Functional phone workflow
* '''AI-parseable''' - Structured data for better LLM context


=== AI Context ===
== Usage Patterns ==
Language models can reference this for personalized assistance. Better responses when the AI knows your actual workflows, preferences, and past solutions.


=== Mobile Updates ===
'''Personal:''' "How did I solve X six months ago?" - full-text search + revision history
Can update from phone. Quick capture of ideas, solutions, links. Organize later.
'''AI Context:''' Structured personal data = better AI responses
'''Mobile:''' Voice-to-text dumps, organize later on desktop


== Technical Notes ==
== Content Pipeline ==


=== MediaWiki Advantages ===
<pre>
* Mature linking system with backlinks
Raw notes → linking → categorization → cross-referencing →
* Mobile editing capability 
templates → API integration → maybe blog post/project
* Built-in version control
</pre>
* Full-text search
* AI-parseable structure
* Export flexibility


=== Content Flow ===
== Philosophy ==
Raw notes → basic linking → cross-referencing → synthesis → sometimes becomes blog post or project


== Philosophy ==
Ideas evolve. Capture incomplete > lose completely. Version-controlled thinking - add new perspectives, don't edit history. Cross-domain connections yield best insights.


Ideas evolve. Capture incomplete thoughts rather than lose them. Version-controlled thinking - don't edit history, add new perspectives. Cross-domain connections often yield the best insights.
Gwern-inspired: document interests early, people find value as they catch up.


Inspired by [https://gwern.net/ Gwern's] long-term documentation approach - if you're ahead of the curve and document your interests, people will find your work valuable as they catch up.
== Success Metrics ==


== AI Integration ==
* Cross-reference density
* Search success rate 
* Mobile edit frequency
* Forgotten insight rediscovery
* Archive → shipped project conversion


This archive provides context that makes AI interactions more useful:
== Automation ==
* Personal APIs and technical setup
* Project history and decision rationale 
* Cross-references between different work domains
* Methodology documentation


== Maintenance ==
* Personal APIs auto-update project status
* Git hooks cross-reference commits
* Category intersection analysis
* Knowledge gap identification


Review monthly for orphaned pages and emerging patterns. Structure evolves with needs. Content stays - context accumulates value over time.
External memory experiment: does systematic externalization improve thinking? Measuring outcomes over 10+ years.


----
----


''Archive running since {{CURRENTYEAR}} • Updated from terminal & mobile • Cross-referenced & searchable''
''Archive running since {{CURRENTYEAR}} • Terminal & mobile • Cross-referenced & searchable''


[[Category:Documentation]]
[[Category:Documentation]]

Latest revision as of 02:35, 29 May 2025

Meta

How this archive works, why it exists, and how to navigate it

What This Is

Personal knowledge base running MediaWiki at `archive.ejfox.com`. Not a blog - those are polished artifacts. This is a living dump of evolving thoughts, technical notes, and cross-referenced ideas.

Blog vs Archive:

  • Blog = frozen artifacts with images/interactives
  • Archive = info dump, post bin, ex-gists

Structure

  • Technical - CLI workflows, APIs, scripts, solutions
  • Dataviz - D3 experiments, Observable notebooks, techniques
  • Journalism - Methods, sources, investigations, published work
  • Projects - Work logs, collaboration notes, active stuff

Cross-links create knowledge networks. Categories auto-cluster. Search finds forgotten solutions.

MediaWiki Advantages

  • Revision history - Every edit timestamped, diffable, API-accessible
  • Templates - Standardized project info, live API data, status indicators
  • Categories - `` enables complex queries
  • Special pages - `Special:WantedPages` finds knowledge gaps automatically
  • Talk pages - Meta-commentary separate from main content
  • Mobile editing - Functional phone workflow
  • AI-parseable - Structured data for better LLM context

Usage Patterns

Personal: "How did I solve X six months ago?" - full-text search + revision history AI Context: Structured personal data = better AI responses Mobile: Voice-to-text dumps, organize later on desktop

Content Pipeline

Raw notes → linking → categorization → cross-referencing → 
templates → API integration → maybe blog post/project

Philosophy

Ideas evolve. Capture incomplete > lose completely. Version-controlled thinking - add new perspectives, don't edit history. Cross-domain connections yield best insights.

Gwern-inspired: document interests early, people find value as they catch up.

Success Metrics

  • Cross-reference density
  • Search success rate
  • Mobile edit frequency
  • Forgotten insight rediscovery
  • Archive → shipped project conversion

Automation

  • Personal APIs auto-update project status
  • Git hooks cross-reference commits
  • Category intersection analysis
  • Knowledge gap identification

External memory experiment: does systematic externalization improve thinking? Measuring outcomes over 10+ years.

Archive running since 2025 • Terminal & mobile • Cross-referenced & searchable

Retrieved from "https://archive.ejfox.com/index.php?title=Meta&oldid=19"