Announcing Changesets v3 | Changesets

A tool to manage versioning and changelogs with a focus on monorepos

Record Versioning - at:// pizza thoughts

The people, they want post editing!

kettanaito/async-history-stack

Arbitrary change history management in JavaScript.

Introducing Tap: Repository Synchronization Made Simple | Bluesky

Just about every app built on AT needs data from a repository at some point. For many use cases – feed generators, labelers, bots – streaming live data through a Relay or Jetstream works well. But some applications need to go beyond what Jetstream was designed for, like tracking specific subsets of a repo, automatically backfilling a database when adding new repos to monitor, or even mirroring the entire Atmosphere.

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.

Debezium

Debezium is an open source distributed platform for change data capture. Start it up, point it at your databases, and your apps can start responding to all of the inserts, updates, and deletes that other apps commit to your databases. Debezium is durable and fast, so your apps can respond quickly and never miss an event, even when things go wrong.

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).

y-atproto - npmx

A [Yjs](https://yjs.dev/) CRDT provider that syncs documents over the [AT Protocol](https://atproto.com/). Documents are stored as ATProto records and real-time updates are delivered via [Jetstream](https://github.com/bluesky-social/jetstream).

Edit lenses

A lens is a bidirectional transformation between a pair of connected data structures, capable of translating an edit on one structure into an appropriate edit on the other. Many varieties of lenses have been studied, but none, to date, has offered a satisfactory treatment of how edits are represented. Many foundational accounts only consider edits of the form "overwrite the whole structure," leading to poor behavior in many situations by failing to track the associations between corresponding parts of the structures when elements are inserted and deleted in ordered lists, for example. Other theories of lenses do maintain these associations, either by annotating the structures themselves with change information or using auxiliary data structures, but every extant theory assumes that the entire original source structure is part of the information passed to the lens.We offer a general theory of edit lenses, which work with descriptions of changes to structures, rather than with the structures themselves. We identify a simple notion of "editable structure"--a set of states plus a monoid of edits with a partial monoid action on the states--and construct a semantic space of lenses between such structures, with natural laws governing their behavior. We show how a range of constructions from earlier papers on "state-based" lenses can be carried out in this space, including composition, products, sums, list operations, etc. Further, we show how to construct edit lenses for arbitrary containers in the sense of Abbott, Altenkirch, and Ghani. Finally, we show that edit lenses refine a well-known formulation of state-based lenses, in the sense that every state-based lens gives rise to an edit lens over structures with a simple overwrite-only edit language, and conversely every edit lens on such structures gives rise to a state-based lens.

Dia on Twitter / X

Meet @ History - an early access feature in Dia that uses memory to find the content you need so you don't have to.It’s brand new, experimental, and off by default. @ History is encrypted & stored locally.Want to give it a try? pic.twitter.com/j2IWUK4Yei— Dia (@diabrowser) June 11, 2025

Peersky Browser (@peersky@mastodon.social)

Attached: 2 images ⚡v1.0.0-beta.22 is here! Meet the new Peers Dashboard in P2P Markdown: - Track live editing status in real time - See who’s in the room with host/client roles - View Edit History for better collaboration context Try it out! #PeerSky