| Name | Description |
|---|---|
| itch.io | Free & paid assets |
| OpenGameArt.org | Free assets |
| Kenney | CC0 assets |
| /r/gameassets | Free assets |
| Name | Type | Description | License |
| Name | Description |
|---|---|
| itch.io | Free & paid assets |
| OpenGameArt.org | Free assets |
| Kenney | CC0 assets |
| /r/gameassets | Free assets |
| Name | Type | Description | License |
below is a security analysis done by clause code. reference https://x.com/adibhanna/status/2046988777789555191 repo: https://github.com/ritualPlay-Net/RitualPlay/ the scammer: https://www.linkedin.com/in/dean-gallimore-440669234/ his email: [email protected] NOTE: if you decide to clone this repo, do NOT run npm install, or try to run it. it has a backdoor
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.
I have looked around online and noticed a lot of users that moved to Niri come from KDE, or were using Dolphin on their previous WM/DE and want to use it on Niri. The problem is that unlike Nautilus, the Dolphin experience on Niri is not out of the box, it has a lot of issues. 90% of the time you open Dolphin the first time it doesn't work properly and it looks horrible. So I try to write this to stealgather all the fixes that I have found and turn it into a guide for newcomers to make Dolphin functions as close as it was on KDE.
This guide focuses on Vanilla Niri. I personally don't use any plugin or theming shell so I don't know exactly how they work.
At the time I'm writing this I'm thinking of upload it into a gist or something at some point, to make it easier to update things and to access/download. Edit: gist
A pattern for building personal knowledge bases using LLMs. Extended with lessons from building agentmemory, a persistent memory engine for AI coding agents.
This builds on Andrej Karpathy's original LLM Wiki idea file. Everything in the original still applies. This document adds what we learned running the pattern in production: what breaks at scale, what's missing, and what separates a wiki that stays useful from one that rots.
The core insight is correct: stop re-deriving, start compiling. RAG retrieves and forgets. A wiki accumulates and compounds. The three-layer architecture (raw sources, wiki, schema) works. The operations (ingest, query, lint) cover the basics. If you haven't read the original, start there.
0x8545: Original 84 -> 850x08FF19: Original 75 -> EB0x1932C7: Original 75 -> 74 (remove UNREGISTERED in title bar, so no need to use a license)