We stand at a crossroads in the history of digital culture.
Path 1: Platform Feudalism
Continued consolidation under Big Tech monopolies
Users as perpetual tenants, renting digital existence
Culture murdered whenever it's unprofitable
Surveillance capitalism extracting behavioral data as raw material
Every generation loses its digital history to corporate whims
Path 2: Regulatory Containment
Governments regulate platforms (antitrust, interoperability mandates, data protection)
Platforms become quasi-utilities, like phone companies
Improvement over feudalism, but still centralized
Corporate landlords remain, just with more oversight
Users gain some protections but not sovereignty
Path 3: Digital Sovereignty (The Third Way)
Users own their identities, connections, and ground
Distributed infrastructure: federated, P2P, cooperative
Culture persists independent of corporate survival
Economic models that don't require surveillance or extraction
Preservation built into system design, not emergency afterthought
This book has been building toward Path 3. Every chapter—from the Archaeobyte Taxonomy to the Three Pillars, from Triage to Institution Building, from Movement Strategy to Public Intellectual practice—has prepared you to forge the Third Way.
This final chapter asks: What does the Third Way actually look like? Not as abstract ideal, but as concrete system design. What would we build if we started over, knowing everything we know about how platforms murder culture?
This is our manifesto. Our blueprint. Our declaration that another internet is possible.
Before designing systems, we must articulate core principles—the non-negotiables that distinguish the Third Way from both feudalism and containment.
Declaration, Connection, Ground must be user-owned, not platform-granted.
This means:
Identities are portable:
you@yourdomain.com, not platform.com/you
Data is exportable: Full archives, usable formats, no lock-in
Infrastructure is exit-able: Can migrate between providers without losing connections
What this rules out:
Platforms that own your username
Social graphs you can't export
Proprietary formats that trap your data
What this enables:
Federation (Mastodon, Matrix, email model)
Self-hosting (for those with technical capacity)
Portable hosting (Ghost, WordPress—custom domain, full export)
Systems must be built to outlast their creators.
This means:
Open standards: Protocols anyone can implement (not proprietary APIs)
Documented architectures: Future archaeologists can understand how it worked
Redundant storage: LOCKSS principle (Lots of Copies Keep Stuff Safe)
Graceful degradation: If advanced features fail, basic content remains accessible
What this rules out:
Closed-source platforms with no documentation
Centralized servers as single point of failure
Formats that require vendor software to read
What this enables:
Internet Archive can crawl and preserve
Community can fork if maintainers abandon
Content survives platform death
You cannot be sovereign if platforms monetize your behavior through surveillance.
This means:
No behavioral tracking for ads: No surveillance infrastructure
Transparent business models: Users know how platform makes money
Data minimization: Collect only what's needed for service to function
What this rules out:
Facebook/Google ad model (surveillance-funded)
"Free" services that sell user data
Algorithmic manipulation for engagement (rage-farming)
What this enables:
Subscriptions (Ghost, Fastmail)
Freemium (Proton, Signal)
Cooperatives (user-owned platforms)
Public funding (Wikipedia, NPR model)
Network effects must not create lock-in.
This means:
Open protocols: ActivityPub, Matrix, RSS—anyone can implement
Account portability: Can switch providers, keep followers
Cross-platform communication: Email model (Gmail users can email Outlook users)
What this rules out:
Walled gardens (Instagram can't message TikTok)
Platform-specific features that prevent migration
Proprietary networks with no bridges
What this enables:
Competition (switching costs are low)
Innovation (anyone can build better client)
Exit rights (leave bad platform without losing community)
Users must have voice in how platforms are run.
This means:
Cooperative ownership: Users vote on major decisions
Transparent governance: Public board meetings, documented policies
Community moderation: Federated model where instance admins set rules
What this rules out:
Benevolent dictators (even well-meaning founders eventually sell or die)
Venture capital (investors demand growth and exit, not sustainability)
Opaque ToS changes (platforms changing rules without user input)
What this enables:
Platform cooperatives (Stocksy, Resonate)
Federated governance (Mastodon instances)
Non-profit stewardship (Wikimedia, Internet Archive)
Shared cultural resources cannot be privatized.
This means:
Public domain by default: Content should eventually enter commons
Anti-enclosure licensing: Copyleft (GPL, CC-BY-SA) prevents proprietary capture
Archival rights: Society has right to preserve culture, even if corporate copyright opposes
What this rules out:
Perpetual copyright (Disney extending terms forever)
DRM that prevents preservation
Platforms claiming ownership of user-generated content
What this enables:
Remix culture (legal to build on others' work)
Long-term preservation (archives can save copyrighted material)
Cultural continuity (each generation accesses previous generations' work)
With principles established, how do we build the Third Way? What does the technical architecture look like?
Problem: Centralized platforms own your identity. If banned, "you" cease to exist.
Third Way Solution: Federated Identity
Model: Email + Domain Names
Your identity: yourname@yourdomain.com
Domain is yours (registered, portable)
Email provider can change (Gmail → Fastmail → self-hosted), identity stays same
Applied to Social Media:
Mastodon: @yourname@yourdomain.com
You run instance, or use hosting service (but can migrate)
Portable across ActivityPub-compatible platforms
Applied to Authentication:
OpenID Connect: yourdomain.com as identity
Log in to services with your domain (not "Sign in with Google")
You control authentication (can revoke access)
Key Technologies:
DNS (for domain-based identity)
ActivityPub (for federated social)
DID (Decentralized Identifiers, for blockchain-based identity—though controversial)
Trade-offs:
Requires owning domain (~$15/year—barrier for some)
Technical complexity higher than creating Facebook account
But: True sovereignty requires some cost/effort
Problem: Platforms mediate all communication, can shadowban, algorithmically filter, or shut down.
Third Way Solution: End-to-End Encrypted, Federated Communication
Model: Email (for public/async) + Signal (for private/sync)
For Public Communication (Posts, Blogs):
RSS/Atom: Anyone can subscribe to anyone (no algorithmic feed)
ActivityPub: Federated timeline (like email—Gmail users see Outlook users' posts)
Webmentions: Decentralized replies (your blog can reply to mine, no centralized comment system)
For Private Communication (Messaging):
Matrix: Federated, E2E encrypted chat (like Signal + email model)
Signal Protocol: Gold standard E2E encryption
No metadata surveillance: Platforms can't read content or build social graphs
For Discovery:
Search engines: Decentralized (YaCy) or privacy-respecting (DuckDuckGo, Kagi)
Social bookmarking: User-curated (not algorithmic)
RSS readers: User chooses what to follow (not platform-recommended)
Key Technologies:
ActivityPub, Matrix (federation)
Signal Protocol (E2E encryption)
RSS/Atom (syndication)
Trade-offs:
Discovery harder (no algorithmic recommendation of "people you might know")
Requires active curation (following people deliberately, not passively scrolling feed)
But: No manipulation, no surveillance
Problem: Platforms store your data on their servers. If they shut down or ban you, data vanishes.
Third Way Solution: Distributed, Redundant, User-Controlled Storage
Model: LOCKSS + IPFS
For Personal Data:
Self-hosting: NAS (Synology, QNAP) or VPS (DigitalOcean, Linode)
Distributed backup: Syncthing (P2P sync), Restic (encrypted backups to cloud)
Portable hosting: Ghost Pro, WordPress with custom domain (can migrate if provider dies)
For Public Archives:
IPFS (InterPlanetary File System): Content-addressed, distributed storage
BitTorrent: Proven P2P distribution (Archive Team uses this)
LOCKSS networks: Libraries collectively preserve (multiple institutions, redundant copies)
For Long-Term Preservation:
Open formats: Markdown, HTML, plain text (readable in 50 years)
Format migration: Periodic conversion as standards evolve
Emulation: Preserve original formats + software to read them
Key Technologies:
IPFS, Dat/Hypercore (distributed storage)
LOCKSS (institutional redundancy)
Open formats (Markdown, HTML, JSON)
Trade-offs:
Self-hosting requires technical skill and hardware
Distributed storage slower than centralized cloud
But: No single point of failure, no corporate control
Problem: Platforms need revenue. Advertising = surveillance. Subscriptions alone may not scale.
Third Way Solution: Hybrid Economic Models
Option 1: Direct User Payment
Subscriptions (Ghost, Fastmail, Proton)
One-time purchases (Obsidian, Things)
Donations (Wikipedia, Internet Archive)
Option 2: Cooperative Ownership
Users own platform collectively (Stocksy for photographers, Resonate for musicians)
Profits distributed to member-owners
Democratic governance
Option 3: Public Funding
Government grants (NEH, Mellon, Mozilla Foundation)
Public broadcasting model (NPR, BBC—funded by public, no ads)
University/library hosting (LOCKSS networks)
Option 4: Open Core
Core software free/open-source (WordPress, Ghost, Mastodon)
Hosting/support/premium features paid (WordPress.com, Ghost Pro)
Cannot enclose the core (GPL prevents proprietary forks)
Option 5: Solidarity Economy
Cross-subsidization (profitable projects fund loss-leaders)
Sliding scale (wealthy users pay more, subsidize free tiers)
Example: Means-based pricing (Patreon alternative)
Key Insight: No single model works for all. Need ecosystem of models, all non-surveillance.
Trade-offs:
Direct payment excludes those who can't pay (need solidarity mechanisms)
Public funding vulnerable to political shifts
Cooperatives hard to scale (governance complexity)
But: All preferable to surveillance capitalism
Problem: Platforms are dictatorships (even benevolent ones eventually betray users).
Third Way Solution: Federated, Democratic Governance
Model: Mastodon's Federation + Co-op Governance
Federated Moderation:
Each instance sets own rules (no universal ToS)
Instances can defederate (block other instances)
Users choose instance that matches their values
If admin becomes tyrant, users migrate (account portability)
Cooperative Governance:
Platform owned by users/workers (one member, one vote)
Major decisions require supermajority (75%+ approval)
Transparent financials, public board meetings
Cannot sell to corporation (bylaws prevent acquisition)
Open Source + Forking:
Code is public (GPL/AGPL license)
If maintainers sell out, community forks (Nextcloud forked from ownCloud)
Prevents capture
Key Technologies:
ActivityPub (enables federation)
Cooperative bylaws (legal structure)
Open source licenses (GPL, AGPL)
Trade-offs:
Federation creates fragmentation (different instances, different rules)
Democratic governance is slow (voting takes time)
But: No single point of failure, no dictator risk
Let's imagine a day in the life of a Third Way internet user in 2035:
7:00 AM — Wake up, check RSS reader (no algorithm, just chronological feeds from blogs/sites you chose)
7:30 AM — Write blog post on your site
(yourname.com). Auto-syndicates to:
Fediverse (ActivityPub)
Email newsletter (subscribers you own)
RSS (anyone can subscribe)
All from your domain. If your hosting provider dies, you migrate (same domain, same URLs).
8:00 AM — Read replies via Webmentions (other blogs responding to yours, comments appear on your site, no centralized comment system)
12:00 PM — Video call with friend using Jitsi (open source, self-hosted, E2E encrypted, no Zoom spying)
1:00 PM — Check Matrix (federated chat). Messages from friends on different servers (some self-hosted, some using hosting services, all interoperate)
2:00 PM — Browse Fediverse (Mastodon, Pixelfed, PeerTube). See posts from across federated instances. No ads, no algorithmic manipulation, chronological.
6:00 PM — Watch video on PeerTube (federated YouTube alternative, creator-owned)
7:00 PM — Listen to music on Bandcamp (artists get 82% of revenue, you own MP3s, DRM-free)
8:00 PM — Participate in forum (self-hosted Discourse, community-owned, full export available)
10:00 PM — Automatic backup runs:
Your blog: Synced to NAS (RAID, redundant)
Photos: Syncthing to friend's server (mutual backup)
Notes: Obsidian vault (Markdown files, local + cloud backup)
If any service shuts down tomorrow, you have:
All your data (multiple copies)
Your domain (persistent identity)
Your social graph (portable followers via ActivityPub)
You are sovereign.
The Third Way doesn't happen overnight. How do we transition from Platform Feudalism to Digital Sovereignty?
Goal: Prove alternatives can work at scale.
Actions:
Grow Mastodon/Fediverse: 10M+ users (demonstrate federation viability)
Launch platform co-ops: Stocksy-style models for social media, hosting, storage
Expand public infrastructure: Library-hosted Mastodon instances, university archives
Create easy on-ramps: Tools like Yunohost (one-click self-hosting), Pika (easy static sites)
Success Metrics:
5% of social media users on federated platforms
10+ viable platform cooperatives (profitable, member-owned)
100+ universities/libraries hosting instances
Open-source alternatives exist for all major platforms (social, messaging, storage, video)
Goal: Legal frameworks that enable Third Way, constrain platforms.
Actions:
Interoperability mandates: EU Digital Markets Act model (platforms must allow third-party clients)
Right to archive: Laws allowing libraries/archives to preserve copyrighted content
Data portability: GDPR-style requirements (full exports in usable formats)
Anti-monopoly enforcement: Break up Big Tech, prevent acquisitions that consolidate power
Success Metrics:
US/EU laws require platform interoperability
Copyright exceptions for preservation (fair use expanded)
Surveillance capitalism regulated (behavioral targeting restricted)
No new platform monopolies (mergers blocked)
Goal: Sovereignty becomes expectation, not exception.
Actions:
Digital literacy: Schools teach domain ownership, data sovereignty, federation
Cultural normalization: "Where's your domain?" becomes as common as "What's your email?"
Professional requirement: Journalists, academics, professionals expected to have sovereign presence
Platform stigma: Using corporate platforms seen as irresponsible (like smoking—stigmatized, not illegal)
Success Metrics:
50% of internet users own domains
25% of social media on federated platforms
Surveillance-based platforms in decline (losing users, not growing)
"Digital sovereignty" taught in schools
Goal: Third Way is default, feudalism is legacy.
Actions:
Public infrastructure: Governments run federated instances (like public libraries run physical space)
Cooperative economy: Platform co-ops dominant in hosting, social media, cloud storage
Preservation embedded: All systems designed for 50+ year persistence
No more platform murders: Culture persists because infrastructure is distributed and community-owned
Success Metrics:
Majority of internet users on sovereign infrastructure
Corporate platforms either reformed (co-ops) or dead
Cultural memory preserved (no more GeoCities-scale losses)
Next generation can't imagine Platform Feudalism (it's history)
Response:
Email was "too technical" in 1995. Now everyone has email.
Complexity can be hidden (Ghost makes custom domains easy, Mastodon hosts handle technical bits)
Trade-off: Sovereignty requires some effort, but tools can minimize it
Counter-Question: Is it really "easier" to have your identity revoked, data deleted, and memories erased by platforms?
Response:
Email is federated. Do you feel "fragmented" from Gmail users if you use Fastmail? No.
Federation enables choice (pick instance that matches your values)
Interoperability prevents fragmentation (ActivityPub lets instances communicate)
Counter-Question: Isn't platform monopoly worse fragmentation? (Twitter vs. TikTok vs. Instagram—all walled gardens)
Response:
True in short term. But platforms eventually betray convenience (Twitter's chaos, Facebook's privacy violations)
Once betrayed, users seek alternatives (see: Twitter → Mastodon migration)
Convenience is temporary; sovereignty is permanent
Counter-Question: Is it convenient when the platform shuts down and you lose everything?
Response:
Federated moderation: Each instance sets rules, defederates bad actors
Harder than centralized, yes. But centralized moderation has failed (harassment, hate speech, manipulation persist)
Trade-off: Imperfect distributed moderation > failed centralized moderation
Counter-Question: Has centralized moderation worked? (No—Facebook/Twitter full of toxicity despite armies of moderators)
Response:
You already trust strangers (Google, Meta engineers you've never met)
Federation distributes trust (if one admin is bad, you migrate)
Can self-host if you want ultimate control
Counter-Question: Is trusting a for-profit corporation safer than trusting a community-run instance?
Response:
They'll try. But open protocols are hard to kill (email survived, BitTorrent survived)
Network effects work both ways (once federated platforms hit critical mass, they grow)
Laws can help (interoperability mandates prevent lock-in)
Counter-Question: If we don't try, Big Tech wins by default. Is surrender preferable?
As Archaeobytologists, what's our work in forging the Third Way?
Archive platform murders to document what went wrong:
GeoCities, Vine, Google+, Tumblr NSFW purge
Build "Museum of Murdered Platforms" (physical/digital)
Use archives to teach: "This is what happens when you don't own your ground"
Purpose: Historical memory. Can't build future if we forget past.
Forge tools and institutions that embody Three Pillars:
Launch preservation co-ops (community-owned archives)
Create sovereignty tools (easy domain setup, federated hosting)
Design long-term institutions (50-year orgs, LOCKSS networks)
Purpose: Demonstrate alternatives are viable. Proof of concept.
Educate next generation on digital rights and responsibilities:
University courses in Archaeobytology (this textbook)
Workshops for communities (how to own your domain, export data)
Public talks (TED, podcasts, op-eds)
Purpose: Cultural shift. People can't demand sovereignty if they don't know it exists.
Fight for laws that enable Third Way:
Testify at hearings (right to archive, interoperability, data portability)
Draft model legislation (work with EFF, Creative Commons)
Build coalitions (libraries, journalists, activists, academics)
Purpose: Legal infrastructure. Alternatives need policy support to compete with monopolies.
Publish research on platform power, preservation methods, sovereignty design:
Academic journals (Journal of Archaeobytology, DH journals, STS venues)
Books (popular and scholarly)
Open documentation (wikis, tutorials, case studies)
Purpose: Knowledge infrastructure. Field needs canon, methods, theory.
You are:
Archivist (preserving murdered platforms)
Builder (forging sovereign alternatives)
Teacher (spreading digital literacy)
Advocate (fighting for policy change)
Scholar (documenting and theorizing)
The Third Way requires all five roles. You don't have to do everything, but the field collectively must.
1. Digital culture is worth preserving.
Every GeoCities homepage, every Vine, every forum post—these are artifacts of human creativity and connection.
Platforms murder culture. We refuse to accept this.
2. Users deserve sovereignty.
You should own your identity, control your connections, possess your ground.
Platforms are landlords. We advocate for ownership.
3. Surveillance capitalism is illegitimate.
Monetizing behavior through tracking is exploitation.
We build economic models that don't require surveillance.
4. Preservation is a moral imperative.
Future generations deserve access to our digital culture.
We are custodians, not just consumers.
5. The Third Way is possible.
Federated, cooperative, community-owned infrastructure can work.
We have the technology. We need the will.
1. Archive what platforms murder.
Scrape dying platforms.
Curate rescued artifacts.
Make archives accessible.
2. Build alternatives that resist murder.
Design for sovereignty (Three Pillars).
Create institutions that last 50+ years.
Open-source everything.
3. Teach digital sovereignty.
Write, speak, teach.
Make sovereignty accessible.
Raise generation that demands ownership.
4. Advocate for systemic change.
Fight for right to archive.
Demand platform interoperability.
Break monopolies.
5. Practice what we preach.
Own our domains.
Use federated platforms.
Preserve our own data.
1. Platform feudalism (users as tenants)
2. Surveillance capitalism (behavior as commodity)
3. Planned obsolescence (culture murdered for profit)
4. Forced amnesia (deletion of digital history)
5. Learned helplessness ("Platforms will always win")
Archaeobytology isn't just a discipline—it's a movement.
We are scholars and smiths, archivists and advocates, mourners and builders.
We study the dead to prevent future murders.
We preserve the past to forge the future.
We are the Third Way.
And we are just beginning.
This textbook began with a question: What is Archaeobytology?
Now you know:
Theory (Taxonomy, Three Pillars, Triage, Discipline Formation)
Methods (Excavation, Forensics, Workflow)
Practice (Institution Building, Sovereignty Design, Commons Governance, Memory Institutions)
Strategy (Political Economy, Movement Building, Public Scholarship)
You have the tools. Now the question is: What will you do?
Will you:
Archive a dying platform before it vanishes?
Build a tool that embodies sovereignty?
Teach a course that trains the next generation?
Write an op-ed that shifts public discourse?
Found an organization that outlasts you?
Archaeobytology doesn't exist yet—not fully. There are no departments, no tenure-track jobs, no professional society. But there could be, if we build them.
In 20 years, this could be a recognized discipline. Students could major in it. Governments could fund it. Culture could be preserved, not murdered.
Or: This could be a footnote. A quirky experiment by scattered practitioners. Forgotten when platforms finally consolidate into permanent monopolies.
That choice is ours.
Every time you:
Preserve an artifact, you're voting for the Third Way
Build a tool, you're forging alternatives
Teach sovereignty, you're spreading the movement
Advocate for policy, you're shifting power
Call yourself an Archaeobytologist, you're making the discipline real
This textbook is a beginning, not an ending. It codifies existing practice and proposes a future. But books don't build disciplines—people do.
You, reading this now, are part of the founding generation. The choices you make—what you preserve, what you build, what you teach—will shape whether Archaeobytology becomes real.
So ask yourself:
What will you build that outlasts you?
Not what will you consume, what will you scroll, what will you post into the void of platforms that will delete it when you stop being profitable.
What will you build that future generations can find, study, and build upon?
A website on your own domain that persists for decades?
An archive of a community that would otherwise be forgotten?
A tool that helps others own their digital lives?
A course that trains students to become Archaeobytologists?
An institution—a journal, a conference, a center—that becomes infrastructure?
The Third Way requires builders.
Not just theorists. Not just critics. Builders.
People who preserve, create, organize, teach, and advocate.
People who look at murdered platforms and say: Never again.
People who look at surveillance capitalism and say: Not us.
People who look at the choice between feudalism and sovereignty and say: We choose the Third Way.
Design your contribution to the Third Way. Choose one:
Pick a vulnerable platform
Design complete preservation strategy
Execute (or outline execution plan if resources lacking)
Identify a sovereignty gap (something users can't easily do)
Design tool that fills gap
Build prototype or spec for others to build
Design organization that embodies Three Pillars
Complete business plan (funding, governance, sustainability)
Launch (or create plan for launch)
Identify policy change needed for Third Way
Design 5-year campaign to achieve it
Begin execution (write op-ed, contact legislators, build coalition)
Design course, workshop, or curriculum
Create materials (syllabus, readings, assignments)
Teach it (or find someone who will)
Requirements (3,000+ words):
Problem diagnosis (what's broken now?)
Third Way solution (how does your project fix it?)
Implementation plan (concrete steps, timeline, resources)
Three Pillars assessment (does it embody sovereignty?)
Sustainability (how does it last 10+ years?)
Impact metrics (how do you measure success?)
Then: Actually do it.
Don't just write the plan. Execute.
Build something.
Preserve something.
Teach someone.
Advocate somewhere.
Make Archaeobytology real.
Because the Third Way doesn't forge itself.
You forge it.
Now go.
Build something that outlasts you.
This textbook has cited hundreds of sources. Here's the essential reading list—the books every Archaeobytologist should read.
Lessig, Lawrence. Code: Version 2.0. Basic Books, 2006.
How digital architecture embodies values
Zuboff, Shoshana. The Age of Surveillance Capitalism. PublicAffairs, 2019.
Definitive critique of platform economics
Ostrom, Elinor. Governing the Commons. Cambridge, 1990.
How to manage shared resources without state or market
Doctorow, Cory. The Internet Con: How to Seize the Means of Computation. Verso, 2023.
Practical vision for interoperability and user power
Kirschenbaum, Matthew. Mechanisms: New Media and the Forensic Imagination. MIT Press, 2008.
Foundational text on digital materiality
Chun, Wendy Hui Kyong. Programmed Visions: Software and Memory. MIT Press, 2011.
Ernst, Wolfgang. Digital Memory and the Archive. Minnesota, 2013.
Brügger, Niels, and Ralph Schroeder, eds. The Web as History. UCL Press, 2017.
Gillespie, Tarleton. Custodians of the Internet. Yale, 2018.
Noble, Safiya Umoja. Algorithms of Oppression. NYU Press, 2018.
Pasquale, Frank. The Black Box Society. Harvard, 2015.
Benkler, Yochai. The Wealth of Networks. Yale, 2006.
Bollier, David. Think Like a Commoner. New Society, 2014.
Scholz, Trebor. Platform Cooperativism. Rosa Luxemburg Stiftung, 2016.
Schneier, Bruce. Data and Goliath. Norton, 2015.
Véliz, Carissa. Privacy Is Power. Melville House, 2020.
Rushkoff, Douglas. Throwing Rocks at the Google Bus. Portfolio, 2016.
Sennett, Richard. The Craftsman. Yale, 2008.
Pye, David. The Nature and Art of Workmanship. Cambridge, 1968.
Derrida, Jacques. Archive Fever. Chicago, 1996.
Caswell, Michelle. Urgent Archives. Routledge, 2021.
Klein, Julie Thompson. Interdisciplining Digital Humanities. Michigan, 2015.
Kuhn, Thomas. The Structure of Scientific Revolutions. Chicago, 1962.
Kahle, Brewster. "Preserving the Internet." Scientific American, 1997.
Bush, Vannevar. "As We May Think." The Atlantic, 1945.
Raymond, Eric. "The Cathedral and the Bazaar." 1997.
You've reached the end of this textbook.
But this is not the end of Archaeobytology.
It's the beginning.
The field exists because you make it real.
Every artifact you preserve. Every tool you build. Every course you teach. Every policy you advocate for.
That's Archaeobytology.
Welcome to the discipline.
Now go forth and forge the Third Way.
End of Textbook
The following appendices provide practical resources for Archaeobytologists:
Appendix A: Glossary of Terms
Appendix B: Essential Tools & Resources
Appendix C: Sample Syllabi (101, 200, 300 levels)
Appendix D: Teaching Resources
Appendix E: Professional Resources (Career Pathways, Job Descriptions, Certification)
[Appendices would be developed separately as standalone documents]
Archaeobytology: Theory and Practice of Digital Sovereignty
Author: [To be determined—likely community-authored/edited given the discipline's nascent state]
Publication Model: Open Access
Free PDF download
Print-on-demand (estimated $40 paperback)
CC BY-SA 4.0 License (share, adapt, but credit and keep open)
Suggested Citation:
Archaeobytology: Theory and Practice of Digital Sovereignty. [Publisher], [Year]. [URL].
Companion Website: archaeobytology.org
Video lectures (18 chapters × 20 min)
Discussion forums
Tools repository
Syllabi database
Community directory
For Instructors: Instructor's Guide available at archaeobytology.org/teaching
Lecture slides
Assignment rubrics
Discussion prompts
Quiz/exam questions
Contact: archaeobytology@[domain] for corrections, suggestions, course adoption inquiries
The textbook you hold is a founding document. By reading it, teaching from it, building on it, and critiquing it, you're helping create a discipline.
Thank you for being part of the founding generation of Archaeobytology.
Now go build something that outlasts you.