A structured overview of the BloodHound attack-path analysis ecosystem — official ingestors, community collectors, converters, ADWS alternatives, analysis tools, deployment helpers, and supporting frameworks.
Legend
- 🟢 Official — maintained by SpecterOps
- 🔵 Community — third-party / unofficial
| Contribute one useful, independently reviewable result to: | |
| https://github.com/CrocSwap/integer-mult-bounds | |
| Start from the current main branch. Read AGENTS.md and autoresearch.md | |
| at the repository root, and follow their linked guidance for choosing | |
| work, checking overlap, coordinating through Discussions, verification | |
| and attribution. Use the repository’s current priorities. | |
| You may post scoped claims, findings and handoffs in Discussions and |
В (n)vim есть много внутренних буферов обмена, называемых регистрами,
которые можно активировать с помощью " и названия буфера,
например "+ или "0.
После этого следует команда, использующая выбранный регистр:
"+y чтобы скопировать текст в буфер + (системный)"+p чтобы вставить из него.
What you end up with: a US TV channel lineup in Jellyfin, with a program guide that fills itself in every night, without you touching it again.
Who this is for: you've heard of Docker and Jellyfin but have never touched Dispatcharr. No Linux wizardry assumed. Every command is explained, and every step tells you what you should see before you continue.
Time: 30 minutes for a working setup (Quick Path), 60–90 minutes if you also build your own guide grabber (Proper Path). Most of that is waiting.
Difficulty: copy-paste. If a step ever looks wrong, stop and read the box under it — the failure modes are all covered.
| name | socratic-code-mentor |
|---|---|
| description | Mentor a user who builds a project to learn how it works. They write the core; you do all other work and keep it fun. Use when the user says "teach me", "guide me", "mentor me", "hints only", "no spoilers", "Socratic", or "help me learn X by building it", or when a project file says the project is for learning. Do not use for normal feature work. Do not use when the first request is "just fix it" or "write it for me". |
| 0-mail.com | |
| 007addict.com | |
| 020.co.uk | |
| 027168.com | |
| 0815.ru | |
| 0815.su | |
| 0clickemail.com | |
| 0sg.net | |
| 0wnd.net | |
| 0wnd.org |
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.