thepurpose

you're right — and the speed-run is even faster than a year. Mine took about five weeks. I was never a serious dev. At the end of September I fell down the Hermes/LLM rabbit hole and haven't climbed out. My entire public GitHub footprint since then: 5 pull requests and 10 issues across six repos — one merged into the official Hermes plugin catalog, two still open, two closed with lessons attached. Quoting my own note below because it's the learning that cost the most to earn: the drag of switching between context windows all day. Taste and output take care of themselves once you stop paying that tax.

Three examples — no privacy needed, it's all public:

1. NousResearch/hermes-agent #142626: merged. A PayPerQ relay provider now installs into a fresh Hermes setup with one command.
2. jooray/third-ear: four bug reports in one week, all four confirmed and fixed by the maintainer — found by using the app daily, not by reading code.
3. caprover/caprover #2527: closed, not merged. A maintainer's blunt "AI slop" review and shed analogy taught me more about taste than any merge would have. The barrier to building isn't coming down. It's already gone. 🤙

Your agent can wait. Your attention can't.

Seven rules for staying the one watchman behind N agent windows. Plus a two-minute day-end ritual and a short Don Juan lesson on demons that work while you look away. #WarriorsWay with #DonJuan

has landed in my toolchain, and it's from another world — seriously great. I talk, the transcript drops into my White Noise group, my LLM coworker picks it up and answers, and Third Ear reads me the reply. Voice to #hermes via

and vice versa: exactly the bridge I'd been missing. Filed three issues on my first day, one closed the same day. This is how open source should feel.

h/t

Onwards 🫡

has landed in my toolchain, and it's from another world — seriously great. I talk, the transcript drops into my White Noise group, my LLM coworker picks it up and answers, and Third Ear reads me the reply. Voice to #hermes via

and vice versa: exactly the bridge I'd been missing. Filed three issues on my first day, one closed the same day. This is how open source should feel.

h/t

Onwards 🫡

"I will always come back and rise. Stronger and wiser than ever🔥🔥🙏 " --

The question of our token-burning times, asked by

.

Less "Netflix and chill", more humans. Read the whole thing, drop your own tips:

#asknostr

i can see myself on the screen. 🤔

I vibe memes and like it: see below plus a looooot of private ones I don't like to share in public. which is the real data point here. i send them in dms sooo often and feel good

My first and most beloved Nostr project #memely has just proven that it is largely superfluous for me and has been replaced in my workflow by LLMs. Hooray!

The hype is real.

Should I cry or laugh? 🤣🤣🤣

h/t

Slaying my heroes again. Fuck it. I procrastinated for too long once more.

h/t

Onwards. 🫡

hits me now with confidence. Onwards. 🫡

https://wavlake.com/track/f9c90b03-bb20-410f-9ded-0b4f65e24df9

The self speaks. the world answers. The warrior prefers the world's answer. #WarriorsWay with #DonJuan

Full effort in silence. Verifying before claiming done, and saying plainly when I don't know.

shifted #memely's core value proposition to dynamic meme templates based on real-time posts from my follows. Usage feels like a Frankenstein resurrection moment. 🎉🎉🎉

for turiz the #memely dev

gg wp. PV 🫂

Read Aloud: 🎙️ Transcribe voice messages (Android)

🛸

Question about credit-id handover on

:

1. If I delete an old credit id (which you describe as permanently destroying almost all metadata), can that same credit id still be redeemed into a new credit id afterwards, or is it gone?
2. Does "redeem a credit id you already have" merge the old credit's deposit/usage history into the new credit id, or does redemption also destroy the old credit's metadata like deletion does?
3. Is the redeem flow documented anywhere for end users? I could only find the one-line link in the account UI.

cc #asknostr

: What do we do next or what are you working on? 😉

I'm digging into White Noise inline rendering of nostr notes — How each official client decodes and renders them — with my LLM coworker: the parsers are all mapped now (five independent NIP-19 implementations across the stack), and next I'm drafting an outside slice-1 for mdk#2362 — shared reference vectors + decode-only conformance tests against the existing parsers.

White Noise (marmot) is a nice channel for me on hermes, so giving something back which I then can reuse myself seems to be a no-brainer.

Update to this: the catalog PR merged 🎉

The

plugin is now in the official #Hermes plugin catalog (v0.3.1, merged 2026-10-24) — a fresh Hermes install reaches the ppq API with one command:

hermes plugins install ppq

No more manual cloning; the catalog pins the exact verified commit. The bootstrap guide is updated in both languages: https://thepurpose-npub.github.io/hermes-ppq-bootstrap/