Your ultimate resource for macOS Office installers, serializers, and troubleshooting.
Discover gists
| import { Controller } from "@hotwired/stimulus" | |
| import PullToRefresh from "pulltorefreshjs" | |
| /* | |
| * Add data-controller="pull-to-refresh" to the element you want to be pulled on. | |
| */ | |
| export default class extends Controller { | |
| connect() { | |
| PullToRefresh.init({ | |
| mainElement: this.element, |
A pattern for building personal knowledge bases using LLMs. Extended with lessons from building agentmemory 20K+ Stars ⭐️, 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.
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.
The initial source comes from sdcuike/issueBlog#4
https://github.com/PacktPublishing free to download books code by Packet
https://github.com/EbookFoundation/free-programming-books Very immense
If you're a React Native or Expo developer, you've probably experienced this frustration: you just want to test your app on an Android emulator, but every guide tells you to install the massive Android Studio IDE. Suddenly you're downloading gigabytes of tools you'll never use, your shell is polluted with Java paths and Android environment variables, and your pristine development setup feels bloated.
You don't want to become an Android developer. You just want to see your cross-platform app running on an Android device.
Maybe you're like me:
- You use Expo with EAS Build for all your native builds
WSA or Windows Subsystem for Android is a Tool that allows Windows to run Android Apps directly without using any emulator. The problem is Windows Subsystem for Android is currently only available through preview via the Beta Channel of the Windows Insider Program. But if you follow this guide, you don't have to be in Windows Insider Program to try it out. The only thing you need is Windows 11 installed and some patience.
- A Device with any version and Edition of Windows 11 installed.
- Internet Connection.
- Hyper-V enabled.
| name | vinted-listings |
|---|---|
| description | Create Vinted listings from item photos, or audit and improve existing listings. Use for Vinted selling workflows involving photo grouping, accurate listing copy, retail-price checks, uploads, and saved-listing verification. |
Turn the user's photos and item facts into accurate, searchable Vinted listings, and carry authorized changes through to verified saved results. Use the current browser-control tool and its documentation; prefer an available dedicated integration if it actually supports the task.
References:
- obsproject/obs-studio#12650
- https://obsproject.com/forum/threads/obs-version-32-0-0-removed-disable-shutdown-check.190590/
For Windows users looking to workaround this change, here's my setup consisting of two Task Scheduler tasks.
