One thing I love about Zcash dev culture is the norm of people surfacing more clarity about the trade-off frontiers for big decisions as different people bring up or advocate their preferences or concerns. We all learn the trade-off space, we learn what different preferences ppl have. What we could improve on, IMO, is ensuring we document / internalize which desirable trade-off points we've chosen to forego and why, and there's a pragmatic norm for rationalizations including things like "we all agreed the benefits of shipping in a timely manner outweighed the downside risks raised here."

I love how AI has rekindled discussion and interest in my bubble of "consciousness" and "the hard problem". I am largely persuaded by @danieldennett (RIP)'s Consciousness Explained, now known as Illusionism: consciousness is a real, emergent outcome of physical processes, while "qualia" or "the ineffable aspect of experiencing stuff" is fully explainable as functional physical processes. Perhaps those who balk might be interested in distinguishing "fully explainable" (given infinite resources) and "fully explained" (impossible in practice) with me? Now I'm especially intrigued by the connection to "qualia", "ineffable / lived experience", tacit knowledge, scientific modeling theory, and my moral stances around sentience. Sounds like from ChatGPT I should read Dennett's "Welcome to Strong Illusionism", Adam Jenkins's “What Mary Didn’t Know About Tacit Knowledge” (2003), and Michael Polanyi's "The Structure of Consciousness". Anybody wanna start a book club?

How do you strike the balance between improving your lifestyle, processes, tools, workshop, "shipping results", and a meaningful / eudaemonic / The Good Life™️ trajectory? I like to fold the eudamonia stuff into "shipping results", perhaps a geeky/aspie approach. As a FLOSS grey beard, I've always been a yak-shaver: every tech project involves a lot of time thinking about / iterating on my underlying toolchains/infra. Coarsely, it is: self-sovereign hardware -> human-computer executive layer -> project tooling -> "tangible results" goal achievement. (Modern products basically lack the exec layer altogether. Soon to change w/ AI. :robot-winking-emoji: ) AI agents haven't changed the shape of my tech yak-stack at all! My leaning edge in AI is figuring out how to redistribute my effort on yak-stack frontier progress. Tangents: my "hardware" layer needs better bio integration, and all layers need better social integration. Any SF workout / diet buddies interested? Ping me!

Introducing an independent organization providing Zcash blockchain integrations and support, infrastructure services, and adoption-focused grants.

Analyze Zcash wallet fingerprints, fee lane anonymity sets, and estimated wallet usage. See how transaction fees, expiry heights, and action padding reveal wallet identity.

Zakura is a new Zcash full node, and its first release is out.

Sovright builds the infrastructure that preserves our right to choose: who sees your data, who controls your money, and how you exist online. It began with Zcash. It doesn't end there.

ALT: a cartoon character is holding a newspaper that says " old man yells at cloud "

Search and browse the full Cypherpunk Library: every manifesto, essay, and treatise on the shelf, by format.

I am SO on board for the "local first, e2e encrypted, cloneware" that is cannibalizing old-school "web2 all your data are belong to us". logseq > roamresearch, AnyType > notion, etc... What other apps are in this category? So much of Web2 is just a UI over a database with small world user interactions. Local first, encrypted, sync'd db tech is proliferating. Love it! Instead of paying by sacrificing your privacy to the adtech panopticon, pay subscription for good UX & data sovereignty.

Loving @shieldedmark.bsky.social 's office hours which are covering intro / intermediate study sessions for the dev community. Starting now: multi-session overview of the Zcash protocol spec! Zcash Discord, jump in! @thedrekal is sharing their developer training initiative: 6 week Zcash hacker school from protocol to building product prototypes. Longer term: multi-class platform. 🔥🛡️🔥 https://forum.zcashcommunity.com/t/protocol-study-series-12-session-guided-reading-of-the-zcash-protocol-specification-starting-april-21/55350

Build Status Tests on GitHub CI Version Documentation License dependency status Minimum Supported Rust Version Miri Changelog

Agent Orchestration I will alpha test, subscribe to, or angel invest in: It's a task list / todo manager that provides me with prioritization / planning UX (maaaybe with some AI augmentation as long as I can have thorough control). Then there's an "active backlog". Agents show up, do work stealing (or more likely tasks are distributed according to pre-existing context in agents which specialize over tasks). There's an inbox of task results showing the original task and a report of the accomplishment or blockers. I review and sign off or request changes. (My brain prefers requested changes to be a new linked task for reasons I could explain elsewhere.) The granularity / scope needs to be chunky enough to be worth my own brain's ~1-10 minute context switch time for serious projects. Compartmentalization: the only write access the agent should have is an append-only revision log. The task report is a capstone revision describing the rest, from a starting context state.

Okay, fine, you crazy kids, instead of getting off my lawn, just explain to me how you orchestrate more than ~2 agents? One claude does like 5-30 seconds of work then blocks on a prompt from me. Two claudes makes that worse plus my machine starts bogging down. The real killer is the prompt. It takes like ~10+ minutes for me to successfully context switch my brain from any focused effort, so ~30s prompts for a 1-10s churn in my brain to respond is waaaaay not worth it.