possibilities

Make Notifications Non-Blocking (Fire and Forget)

Problem

Several notification calls block execution until dismissed. Notifications should always be fire-and-forget.

Current State

• common/notifications.py - Central module using subprocess.run() (blocking)
• run_sync_topics.py - Has its own _send_notification() function (blocking, duplicated code)

possibilities

Make Notification Calls Non-Blocking

Problem

Several notification calls in the codebase use subprocess.run(), which blocks execution until the notification is dismissed. This slows down scripts and hook execution unnecessarily.

Current State

Location	Method	Blocking	Notes

possibilities

Plan: Remove rsnapshot completely

Summary

Remove all rsnapshot-related files, configs, scripts, and references from the dotfiles repo and system.

Files to Delete

Directories

• rsnapshot/ - entire directory

possibilities

Plan: Remove rsnapshot completely

Summary

Remove all rsnapshot-related files, configs, scripts, and references from the dotfiles repo and system.

Files to Delete

Directories

• rsnapshot/ - entire directory

possibilities

Plan: Write a Short Poem

Task

Write a short poem from the heart.

Approach

Compose a brief, sincere poem reflecting on something meaningful - perhaps the nature of connection, the passing of moments, or the quiet wonder found in simple things.

The Poem

possibilities

Plan: Write a Short Poem

Goal

Write a short, heartfelt poem.

The Poem

The cursor blinks in silence,
waiting for the words to come.

possibilities

Plan: Make scrapectl resilient to stale containers

Problem

When a browser container (scrapectl-browser) is stopped but not deleted, subsequent scrapectl fetch-markdown calls fail with:

Error starting container: Error: exists: "container with id scrapectl-browser already exists"

possibilities

Plan: Make sync-links Fail Immediately on Any Failure

Context

The user fixed tweet scraping issues that appeared as 404s. Now they want sync-links to fail immediately when any failure occurs, rather than continuing and masking errors.

Current Behavior

The sync-links command in /Users/mike/code/links/scripts/bin/linkctl (lines 234-577) has inconsistent error handling:

possibilities

Plan: Make sync-links Fail Immediately on Any Failure

Context

The user fixed tweet scraping issues that appeared as 404s. Now they want sync-links to fail immediately when any failure occurs, rather than continuing and masking errors.

Current Behavior

The sync-links command in /Users/mike/code/links/scripts/bin/linkctl (lines 234-577) has inconsistent error handling:

possibilities

Plan: Make sync-links Fail Immediately on Any Failure

Context

The user fixed tweet scraping issues that appeared as 404s. Now they want sync-links to fail immediately when any failure occurs, rather than continuing and masking errors.

Current Behavior

The sync-links command in /Users/mike/code/links/scripts/bin/linkctl (lines 234-577) has inconsistent error handling: