







Tangled did a good post about contributions that I’ll need to follow up on but in the context of CRDTs I think it’s worth calling out a few differences and discussing best practices Constraints CRDTs require storage of some portion of an OP Log Some portion of the storage will be on a hosted server (PDS) A portion of those servers will be self hosted by an individual Contributions can come from many users There is a value in allowing contributions from a wide swath of users. Concerns Legal...
About CRDTs • Conflict-free Replicated Data Types
Resources and community around CRDT technology — papers, blog posts, code and more.
CRDT Papers • Conflict-free Replicated Data Types
Resources and community around CRDT technology — papers, blog posts, code and more.
Wrangling Web Contributions: How to Build a CONTRIBUTING.md
In this activity you will learn how to create and maintain a CONTRIBUTING.md for an open source project.
Proposal for a CRDTs on At Proto Working Group
There’s been some work done on using the PDS / At Proto as a to store and transmit CRDT operations. There is a general feeling that if we can figure out the right approach for this it will enable a number of new experiences on At Proto, specifically a collaborative editing approach that is localfirst. We hope that as a working group we can come up with some of the following: A set of best practices and recommendations that apps can adopt to enable collaborative, localfirst, editing via crdts ...

Conflict-Free Replicated Data Types (CRDTs)
The CRDT Dictionary: A Field Guide to Conflict-Free Replicated Data Types - Ian Duncan
A comprehensive guide to CRDTs and their tradeoffs, from counters to sequences. Written in the spirit of the Typeclassopedia, exploring how different CRDTs solve the distributed consensus puzzle.



research.latha.org
A permissioned appview for research documents on AT Protocol. True data ownership with optional monetization.
Schema 5.5 now available: adding CRediT, new record types for blogs and posters, and more - Crossref
Research is rarely limited to a single contributor performing a single role. Behind every research output are people contributing in various ways: software development, data analyses, methodology design, and much more. Often, the same person contributes in several of these ways. Until now, Crossref metadata could only capture part of that picture, but this is changing with Schema 5.5.

How to manage casual contributors to open source projects
Try these strategies to better utilize contributions from your project's episodic volunteers.

Robot Pedantry, Human Empathy
Homebrew was the first open source project I’ve maintained where I’ve had to review and merge contributions from other users. Homebrew is also one of the most active community projects on GitHub with a consistently small team of maintainers (always under thirty in total, always under ten doing work every week). As a result I’ve had to figure out over the last twelve years how best to manage large numbers of contributions from users in pleasantly and efficiently for both maintainers and contributors.
Private, non-shared data in repo? · bluesky-social atproto · Discussion #3363
I have a use-case for keeping private data in a repo, i.e. data that does not leave the repo via the standard sharing mechanisms, and before I leap into modifying the code to support it, I'd li...
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.pubSharing this! Wish I'm not late for #IETF126 Tangled found PDS doesn't fit well for contributions even with upcoming permissioned space spec. So, we are planning to store record-like data outside of PDS, in Knot. This is a post explaining the reasons & upstream spec change we need. #atproto #atdev
tangled-cob.md · by boltless.me
tangled.org