







Cua on Twitter / X
1/ Today, we're releasing the first open-source Computer History - now in early preview for Cua Driver on macOS, Windows, and Linux.It gives agents an encrypted, local record of actions they took through Cua Driver, so new sessions can recover useful context from earlier work. pic.twitter.com/tzIb1dFhPP— Cua (@trycua) August 18, 2026
Logging Sucks - Your Logs Are Lying To You
Why traditional logging fails and how wide events can fix your observability

OpenAI’s Egregious Pattern of Misconduct
Nine troubling new reports in seven days

Publish events, not logs
Don't think about logs for observability. Think about system boundaries and events.

Automated edits - OpenStreetMap Wiki
Automated edits and semi-automated edits (sometimes called mechanical edits) are changes made to OpenStreetMap content with no or very limited human oversight, including those made by bots, algorithmic processes, imports and also major changes made using general-purpose map editing tools such as JOSM. The creation and usage of such tools should conform to the Automated Edits code of conduct and details of edits should be documented on a wiki page in Category:Automated edits log. Undiscussed mechanical edits may be reverted without any discussion, though it may be nice to ask user who made edit before doing that.
Introducing COSIG: The Collection of Open Science Integrity Guides
Investigating the integrity of published scientific papers is key to the scientific process, but the necessary knowledge is in short supply. We present COSIG, an open collection of meta-scientific guides enabling anyone to perform forensic peer review.
A journal named a sleuth in a correction. The sleuth says that was ‘ethical editorial malpractice’
As the publishing community debates the merits of naming sleuths in retraction or correction notices, one journal did so without the sleuth’s permission — by publishing an email from the authors na…

Retraction Watch testifies in Congressional hearing on scientific publishing
Retraction Watch managing editor Kate Travis (center) testified April 15 in a hearing before the Investigations and Oversight Subcommittee of the House Science, Space and Technology Committee. Othe…

Permissioned Data Diary 7: Off the Record - Daniel's Leaflets
In which we put records in a repo, sign them, and sync them (but not quite the way you think).
There Are No Bugs, Just TODOs | Almad's Changelog
One of my life’s traumas is the bug trackers, the issue trackers, the project management tools. The toolset that completes the version control log to form the development equivalent of double-entry bookkeeping.
War on CARs - Data service diaries
A widespread authenticity problem in the Authenticated Transfer Protocol, from real-world use of Content-Addressible aRchives

War on CARs - Data service diaries
A widespread authenticity problem in the Authenticated Transfer Protocol, from real-world use of Content-Addressible aRchives

AT Proto Collection Tracker
Discover AT Protocol activity from the bottom up — live record counts by collection type from the Jetstream firehose, grouped by namespace.
AT Proto Collection Tracker
Discover AT Protocol activity from the bottom up — live record counts by collection type from the Jetstream firehose, grouped by namespace.
extremely cool idea. but yeah manually logging such decisions is obviously not going to happen. you should just work and let the tools log the decision points as you go
crates.io: Rust Package Registry
crates.iodan
ok this is amazing i've made a claude skill that uses @bobbby.online's deciduous to generate a design evolution tree from a project's commit history. this tree is generated by Claude using the displayed prompt (and my skill). the graph ~matches how i remember it react-deciduous-example.pages.dev
Blink: Intent to Experiment: Signature-based Integrity
Blink: Intent to Experiment: Signature-based Integrity
groups.google.com