Announcing Changesets v3 | Changesets
A tool to manage versioning and changelogs with a focus on monorepos
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.
ActivityPub, AT Protocol, and more!
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.
at://moderation.wsocial.eu/eu.wsocial.verification.record
List of eu.wsocial.verification.record records from moderation.wsocial.eu
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).
Reading Proposal 0016: What atproto’s “Permissioned Data” Actually Does - Nick's Blog
AT Protocol is public by default. Everything you write goes into a signed, archived, and rebroadcastable repository that anyone can read from and moves throu…
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).
A new automated feedback option for authors - openRxiv
Authors who post preprints on openRxiv servers can get formal and informal feedback on their manuscripts in a number of ways. Our bioRxiv to journal (B2J) and medRxiv to journal (M2J) pipelines are linked to traditional peer review venues, enabling authors to save time by submitting directly from bioRxiv or medRxiv to any one of…
I've been working on an "at protocol notion". One of the things that has been holding it up has been coming to terms with the oddities of putting this data on a PDS. A document is a collection of edits, whose edits we collect will change that document pretty substantially. This is a feature
What if a PDS became more than a repository for posts? We propose using AT Protocol as a creator-controlled publication layer for declaration metadata describing digital works, making rights, provenance, and other trusted metadata independently verifiable and easier to discover.
From Personal Data Server to Personal Metadata Server
liccium.leaflet.pubnew data diary! this is the most in the weeds yet, all revolving around our proposed URI structure for permissioned data. turns out you can figure out a lot about a protocol from the uri! as always, let me know what you think :)
Permissioned Data Diary 5: What’s in a Name?
dholms.leaflet.pub
