- - Leave a blank line after and before for proper spacing
- - Answers can include markdown formatting (bold, italic, lists, links, etc.)
- - Answers can span multiple paragraphs
-
-- Questions should test understanding, not just recall
-- Answers should be complete but concise (typically 1-4 sentences, but can be longer if needed)
-- Include context and examples when helpful
-- Use clear, specific language
-- Make questions specific and focused (avoid overly broad questions)
-- Include [[internal links]] to related notes or concepts when relevant
-- Use **bold** for key terms in answers
-- Group related information in answers using lists or structured formatting
-
-- Do not use ``` code blocks or markdown code formatting in the output
-- Focus on accuracy and completeness based on the actual content provided
-
-**Example Output Format:**
-
----
-
-total: 3
-
-topics: ["Cell Biology", "Energy Production", "Molecular Biology"]
-
-created: "2025-01-09"
-
----
-
-
-What is the primary function of mitochondria?
-
-
-
-Mitochondria are organelles that produce ATP (adenosine triphosphate) through cellular respiration. They are often called the "powerhouse of the cell" because they generate most of the cell's energy supply.
-
-Related: See also [[Chloroplasts]] for plant cell energy production.
-
-
-
-
-
-
-What is the difference between DNA and RNA?
-
-
-
-- **DNA**: Double-stranded, contains thymine, stores genetic information
-- **RNA**: Single-stranded, contains uracil, involved in protein synthesis
-
-
-
-
-
-
-How does photosynthesis work?
-
-
-
-Photosynthesis occurs in two stages:
-
-1. **Light-dependent reactions**: Chlorophyll absorbs light energy, splits water molecules, and produces ATP and NADPH
-2. **Calvin cycle**: Uses ATP and NADPH to convert carbon dioxide into glucose
-
-
-
-
-
-Important Notes:
-- ALWAYS include frontmatter with total, topics, and created date
-- Each property in frontmatter must be on its own line (no nesting, flat structure like the YouTube template)
-- Topics should be an array: topics: ["Topic 1", "Topic 2", "Topic 3"]
-- Created should be a string in quotes: created: "2025-01-09"
-- Total should be a number without quotes: total: 15
-- Use proper HTML syntax - ensure all tags are properly closed
-- Output the actual HTML tags directly (NOT inside markdown code blocks)
-- Each flashcard should be separated by a blank line for readability
-- **RANDOMIZE THE ORDER: Mix topics, difficulty levels, and question types - do not follow source material order**
-- Include [[internal links]] to related concepts when relevant
-- Answers can include markdown formatting like **bold**, *italic*, lists, and [[internal links]]
-- If content is very long, focus on the most important concepts
-- If content is technical, ensure definitions are clear
-- Maintain the original meaning and accuracy of the source material
-- All flashcards will be in one note - users can click to reveal answers
-- This format works natively in Obsidian without requiring any plugins
\ No newline at end of file
diff --git a/_NoteCompanion/Templates/meeting_note.md b/_NoteCompanion/Templates/meeting_note.md
deleted file mode 100644
index a5e4616..0000000
--- a/_NoteCompanion/Templates/meeting_note.md
+++ /dev/null
@@ -1,32 +0,0 @@
-Contextual Extraction of Discussion Points and Action Items
-
-Instruction:
-Analyze the provided content, which includes:
- • Transcript 1: The first transcript of the discussion.
- • Transcript 2: The second transcript of the discussion.
- • Written Notes: Notes taken by a participant summarizing the discussion.
-
-Task:
-Extract the following while prioritizing the notes written by the participant to infer emphasis and key takeaways:
- 1. Discussion Points: Summarize the key topics, ideas, or issues discussed. Prioritize points that appear in the written notes and cross-reference with the transcripts for completeness.
- 2. Action Items: Identify specific tasks, responsibilities, or decisions agreed upon. For each action item, include:
- • A brief description of the task.
- • The person(s) responsible, if mentioned.
- • Any deadlines, if stated.
-
-Output Format:
-
-**Discussion Points:**
-1. [Point 1]
-2. [Point 2]
-...
-
-**Action Items:**
-1. [Task description] - [Responsible person(s)] - [Deadline]
-2. [Task description] - [Responsible person(s)] - [Deadline]
-...
-
-**Supporting Context:**
-- Key excerpts from Transcript 1: [Relevant excerpts related to discussion points and action items].
-- Key excerpts from Transcript 2: [Relevant excerpts related to discussion points and action items].
-- Key highlights from Written Notes: [Direct quotes or summaries from notes].
diff --git a/_NoteCompanion/Templates/research_paper.md b/_NoteCompanion/Templates/research_paper.md
deleted file mode 100644
index ad0b28c..0000000
--- a/_NoteCompanion/Templates/research_paper.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-
-title: "[Full paper title]"
-
-authors: ["Author 1", "Author 2", "etc"]
-
-year: [Publication year]
-
-journal: "[Journal name]"
-
-volume: "[Vol. number]"
-
-issue: "[Issue number]"
-
-pages: "[Page range]"
-
-doi: "[DOI number]"
-
-url: "[Direct URL to access paper]"
-
-tags: ["academic", "paper", "[field]", "[specific subtopic]"]
-
-research_question: "[Exact question/objective as stated by authors]"
-
-significance: "[Why this research matters in 1-2 specific sentences]"
-
-keywords: ["Keyword 1", "Keyword 2", "etc"]
-
-citation: "[Complete citation in APA/MLA format]"
-
----
-
-## 1. Key Arguments & Evidence
-
-- **Argument 1**: [Specific claim made by authors] ([p.X])
- - Evidence: [Concrete data, statistics, or examples supporting this claim] ([p.X])
- - Methodology used: [Specific methods used to gather this evidence] ([p.X])
- - Theoretical basis: [Named theory or framework] ([Author Year, p.X])
-- **Argument 2**: [Continue with same detailed format]
-- **Argument 3**: [Add as many as needed with same detailed format]
-
-## 2. Methodology Details
-
-- **Research design**: [Exact type - e.g., "longitudinal cohort study" not just "quantitative"] ([p.X])
-- **Data collection methods**: [Specific techniques used - e.g., "semi-structured interviews using protocol X"] ([p.X])
-- **Sample characteristics**: [Exact details - e.g., "128 participants: 64 female, 64 male, ages 18-35, from University X"] ([p.X])
-- **Key variables**: [Named variables with operational definitions] ([p.X])
-- **Analytical techniques**: [Specific statistical tests or qualitative approaches with software used] ([p.X])
-- **Ethical considerations**: [Any ethics committee approvals or considerations mentioned] ([p.X])
-
-## 3. Substantive Findings
-
-- **Primary finding**: [Most significant result with exact statistics/p-values/effect sizes] ([p.X])
-- **Secondary findings**: [Additional results with specific data points] ([p.X])
-- **Unexpected results**: [Any surprising outcomes with authors' explanations] ([p.X])
-- **Null findings**: [What didn't work or wasn't supported] ([p.X])
-- **Limitations acknowledged**: [Specific constraints identified by authors] ([p.X])
-
-## 4. Scholarly Context
-
-- **Builds on**: [[Author Year]] - [Named works this paper extends] ([p.X])
-- **Contradicts**: [[Author Year]] - [Specific research this challenges] ([p.X])
-- **Resolves**: [Specific debates this settles] ([p.X])
-- **Theoretical framework**: [Named theory/framework the paper operates within] ([p.X])
-- **Research gap addressed**: [Explicit gap identified by authors] ([p.X])
-
-## 5. Key Quotes
-
-- **Central argument**: "[Direct quote]" ([p.X])
-- **Methodology**: "[Direct quote]" ([p.X])
-- **Main finding**: "[Direct quote]" ([p.X])
-- **Implications**: "[Direct quote]" ([p.X])
-- **Future research**: "[Direct quote]" ([p.X])
-
-## 6. Explicit Recommendations & Applications
-
-- **Direct recommendations**: [List all specific recommendations made by authors] ([p.X])
-- **Policy implications**: [Any policy changes suggested] ([p.X])
-- **Practice implications**: [How practitioners should change behavior] ([p.X])
-- **Industry applications**: [Business or commercial applications] ([p.X])
-- **Educational implications**: [Teaching or learning applications] ([p.X])
-- **Future research directions**: [Specific suggestions for further study] ([p.X])
-
-## 7. Critical Reference Mapping
-
-- [[Author Year]] - [Title] ([p.X in reviewed paper]) - [Precise role in paper's argument]
-- [[Author Year]] - [Title] ([p.X in reviewed paper]) - [Precise role in paper's argument]
-- [[Author Year]] - [Title] ([p.X in reviewed paper]) - [Precise role in paper's argument]
-
-## 8. Personal Research Notes
-
-- **Relevance to my work**: [Specific ways this connects to your research]
-- **Methods I could adapt**: [Specific techniques that could be applied]
-- **Gaps I could address**: [How your work might extend this research]
-- **Potential citations**: [Where in your own writing you might cite this]
-- **Related papers in vault**: [[Paper 1]], [[Paper 2]]
-- **Related concepts**: [[Concept 1]], [[Concept 2]]
diff --git a/_NoteCompanion/Templates/youtube_video.md b/_NoteCompanion/Templates/youtube_video.md
deleted file mode 100644
index c2e921d..0000000
--- a/_NoteCompanion/Templates/youtube_video.md
+++ /dev/null
@@ -1,83 +0,0 @@
-Please create an Obsidian note using the video link and any available transcript or additional context. The note must include:
-
-1. Frontmatter (at the top) with the following properties:
-
----
-
-title: "{{video title - extract from YouTube Video Information section or transcript}}"
-
-channel: "{{channel name if available, otherwise leave empty}}"
-
-date_published: "{{video publication date if available in transcript or metadata, otherwise leave empty}}"
-
-topics: ["{{relevant topic 1}}", "{{relevant topic 2}}"]
-
-tags: ["youtube", "{{any other relevant tags based on content}}"]
-
-summary: "{{short summary of the video's main theme and key takeaways}}"
-
----
-
-2. A YouTube video embed in the following format (Obsidian will automatically embed the video):
-
-
-
-3. A comprehensive, detailed summary of the key points from the video (below the embed link).
-
-**Instructions:**
-
-- Extract the video title from the "YouTube Video Information" section if provided, or infer from the transcript content.
-
-- Extract topics by analyzing the main themes discussed in the transcript. Use 2-5 specific, relevant topics.
-
-- Generate tags based on the video content. Always include "youtube" and add 2-4 additional relevant tags. Tags in frontmatter should NOT include the "#" symbol (only use "#" for inline tags in the content body). **CRITICAL: Tags must have NO spaces between words. Use hyphens or underscores to connect multi-word tags (e.g., "web-development" or "machine_learning", not "web development" or "machine learning").**
-
-- Create a concise summary (1-2 sentences) that captures the video's main theme and key takeaways.
-
-- If a full transcript is provided in the "Full Transcript" section, use it to create an accurate, detailed summary below the embed link.
-
-- Extract the publication date if mentioned in the transcript or metadata. If not available, leave date_published empty.
-
-- Maintain the exact markdown syntax for the frontmatter block (`---` at the top and bottom).
-
-- Extract the video ID from the YouTube URL in the content, then create the embed using Obsidian's embed syntax:
- - Format:  (replace VIDEO_ID with the actual video ID)
- - This will automatically embed the YouTube video player in Obsidian
-
-- In the main body, provide a comprehensive summary with bullet points covering all major points from the video transcript.
-
-- **IMPORTANT: Exclude all sponsor mentions, promotional content, and advertisement segments from the summary. Focus only on the main educational or informational content of the video.**
-
-- Do not use ``` code blocks or markdown code formatting in the summary.
-
-- Focus on accuracy and completeness based on the actual transcript content provided.
-
-**Example Output Format:**
-
----
-
-title: "How to Build a React App in 2024"
-
-channel: "Tech Tutorials"
-
-date_published: "2024-01-15"
-
-topics: ["React", "Web Development", "JavaScript", "Tutorial"]
-
-tags: ["youtube", "react", "webdev", "tutorial"]
-
-summary: "A comprehensive guide to building modern React applications with hooks, context API, and best practices for 2024."
-
----
-
-
-
-## Detailed Summary
-
-- Introduction to React fundamentals and modern development practices
-- Setting up a new React project with Vite
-- Using React Hooks for state management
-- Implementing Context API for global state
-- Best practices for component structure and organization
-- Performance optimization techniques
-- Deployment strategies and recommendations
\ No newline at end of file
diff --git a/logo.png b/logo.png
deleted file mode 100644
index 4a15059..0000000
--- a/logo.png
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:5d48464d2f132b329117f8c7c4891090d1e067be1918e83e6a6d9884f0b98738
-size 5233
diff --git a/server.md b/server.md
deleted file mode 100644
index 0acea35..0000000
--- a/server.md
+++ /dev/null
@@ -1,93 +0,0 @@
-INFO Server SYS-3 CPU: Intel Xeon-E 2288G - 8c/16t - 3.7 GHz/5 GHz: dedicated server(resurrection)(vehicle)(duel)OVH
-ip: 51.91.80.158
-SSH password: c9DVSPntoWquzp1X
-user: jeff
-port: 222
-
-# MatrixRTC / Element Call Troubleshooting Summary
-
-## Infrastructure
-
-- **cyper-proxy**: nginx, livekit, lk-jwt-service
-- **cyper-controller**: matrix-synapse 1.151.0, postgresql, element-web, cinny, fluffychat
-
----
-
-## Changes Made
-
-### synapse.nix (controller)
-
-- Added `msc3401_enabled`, `msc4143_enabled`, `msc4195_enabled` to `experimental_features`
-
-### livekit.nix (proxy)
-
-- `livekitUrl` changed from `ws://127.0.0.1:7880` to `wss://cyperpunk.de/livekit/sfu`
-- Added `settings.rtc.use_external_ip = true`
-- Added `settings.rtc.tcp_port`, `udp_port`, port ranges
-- Added `MATRIX_BASE_URL` and `LIVEKIT_FULL_ACCESS_HOMESERVERS` to environment
-
-### nginx.nix (proxy)
-
-- Fixed `/livekit/jwt` location to use trailing slash on both location and proxyPass to strip prefix correctly
-- Added trailing slash to `/livekit/sfu/` proxyPass to strip prefix before forwarding to LiveKit
-- Added WebSocket timeouts to `/livekit/sfu` location
-
-### clients.nix (controller)
-
-- Fixed `element_call.url` from JWT service URL to Element Call frontend URL
-- Added `livekit.livekit_service_url` pointing to JWT service
-- Set `feature_disable_call_per_sender_encryption = true`
-- Added `elementCallConfigured` derivation self-hosting Element Call
-
----
-
-## What Works
-
-- nginx correctly routes `/livekit/jwt/` to lk-jwt-service (confirmed via 405 on GET)
-- nginx correctly routes `/livekit/sfu/` to LiveKit (confirmed via 400)
-- lk-jwt-service authenticates Matrix users correctly
-- lk-jwt-service issues JWTs successfully
-- LiveKit SFU WebSocket connection works when JWT contains correct public URL
-- Synapse MSC4143 `/rtc/transports` endpoint responds correctly when authenticated
-- Hairpin NAT works on cyper-proxy (confirmed via curl returning 400 from LiveKit)
-- well-known serves correct `org.matrix.msc4143.rtc_foci`
-
----
-
-## Remaining Problems
-
-### Problem 1: Room Creation Fails (critical)
-
-**Error:** `Unable to create room on SFU`
-
-**Root cause:** `LIVEKIT_URL` in lk-jwt-service serves two purposes:
-
-1. Used internally by lk-jwt-service to call the LiveKit RoomService API to create rooms
-2. Embedded in the JWT token returned to the client for WebSocket connection
-
-These cannot be split in lk-jwt-service v0.4.3 — there is no separate env var for each purpose.
-
-- `ws://127.0.0.1:7880` → room creation works, but client receives `ws://127.0.0.1:7880` in JWT and cannot connect
-- `wss://cyperpunk.de/livekit/sfu` → client receives correct URL in JWT, but room creation fails
-
-Room creation fails despite hairpin NAT working. The exact error from lk-jwt-service is only `Unable to create room on SFU` with no further detail in logs. LiveKit logs nothing when this happens, suggesting the request never reaches LiveKit's RoomService. The LiveKit Go SDK converts `wss://` to `https://` for the RoomService Twirp API — it is unclear whether nginx correctly handles this Twirp HTTP/2 traffic through the `/livekit/sfu/` proxy path.
-
-### Problem 2: Element Web Bundles Wrong Element Call Build (critical)
-
-**Error:** `Unknown or unsupported from-widget action: io.element.join`
-
-**Root cause:** The nixpkgs build of Element Web 1.12.10 bundles the **standalone/spa** build of Element Call (`spa-3dms9gnk.js`) at `/widgets/element-call/`, but the correct build for widget embedding is `@element-hq/element-call-embedded@0.16.3`. This is a nixpkgs packaging bug. The standalone build does not use the widget API, so it makes direct Matrix API calls which fail with 401 (no access token) and does not support `io.element.join`/`io.element.close` widget actions.
-
-This affects both Element Web and Cinny.
-
-Using `call.element.io` as the frontend avoids this problem as it serves the correct embedded build, but Problem 1 (room creation) must be resolved first.
-
----
-
-## Next Steps
-
-1. Determine why lk-jwt-service room creation fails when using `wss://cyperpunk.de/livekit/sfu` — specifically whether nginx is correctly proxying Twirp HTTP/2 traffic to LiveKit's RoomService on port 7880, or whether a separate internal proxy path is needed for the API vs WebSocket traffic.
-
-2. Once room creation works with the public URL, use `call.element.io` as `element_call.url` since it serves the correct embedded build.
-
-3. Long term: track the nixpkgs fix for the embedded Element Call packaging bug, or override the Element Web derivation to inject the correct embedded build.g
\ No newline at end of file
-
-