ept / crdt-website Goto Github PK

In the CRDT Glossary section, under Optimistic replication subsection,
"See Optimistic Replication by Yasushi Saito and Marc Shapiro." the link seems to be broken.

https://core.ac.uk/download/pdf/22879037.pdf

The mentioned URL Nikita Voloboev: “Everything I know” is broken.
Looks like the updated URL is https://wiki.nikiv.dev/sharing/everything-I-know.

Can you check?

Issue on: https://github.com/ept/crdt-website/tree/gh-pages/pages/index.md

Please add these:
Best paper DAIS'21: https://link.springer.com/chapter/10.1007/978-3-030-78198-9_4

LightKone LiRA: https://www.researchgate.net/publication/347522020_LightKone_Reference_Architecture_LiRA

Thanks.

As shown on the actions list, the PRs merged today failed to deploy, likely due to a GitHub Actions outage:

The outage is now resolved, so hopefully deployment should work now. I believe @ept could go to the most recent run and click "Re-run all jobs" on the top right (only available to those with repo access).

Please consider including a link to my blog series on the mathematical foundations of state-based CRDTs:

https://lars.hupel.info/topics/crdt/01-intro

It contains interactive code examples for JS programmers to play around with.

Issue on: https://github.com/ept/crdt-website/tree/gh-pages/pages/glossary.md

Currently, it is only "Another name for add-wins set. “Add-wins” is now preferred." but there is no definition of "AWSet" in the glossary

First, thanks for creating this site. Super useful.

Second, in a few places you refer to Figma as using CRDTs. They themselves say this is not the case in the document you refer to:

Figma isn't using true CRDTs though. CRDTs are designed for decentralized systems where there is no single central authority to decide what the final state should be. There is some unavoidable performance and memory overhead with doing this. Since Figma is centralized (our server is the central authority), we can simplify our system by removing this extra overhead and benefit from a faster and leaner implementation.

I think this distinction is important. If what Figma is doing is a CRDT, then Replicache, Fluid Framework, and similar approaches would also be considered CRDTs.

But that doesn't seem right -- what Replicache and FF do are clearly not CRDTs, and therefore it's not correct to refer to Figma as using CRDTs either (unless you have more up to date info than that blog post).

Hi,

Sorry I know it's off site but is the dist-sys #crdt channel still active? The link from https://crdt.tech/community ends up on a heroku application error.

I was just chatting about whether there is / should be a general CRDT community workspace and immediately thought to look on https://crdt.tech -- is there an active community channel somewhere or should we maybe create one?!

Thanks,

James.

Issue on: https://github.com/ept/crdt-website/blob/gh-pages/pages/index.md

Hi, I find it the "about" is very concise and right to the point.

May I translate the "about" page to Chinese and publish it on my personal blog? Will link to the original site and make it clear it is an approved translation.

Thank you.

https://arxiv.org/abs/2004.00107

Based on what I read on the website, it sounds like there are some practical limitations to this. Say for example, in a collaborative document that is being edited offline, a user moves one object to one place and the other moves the object to a different place. It maybe so that algorithms can resolve and build a merged a version of the document, but who is to say whether the change by one user is correct over the other. One object can't be in two places, so I think the users have to ultimately discuss and decided which version to keep, so it's better if the document is kept strongly consistent in the first place.