thedavidyoungblood

Stopping Spam Calendar Invites

Prevention, Removal, Filtering, and Administrative Controls

Document type: Wiki / Quick Reference Guide Audience: End users, help-desk personnel, messaging administrators, and security teams Applies to: Google Calendar, Google Workspace, Outlook, Microsoft 365, Exchange Online, Apple Calendar, and iCloud Calendar Last reviewed: August 4, 2026

---

thedavidyoungblood

Here's the schema — a single universal rubric you can apply to score any local-AI candidate (a GPU, a model, a serving framework, a deployment) against the same structural skeleton, so every comparison in this whole conversation collapses into one repeatable due-diligence instrument rather than nine separate narratives.

---

How to Read This Schema

Each row follows the pattern Feature :: Function :: Spec/Metric :: Value(Range/Band/Qty) :: Similar/Related/Other. "Feature" is the atomic attribute being measured (it should not overlap with any other row — that's the MECE discipline). "Function" is what that attribute actually does for you operationally. "Spec/Metric" is the measurable unit. "Value" is the realistic 2026 band, not a single number, since real hardware/software spans a range. "Similar/Related/Other" cross-links the attribute to adjacent decisions so you see what it trades off against. This mirrors the discipline used in vendor-neutral edge-AI scoring: define criteria once, weight them p

thedavidyoungblood

unsorry — containerized cross-platform dev environment (PoC artifacts)

Proof-of-concept for a proposal to agenticsnz/unsorry: an additive, reproducible dev container that mirrors the environment Gate A trusts in CI (Ubuntu + elan-pinned Lean + mathlib binary cache + Python + gh). Docker-first, runs unchanged under Podman.

These files are validated end-to-end (build + Gate A --wfail + Gate B + agent.sh --self-test 67/67) on Podman/WSL2. They are shared here for inspection — happy to open a proper PR on request. Additive DevX only: no change to Gate A, Gate B, the claims substrate, AISP records, or agent behaviour. The image bakes in no repository sources and no secrets.

thedavidyoungblood

Sharing a short write-up in case it is useful:

[!TLDR] explores using PreToolUse hook function(s) as interim mitigation for ISSUE: #3024 (and related).

LINK-TO-GIST

Note

It includes:

• an expanded issue-commentary

thedavidyoungblood

[!Note from the researcher]

What's this all about?

I was curious in flow, and just felt like exploring what a more unified, DevEx oriented approach could look like to a UV/BUN like system would be for rust and came across this rx project, so decided to one-shot some opinionated constraints to explore what creating anew, and/or enhancing what is, as borrowed from other well done projects for comparative analysis, and exploration.

---

What's WINNING look like?

thedavidyoungblood

RCS General Research - Privacy & Security

---

[TLDR]: "Do Your Own Due Diligence!"(DYODD)

Ultimately, compared to all of the other available options today, this is one of the most proprietary, restrictive, yet, exposed, and in vulnerable ways, where we trade 'features' and 'functionalities', for our privacy, and data-sovereignty. Find and use something else. Almost anything will do. (Relative to where you're located globally, of course.)

thedavidyoungblood

The Complete OSS Contribution Framework

A decision-ready system for contributing to open source without burning bridges

---

---

thedavidyoungblood

Resolving python3 errors on Windows 11 (Claude Code + other CLI agents)

Goal: Make python3 resolve to a real interpreter across PowerShell, cmd, Git Bash, and other shells used by agent tooling on Windows 11, without requiring WSL.

Common symptom: python3 --version → “Python was not found; run without arguments to install from the Microsoft Store…”

Root cause (often): Windows “App execution aliases” stub python3.exe in ...\WindowsApps shadows the real Python.

thedavidyoungblood

ADR (Architecture Decision Record) — Documentation Pattern

ATTRIBUTION: thanks to Martin Cleaver https://github.com/mrjcleaver and the Agentics-Foundation https://agentics.org/ -- I took chat notes, and restructured for future reference below.

A lightweight, durable way to capture why an architectural decision was made (not just what was built), so teams can revisit decisions with context instead of re-litigating from scratch.

Tip

ADR = one decision, one file. Keep it durable, searchable, and easy to supersede.

---

thedavidyoungblood

Search for articles...

What's New

Model selection

Installing Claude in Chrome

Permissions required to install Claude in Chrome