3 releases (breaking)

0.11.0 Jun 5, 2024
0.10.0 Jun 5, 2024
0.9.0 Mar 26, 2024
0.2.0 Aug 7, 2023

#558 in Data structures

Download history 100/week @ 2024-03-20 62/week @ 2024-03-27 38/week @ 2024-04-03 3/week @ 2024-04-10 1/week @ 2024-04-17 4/week @ 2024-04-24 7/week @ 2024-05-08 24/week @ 2024-05-15 45/week @ 2024-05-22 49/week @ 2024-05-29 388/week @ 2024-06-05 84/week @ 2024-06-12 120/week @ 2024-06-19 88/week @ 2024-06-26

686 downloads per month
Used in 11 crates (2 directly)

MIT/Apache and GPL-3.0-or-later

160KB
4K SLoC

Collaborative Objects

Collaborative objects are graphs of CRDTs.

Basic Types

The basic types that are found in radicle-cob are:

  • CollaborativeObject -- the computed object itself.
  • ObjectId -- the content-address for a single collaborative object.
  • TypeName -- the name for a collection of collaborative objects.
  • History -- the traversable history of the changes made to a single collaborative object.

CRU Interface (No Delete)

The main entry for manipulating CollaborativeObjects is by using the CRU like functions:

Storage

The storing of collaborative objects is based on a git backend. The previously mentioned functions all accept a Store as parameter. The Store itself is an accumulation of different storage capabilities:

Resource

The create and update functions take a Resource. It represents the type of resource the collaborative objects are relating to, for example a software project.

History Traversal

The History of a CollaborativeObject -- accessed via CollaborativeObject::history -- has a method History::traverse which provides a way of inspecting each Entry and building up a final value.

This traversal is also the point at which the Entry::author and Entry::resource can be retrieved to apply any kind of filtering logic. For example, a specific author's change may be egregious, spouting terrible libel about Radicle. It is at this point that the actor's change can be filtered out from the final product of the traversal.

Dependencies

~19MB
~452K SLoC