THE ZETTELKASTEN MANIFESTO | What is a Zettelkasten?  ## Metadata - Author: [[YouTube]] - Full Title: THE ZETTELKASTEN MANIFESTO | What is a Zettelkasten? - Category: #articles - Document Note: --- tags: [zettelkasten, note-taking, knowledge-management] author: Shu Omi source: YouTube reference: https://www.youtube.com/watch?v=c5Tst3-zcWI date created: 2024-12-19 08:30 --- # 🏷️ Title: THE ZETTELKASTEN MANIFESTO | What is a Zettelkasten? ## 🧰 Action Inbox - [H1] Stop copying Luhmann's exact system — find your own approach #zettelkasten - [H2] Focus on ID, tags, and relationships over rigid structure — 00:05:23 #methodology - [H3] Think graph database not relational database — 00:12:45 #system-design ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Zettelkasten.de](https://zettelkasten.de) - [The Archive app by Daniel Lüdecke](https://zettelkasten.de/the-archive/) ## 📝 Summary - A critique of traditional Zettelkasten tutorials that over-emphasize copying Niklas Luhmann's exact system - Argues modern Zettelkasten should function like graph databases rather than rigid relational databases - Key insight: Focus on flexible containers (ID, tags, relationships) rather than prescribed content structure - Aimed at knowledge workers struggling to implement Zettelkasten effectively - Risk: Abandoning structure entirely vs. maintaining too much rigidity - Bottom line: Your Zettelkasten should adapt to your thinking, not force your thinking into predefined boxes ## 📖 Main Content The video presents a manifesto against the "ghost of Niklas Luhmann" that haunts modern Zettelkasten implementations. The author argues that most online tutorials create unnecessary constraints by trying to exactly replicate Luhmann's analog system in digital environments. Luhmann's system had three components: sequential ID numbers, note content, and references to related notes. This worked as a manual relational database with one table and three columns. However, modern knowledge work involves diverse media types (text, images, videos, audio) and varying note structures that don't fit rigid templates. The solution proposed is thinking of Zettelkasten as a graph database rather than a relational one. Instead of forcing all notes into identical structures, each note becomes a flexible container with minimal metadata (ID, tags, relationships) while allowing arbitrary content inside. The key insight is that different people have different thinking patterns and information needs. A successful Zettelkasten adapts to the user rather than forcing conformity to historical precedent. ## 🗒️ Notes #### ⏱️ [00:00:00](https://www.youtube.com/watch?v=c5Tst3-zcWI?t=0) — [H1] The Specter of Luhmann Haunts Academia - Key idea: Luhmann's influence creates confusion about what Zettelkasten actually is - Evidence: "All the powers of the old analog world have entered into a holy Alliance to exorcise the specter" #### ⏱️ [00:01:30](https://www.youtube.com/watch?v=c5Tst3-zcWI?t=90) — [H2] Traffic Analysis Reveals Tutorial Problems - Key idea: People seek implementation guides but find unhelpful prescriptive rules - Evidence: "A lot of traffic is actually going to my two guides on how to use Zettel as a Zettelkasten" #### ⏱️ [00:02:45](https://www.youtube.com/watch?v=c5Tst3-zcWI?t=165) — [H2] The Booby Trap of Exact Replication - Key idea: Copying Luhmann exactly leads to failure for most people - Evidence: "I had a hard time getting started and for four or five years I had nothing resembling Zettelkasten" #### ⏱️ [00:03:30](https://www.youtube.com/watch?v=c5Tst3-zcWI?t=210) — [H2] Excessive Constraints Kill Creativity - Key idea: Too many structural requirements prevent natural note-taking - Evidence: "You need ID, text, related notes, outline notes, meta notes... this is not going to work" #### ⏱️ [00:05:23](https://www.youtube.com/watch?v=c5Tst3-zcWI?t=323) — [H1] Luhmann's Three Components Explained - Key idea: Original system had ID numbers, content, and reference lists - Evidence: "Sequential numbers, actual content, and sequence of numbers referencing other notes" #### ⏱️ [00:07:15](https://www.youtube.com/watch?v=c5Tst3-zcWI?t=435) — [H2] Zettelkasten as Manual Database - Key idea: Luhmann accidentally created what we now call a relational database - Evidence: "Exactly the form that contemporary databases and web services use" #### ⏱️ [00:09:00](https://www.youtube.com/watch?v=c5Tst3-zcWI?t=540) — [H2] Modern Knowledge Has More Complexity - Key idea: Digital knowledge work involves multiple media types and structures - Evidence: "Images, videos, sounds, ethnographic research data, inconsistent formats" #### ⏱️ [00:10:30](https://www.youtube.com/watch?v=c5Tst3-zcWI?t=630) — [H2] Relational Database Problems - Key idea: Adding columns for every data type creates automation nightmares - Evidence: "Duration for videos, location for images, references for books - how do you search consistently?" #### ⏱️ [00:12:45](https://www.youtube.com/watch?v=c5Tst3-zcWI?t=765) — [H1] Graph Database Solution - Key idea: Use flexible containers instead of rigid table structures - Evidence: "One box to store one chunk of information - image, video, text, whatever" #### ⏱️ [00:14:20](https://www.youtube.com/watch?v=c5Tst3-zcWI?t=860) — [H2] Box Metaphor for Flexible Storage - Key idea: Each note is a container with minimal metadata attached - Evidence: "Put USB stick in box, add tags on paper, search returns relevant boxes" #### ⏱️ [00:16:00](https://www.youtube.com/watch?v=c5Tst3-zcWI?t=960) — [H2] Weak vs Strong Links - Key idea: Tags provide weak connections, IDs provide strong relationships - Evidence: "Tags bring up many results, IDs create direct connections between specific notes" #### ⏱️ [00:17:30](https://www.youtube.com/watch?v=c5Tst3-zcWI?t=1050) — [H1] Core Requirements: ID, Tags, Relationships - Key idea: Only three elements are essential for effective Zettelkasten - Evidence: "You only need an ID, links to other notes, and text" #### ⏱️ [00:18:15](https://www.youtube.com/watch?v=c5Tst3-zcWI?t=1095) — [H2] Reject Prescribed Content Structure - Key idea: Don't force notes into summary-detail-bullets format - Evidence: "Don't listen to people telling you: first summary, then longer text, then bullet points" #### ⏱️ [00:19:00](https://www.youtube.com/watch?v=c5Tst3-zcWI?t=1140) — [H1] Revolutionary Call to Action - Key idea: Overthrow rigid Zettelkasten orthodoxy for flexible personal systems - Evidence: "Let Luhmann tremble at an academic revolution. Researchers have nothing to lose but their chains" ## 📚 References - [Zettelkasten.de](https://zettelkasten.de) - Primary hub for Zettelkasten learning - [The Archive](https://zettelkasten.de/the-archive/) - App resembling Luhmann's system - [Zettel app](https://zettel.app) - Creator's flexible Zettelkasten software ## 🗣️ Paraphrase - Most Zettelkasten tutorials fail because they try to force users into copying Luhmann's specific analog system rather than understanding the underlying principles - Luhmann's system worked as a manual relational database, but modern knowledge work needs the flexibility of graph databases to handle diverse content types - The only essential elements are unique identifiers, searchable tags, and relationship links - everything else should adapt to your personal thinking style ## 📰 Newsletter **Free Your Zettelkasten from Historical Constraints** Struggling with your note-taking system? You're not alone. Most Zettelkasten tutorials create more problems than they solve by forcing rigid structures copied from a 20th-century sociologist. The key insight: Your digital Zettelkasten should work like a graph database, not a relational one. Focus on three essentials - unique IDs, searchable tags, and relationship links - while keeping content structure completely flexible. Whether you're storing research quotes, project notes, or creative ideas, your system should adapt to your thinking patterns, not the other way around. **Try This**: Start with simple containers. Each note gets an ID and tags, but put whatever content makes sense inside. Link related ideas directly rather than forcing everything into identical templates. Resources: [Obsidian](https://obsidian.md/), [Roam Research](https://roamresearch.com/), [Zettel](https://zettel.app/) ## ✅ Action Items #### DevRel - Developer advocacy: Create workshops on flexible knowledge management systems for developers - Education: Develop curriculum comparing database models to note-taking approaches - Developer experience: Document graph-based approaches to technical documentation - Community management: Survey developers on current note-taking pain points #### Community - Maintainers: Create governance templates that avoid over-prescriptive rules - Contributors: Design onboarding that adapts to different learning styles - Ecosystem: Build bridges between note-taking and project management communities #### WordPress - Documentation: Audit HelpHub for overly rigid documentation structures - Design: Research flexible content organization patterns - Meta: Consider graph-based approaches to organizing .org resources ## 🧪 Hypotheses - Flexible note-taking systems lead to better long-term knowledge retention than rigid templates - Graph database mental models produce more creative connections than relational database thinking - Prescriptive tutorials create higher abandonment rates than principle-based guidance - Personal adaptation of systems correlates with sustained usage over time ### 📊 Methodology - A/B test rigid vs flexible onboarding flows for note-taking apps - Survey long-term Zettelkasten users about which elements they actually use - Compare connection patterns in graph vs template-based systems ### ❓ Questions - How do we balance flexibility with enough structure to prevent chaos? - What are the minimum viable constraints for a functional knowledge management system? - How do different personality types respond to structured vs unstructured approaches? ### 🔮 Future Research - Longitudinal studies of knowledge management system evolution - Cross-cultural analysis of note-taking preferences and constraints - Integration patterns between personal knowledge systems and collaborative tools ### 💡 Implications - Practice: Question whether your current note-taking constraints serve your actual thinking - Policy: Avoid over-prescriptive documentation standards that limit natural expression - Education: Focus on principles rather than specific implementations when teaching knowledge management - Funding: Invest in adaptable systems rather than one-size-fits-all solutions ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade (Flesch-Kincaid) #### 👀 Visual learners - Present: Box metaphor, database structure comparisons - Improve: Actual diagrams of graph vs relational structures, visual note examples #### 🔊 Aural learners - Present: Full video with clear narration - Improve: Podcast-style summary, interview format discussion #### 🗣️ Verbal learners - Present: Clear analogies, defined technical terms - Improve: More storytelling about user journeys, concrete examples #### 🧩 Kinesthetic learners - Present: Box manipulation metaphor, hands-on thinking - Improve: Interactive demos, step-by-step setup guides #### 🧠 Logical learners - Present: Database comparison, systematic analysis - Improve: Decision tree for choosing approaches, comparison matrices #### 🧑‍🤝‍🧑 Social learners - Present: Community references, shared struggles - Improve: User testimonials, collaborative examples #### 🧘‍♀️ Solitary learners - Present: Individual system development focus - Improve: Self-assessment quizzes, personal reflection prompts #### 🌿 Naturalistic learners - Present: Evolution from analog to digital systems - Improve: Ecosystem thinking about knowledge environments ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure, descriptive video - Improve: Transcript with time codes, alt text for visual metaphors #### Keyboard navigation - Present: Standard video controls - Improve: Chapter navigation, transcript linking #### Contrast and readability - Present: High contrast video text - Improve: Transcript formatting options #### Text resizing and reflow - Present: Responsive video player - Improve: Scalable transcript interface #### Media and captions - Present: Full video content - Improve: Auto-generated captions, downloadable transcript #### Forms and interactions - Present: Basic video interaction - Improve: Interactive examples, accessible controls ### 🌍 DEIB Assessment #### Cultural breadth - Present: Western academic context primarily - Improve: Examples from different knowledge traditions #### Inclusive language - Present: Generally neutral technical language - Improve: Define academic jargon, avoid assumptions about prior knowledge #### Neurodiversity support - Present: Clear structure, consistent messaging - Improve: Multiple explanation formats, paced delivery options #### Representation - Present: Single perspective from one creator - Improve: Multiple user examples, diverse use cases #### Psychological safety - Present: Encouraging tone about personal adaptation - Improve: Normalize different approaches, reduce judgment ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Clear premise about database structures leading to logical conclusions - Inductive strength: Uses personal experience and traffic analysis as evidence - Causal reasoning: Connects rigid tutorials to user abandonment effectively - Analogical strength: Box metaphor and database comparisons work well #### Fallacies - False dichotomy: Presents only rigid vs flexible options, ignoring middle ground - Hasty generalization: Assumes personal experience applies to all users - Appeal to modernity: Suggests newer (digital) approaches are automatically better #### Tone of voice - Overall tone: Revolutionary, confident, somewhat dismissive of traditional approaches ### 🛡️ DARVO Analysis - Deny: Minimizes legitimate value in structured approaches - Attack: Directly attacks tutorial creators and traditional methods - Reverse victim/offender: Positions rigid tutorials as oppressive rather than helpful - Emotional cues: Uses manifesto format and revolutionary language to create urgency ## 🎯 Conclusion The core insight is liberating: stop trying to perfectly replicate historical note-taking systems and instead focus on the underlying principles of connection and retrieval. Your Zettelkasten should be a flexible graph of linked containers, not a rigid database table. **Next steps**: Audit your current note-taking constraints. Keep only what serves your actual - Document Tags: [[system]] [[methodology]] [[zettelkasten]] - Summary: THE ZETTELKASTEN MANIFESTO | What is a Zettelkasten? - URL: https://www.youtube.com/watch?v=c5Tst3-zcWI a Spectre is haunting academia thespecter of Niklas Luhmann all the powersof the old analog world have enteredinto a holy Alliance to exorcise thespectre professors and researchassistants PhD students andundergraduates software developers and I welcome to the settle caste manifesto[Music]in this video what I'm going to do is exercise the ghost of Niklas Luhmann outof the idea of what etc custom isbecause it tends to confuse people a lotwhen I analyze the traffic that comes tomy page settle calm I realized that alot of traffic is actually going on intotwo pages my two guides on how to usesetter as ascetical I never intendedthese pages to be guides on whatpathetic custom in itself is but more of how to use sector to realize such aconcept of its ethical stance so myintention was to create these pages tohelp those people who have informedthemselves at other places on theinternet about what a telecast is tomake use of that knowledge with my appbut it turns out that a lot ofinformation is not useful at all and soI want to start asking the question why is this information not helpful to manypeople when I first started thinkingabout the opportunity to create my ownset of custom I of course went on Googleand search for tedder custom and foundsome tutorials obviously many of themresiding on the page set a custom pointa which is basically the hub where yougo if you want to learn how thetelecasting works you will probablyalready have found the app tetra custom by Daniel Utica which is supposed toresemble the new tetra custom bynicholas newman as close as possible andmaybe you've just switched into thisvideo and had a lot of question markscircling above your headwhen I first stumbled upon the conceptof telecast I also went into the boobytrap of Niklas Luhmann because I thoughtokay I have to simply completely copythis idea and then it will work but it won't so I had a hard time gettingstarted and for four or five years Ihad nothing resembling etc cousinbecause there were so many constraintsfor instance if you look on the internetthey will always tell you you need an IDyou need text you need related notes youneed outline notes you need meter notesyou need this and that and theinformation on the notes must bestructured in a way that you have firstgeneral summary then some more detailedexplanation and then a bullet point list containing all properties of whateveryou were thinking about and this is notgoing to work because there are so manyconstraints put on you that you willvery soon run into problems generatingyour own notes and this is somethingthat many of the tutorials online simplyneglect they simply see ok NiklasLuhmann did it Sarah Carson and itworked very well for him so our task isto understand how did the specific how did the concrete set a custom byNicholas Newman work and how can werepresent our own quotes and our ownnotes to make use of this specific wayof creating a centre custom forourselves and this is where the problemsstart so let us take a look at NiklasLuhmann channel custom the cell customwas basically a concrete manifestationof what the word sati custom means in English a box with notes so he literallyhad these huge wooden boxes in whichthere were thousands of small pieces ofpaper on which he wrote down somethoughts if we look closely at thesenotes we can see three distinctcomponents that will be important for usin this video the first is a number thatis mostly written on the top of thepaper this is just a number that begins at one and then counts up to the numberof settles inside this box so if thereare 2300 notes in this one box then thefirst ID number would be one and thelast would be 2300 so this was basicallyjust a continuallist of numbers so that nikka's lumencould identify the separate notes thesecond thing that is important here isthe actual content of the note right what he wrote on the notes some thoughtssome quotes references to works ideassomething like this this is the contentof all these notes and then there is thethird element the third element is asequence of numbers also mostly writtenat the top and these numbers referencedother notes inside the set accustomedfor instance if Niklas Luhmannwere to take one note and look at what he's written on these notes and thinkokay this is basically what I've beensearching for and then he sees threenumbers a list of three numbers alsowritten on the note then he knows okaythe notes with these three IDs will alsoin some way relate to what is written onthis one note so he would go look forthem find the for instance threedifferent notes and put all of them next to each other and then he can see allthe contents of the four noteshe now has in front of him and can seeaha I wrote this here and this isanother thought that relates to thefirst one and the third one is not aquote by another author that alsorelates to this is cetera P P and thisis basically the way the Tetra customfor any class movement works what hiscentral cousin actually tried to do wascreate a databasenowadays we have databases everywherefor instance if you are using a citation software it's probably gonna use adatabase Niklas Luhmann did not havesuch a programto do this work for him so he had to doit manually and it's actually amazing ifyou think about that Niklas Luhmannaccidentally use exactly the form thatcontemporary databases on Web Servicesuse nearly all web services nowadaysstore the user information when someoneregisters on this app inside such a relational database soinside the relational databaseinformation is ordered by way of usingtables and you all know tables you haverows and columns and in the first columnnormally in such a table there is an IDof the user in the second there is forinstance a username and the third columnthere is an email in the fourth columnthere is a password and wheneversomebody wants to log in the servicelooks inside this table searches for theemail or the username and compares the password to the one who provided and ifthis matches then you'll be locked intoso this is how relational databases worknormally you have hundreds of tablesinside one of these databases becauselumen had only one and these this tableonly contained three columns the IDcolumn the number on the notes thecontent column where the actual text waswritten and third the column containing a list of all the other notes that thisone peculiar note referenced this workedfine for Niklas Luhmann but imagine whatknowledge looks like imagine what youwould like to write on such a notesometimes you would like to write athought you had sometimes you would liketo write a quote you have from a bookand also at the book as reference so that you always know where you took thequote from and maybe you also want tostore an image because it's because forinstance you're doing ethnographicresearch and when you observe peopleinside a given space you're probably notonly taking notes but also taking photosmaking videos recording sounds I don'tknow there is a lot of data a lot ofarbitrary data that can be createdduring such an ethnographic research but even if you're just a few attrition as Iam you still will have someinconsistencies in the way the data issafe for instance on manyI use text to have some small referenceas to the contents of a file but in somenotes I don't have text at all and whilesome notes feature a header like a short line of text that describes what thecontent of this note is about some donot and while some notes contain areference to a work that I used ingenerating this thought or quote orwhatever I have put in my notes it willcontain this reference work so basicallyyou have the problem that if you try todo this by way of using tables you wouldneed columns to account for each ofthese possibilities if you were to create a separate custom that is able toactually contain a lot of differentinformation a lot of concreteinformation to go back to the abstractconcrete notion again then you willprobably need a lot of columns you willneed a column I deep content relatednotes but you would also need a columnfor references a column for for instancelocation data for images duration for videos a description of what's inside asound if you record a sound etc peopleyou have a lot of different kinds ofinformation and if you were just to taketo use one column called additionalinformation and then you would have inone row in one node you would haveinformation duration column four minutes30 seconds and in another node you would have as additional information somereference to a bookthis might seem fine at first but assoon as you try to automate this processand search for instance only for videoshow would you do this would you alwaysput duration column and then the actualduration of a video or would yousometimes just put the duration of thevideowithout calling it Eurasian Colin and you would very soon get into a lot oftrouble just by structuring the datathis way and therefore don't try to usesuch etc custom but what is the rightapproach if we think again about atetrakis Niklas Luhmann just wanted tostore his information inside a systemthat is able to let him find thesethoughts at a later time so he justwanted to store his information in a way that he can always find it again so butas I said there is a lot of differentproperties that the data you want tostore inside such a telecasting can havebecause at some point you won't want toonly store images to only store text inthem sometimes you will want to storeimages drawings some sketches ofconcepts for instance the Lacanian concepts of the real imaginary insymbolic is always represented in threecirclesI think it's called Borromean knot andso you would like to have this image inthere but you also need a description soand most of your notes don't have anyimages attached to thembut some of them do and you need a wayto store all of them without all thepitfalls that we just discussed and thisis why we have to think of a different concept we now know because lumen usethe kind of relational database but whatyou want to use is a graph database butwhat is a graph database imagine forthis a telecast in a traditional senseright you have notes in them and youhave these ID numbers you have relatenotes numbers and you have the contentso but they're all inside a box now imagine that you luckily as I do have avery small box then simply take thenotes throw them awaywhat you're left with is a small box andnow imagine that you don't use one boxto store all your information in but useone box to store one chunk ofinformation so for instance you have animage you can put it in here you have avideo you can also put it in here yousimply want to quote some lines of text from a book you can also put it here incase of an image you would I don't knowin this analog example you wouldprobably use an USB stick and throw itin there I don't have anyone at at handright now but right I have fun so let'simagine you were about to store an imageso you're just taking your USB key putit in there and it's in here how do youfind it well the first approach to stick with because Newmont would just be totake a piece of paper write an ID on itput it in here together with the imageclose it and put it somewhere and thenbecause we are digital and not analog asyour software your information systemyou would simply search for the ID andthe system would tell you use this boxbecause it's in here so of course thenID is somewhat arbitrary is just anumber that grows over time and to search for information that may berelevant to you forget about the ID manytelecasting approaches will still needthem but you shouldn't care too muchabout them so we still are left backwith our empty box with this USB stickbut instead of an ID what we are goingto take is one piece of paper and wewrite all the text that this image or this video of whatever data you have inthere corresponds to so for instance ifI have an image of the Tetra custom halfin here the internet is full of telecastand images from the costume on so let'sjust say that we have an image of thetelecast not because lumen sowould use the tax lumen check accustomednode image put it in here those talksand put the box someplace and then when I search for tetrakis boom this boxwould also be returned by our system wecould look at the image and make theconnection and hopefully get new ideasso but this is also not the only waybecause for instance let's imagine wehave this image and we have a video forinstance an interview by Niklas Luhmannalso so we have another USB key put itin another box and then we have two boxes and we put the same keys the sametext inside this box so we have thefirst box let's say five texts close itput it back take the next box put in thenext piece of information put the sametext in there put it awayand then we search for for instancelumen and we will both find the one boxwith the image and the other box withthe video or as I said remember you can also have one quote in another quote itdoesn't matter the kind of data isirrelevant here it's just that they arestored in boxes and you have two boxeswith two disparate sets of informationright an image is not the video in theother box just as the quote in the onebox is not like the thought you put intothe other box so but you have these twothings and they turn up in one searchand you think okay these two are related to each other then we come back to theIDE idea of an identifier because youhave the text in here but these areso-called weak linksif you search for these tags these boxeswill come up but so will other boxesthat may not be as closely related asthe two boxes we currently have in ourmind so what you would do is create an ID put it also together with the textinside this boxclose it do the same with the other oneand whenever you search for something inthis one box an end of one box of thesetube comes up but not the other one youcan then put a third piece of paper inhere writing the ID of the other box inhere and then whenever this box turns upinside the search and you think ok thisis relevant you can see a hard there are related boxes you can search for themget the second box it's really bad ifyou just have one box and describesomething with two boxes but anyways Ihope you have an imagination enough andthen you have two boxes and then you canalways pull out the second box as welleven if it did not turn out in youroriginal search and this is basicallywhat a graph database looks like youhave the container and only a limited set of meta information attached to thiscontainer like an ID tags and relatednotes but whatever is thought insidehere is completely irrelevant if it'stext then it will probably also show upin your searches for instance if you doa full-text search on a Teta custom thatis stored in this way you will probablyalso want to have results that had amatch in the full-text but you don't need to you can also store images videossounds whatever you like and with youwill still be able to find them to linkthem to each other and to give IDs tothese boxes and this is basically theconcept of a graph database there is alot more that you can that you can thinkof when thinking of a graph databasesbut thisis the gist of what obstetric arsonactually should be so forget NiklasLuhmann and think about this and then you will have the correct set a customthat works as you do because if you usethe software or any approach thatrequires you to not use and do not onlyuse for instance an idea tags and thisrelationship concept but also a certainway to structure the thoughts it willnot be helpful for you you have to findyour very own approach to what etc custom is and you shouldn't listen toomuch to people trying to tell you okayinside one of your notes you will firstneed a summary then a longer text andthen a list of additional thoughts forinstance you only need an ID links toother notes and text and always when youare starting with your own set of customthink of these boxes think of an unlimited amount of these boxes so forevery new file you create you canimagine this box you put anything inthere and on top of this simply putthese three notes that we talked aboutthe academics disdain to conceal theirviews and names they openly declare thattheir ends can be attained only by theforcible overthrow of all existingtelecasting systems let Niklas Luhmann tremble as an academic revolution theresearchers have nothing to lose buttheir chains they have a world to winresearchers or countries unite[Music], THE ZETTELKASTEN MANIFESTO | What is a Zettelkasten?, YouTube, 01ka7yxnva8c3agna6n8vtsb96.