Author of design brief: Nick Gerakines (CTO, Graze Social; founder, Smoke Signal & Lexicon Garden; author, AIP OAuth server; AT Protocol Community Fund member).
Target home: tangled.org/ngerakines.me/atproto-crates, as a new crate atproto-pds.
Date: May 1, 2026 (revision 2).
Architectural North Star: A low-latency, highly-performant Rust PDS that is fully conformant to the existing reference implementations and is architected from day zero to support permissioned data spaces as a first-class concern, grounded in the concrete design laid out in bluesky-social/atproto/docs/superpowers/specs/2026-04-22-permissioned-data-pds-design.md (Daniel Holmgren's PDS implementation design, hereafter "the Spaces Design Spec"). The Spaces Design Spec supersedes the earlier Permissioned Data Diary blog posts as the authoritative source for protocol mechanics; the diary is retained only as conceptual backgr
Discover gists
In order for the LXC container to have full access the proxmox host directory, a subgid is set as owner of a host directory, and an ACL is used to ensure permissions.
Add the following line to /etc/pve/lxc/<CT_ID>.conf
mp0:/mount/point/on/host,mp=/mount/point/on/lxc
In the default Proxmox configuration, unpriviliged container subgids will have the prefix "10" followed by the expected 4-digit gid.
| Filter | Description | Example |
|---|---|---|
| allintext | Searches for occurrences of all the keywords given. | allintext:"keyword" |
| intext | Searches for the occurrences of keywords all at once or one at a time. | intext:"keyword" |
| inurl | Searches for a URL matching one of the keywords. | inurl:"keyword" |
| allinurl | Searches for a URL matching all the keywords in the query. | allinurl:"keyword" |
| intitle | Searches for occurrences of keywords in title all or one. | intitle:"keyword" |
Tutti i comandi che iniziano per % sono eseguiti sul mio mac. Quelli con $ sono eseguiti sul server remoto come utente (ubuntu). Quelli con # sono eseguiti come root... a me piace poco sudo.
Per maggiori info riguardo il Free Tier: https://docs.oracle.com/en-us/iaas/Content/FreeTier/freetier_topic-Always_Free_Resources.htm
| #!/bin/bash | |
| # | |
| # Instructions | |
| # ------------ | |
| # do the following on every node of your cluster | |
| # - save this script to /etc/pbs_up-down.sh | |
| # - chmod 755 /etc/pbs_up-down.sh | |
| # - add the following line to /etc/vzdump.conf on (without the #) | |
| # script: /etc/pbs_up-down.sh | |
| # - set up ssh key authentication from the root@PVE and root@PBS |
| diff --git a/iina/MainWindowController.swift b/iina/MainWindowController.swift | |
| index be3048e..0cda168 100644 | |
| --- a/iina/MainWindowController.swift | |
| +++ b/iina/MainWindowController.swift | |
| @@ -2740,6 +2740,7 @@ class MainWindowController: PlayerWindowController { | |
| override func updatePlayTime(withDuration duration: Bool, andProgressBar: Bool) { | |
| super.updatePlayTime(withDuration: duration, andProgressBar: andProgressBar) | |
| + syncPIPPlaybackState() | |
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.
| class Meeting extends EventEmitter { | |
| ... | |
| constructor(...) { | |
| super(); | |
| ... | |
| } | |
| // STEP->3 | |
| // Create Meeting in MediaNode |