I)ruid
39.8K posts

I)ruid
@druidian
NIP-05:[email protected] - Cleverly disguised as a responsible adult. Founder @TrammellVC, @Blockhenge, & @Rogue__Signal. My opinions are my own. #Bitcoin ∞/21M



Yes, Deputy Roush failed to appear in court on May 8, 2025, leading to dismissal of all traffic citations. The sheriff's internal investigation found he violated multiple department policies during the stop and arrest. Trumbull has filed a notice of intent to sue the county for $1M over the incident, which—if settled or lost—would be paid from taxpayer funds.

The FBI just acknowledged that the federal government buys Americans' location data in its testimony to the Senate Select Subcommittee on Intelligence. This is a clear violation of the Fourth Amendment and is why I introduced the Government Surveillance Reform Act - to close the data broker loophole that allows intelligence agencies to buy Americans' private data.




Charted: Trust in the U.S. Government Fell From 77% to 17% 🏛️ visualcapitalist.com/chart-trust-in…





OpenClaw memory unlock! Forcefeed memories before responses! I just noticed that a new runtime hook was added to OpenClaw this week by @vincent_koc & others that will solve a lot of OpenClaw drift ... if someone builds a plugin for it! Who's building a communication plugin for OpenClaw using the new before_prompt_build hook? Using prependSystemContext and appendSystemContext, this allows you to inject extra instructions/directions BEFORE the agent builds the response. Here's how OpenClaw weights things: 1 Core system prompt 2 Plugins - prependSystemContext (NEW) -appendSystemContext 3 Agents.md - your custom rules 5 Tools > Skills - tool APIs and documentation 4 Workspace files - memory, playbooks/SOPs etc 5 long-term memory - retrieval from Obsidian/DB 6 session transcript - current convo context 7 your message - your request or you can think about it this way: prependSystemContext (NEW plugin hook) system prompt (you can't change this) appendSystemContext (NEW plugin hook) agents.md, bootstrap files tools & skills workspace files (memory, Playbooks & SOPs) conversation context prependContext (previous plugin hook) current message / request -- The biggest unlock of this addition to OpenClaw (which should be default behavior by OpenClaw cc @steipete) is a template communication plugin that turns on when a user activates memory_search & memory_get. The Default Comms Protocol Plugin should require the agent to use memory_search before asking the user a question. Majority of users who turn on openclaw's advanced semantic memory don't realize their bot is not using it. Even if you add a hard rule in agents.md that the agent must use it's memory tools before asking questions, majority of the time it does not use the tool. This is surfaced when you ask your bot to read the logs and show how many times it uses memory_search and memory_get over the last 24 hours. usually the answer is close to zero. Anyway, with this new runtime hook exposed, you can now really tune the kinks out of how your openclaw agent communicates with you. Don't want your agent to offer you "if you like I can ..." rabbit holes? Don't want your agent to say "good catch" ? Don't want your agent to ask you things it knows already? Don't want your agent to say "you're right to call that out..." Train it out with a comms plugin that has prompt weight above everything else, and then block messages that come back to you violating the comms protocol & force the agent to rewrite them to spec using message_sending hook for outbound filtering. This can also be used more practically for other things like token caching, model routing & multi-agent routing. You can now route messages to models more effectively to save money, and catch context-switching messages that are sent to the wrong agent before it bloats the context window of the main agent... Is anyone building on this?





















