yjs
solid
yjs | solid | |
---|---|---|
53 | 117 | |
15,280 | 8,173 | |
3.5% | 0.0% | |
8.6 | 0.0 | |
9 days ago | over 1 year ago | |
JavaScript | HTML | |
MIT | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
yjs
- Show HN: Collaborate on your YC Application with CRDT-powered forms
-
Making CRDTs 98% More Efficient
One idea is just to use fewer random bits in peerIDs. Yjs (https://docs.yjs.dev/) gets away with just 32 random bits. If you compromise and use 64 random bits, then even a very popular doc with 1 million lifetime peerIDs will have a < 10^-7 lifetime probability of collision.
-
An Interactive Intro to CRDTs
I've seen it come up often in collaborative text editors.
Also see: https://github.com/yjs/yjs
-
JSON Schema Store
You are absolutely right that XML is better for document structures.
My current theory is that Yjs [0] is the new JSON+XML. It gives you both JSON and XML types in one nested structure, all with conflict free merging via incremental updates.
Also, you note the issue with XML and overlapping inline markup. Yjs has an answer for that with its text type, you can apply attributes (for styling or anything else) via arbatary ranges. They can overlap.
Obviously I'm being a little hypabolic suggesting it will replace JSON, the beauty of JSON is is simplicity, but for many systems building on Yjs or similar CRDT based serialisation systems is the future.
https://github.com/yjs/yjs/
-
Launch HN: Tiptap (YC S23) โ Toolkit for developing collaborative editors
Note: https://github.com/yjs/yjs for collaborative "document edition, and user cursors"; has WebRTC, web socket, matrix.org backend
-
Wormholers, what can CCP and wormholers do to improve J-Space?
CCP needs to revamp proto anyway, due to recent exploits... practically, nothing really prevents 'em from using some sort of CRDT's to make the state of the sig view eventually consistent (yjs lib, if we're speaking frontendian).
-
How to use Yjs with Ruby on Rails?
Yjs framework: Because it is a CRDT implementation which provides collaborative editing and offline-first capability.
-
๐๐๐ EweserDB, the user-owned database ๐๐๐
No problem. The database CRUD features are just helpers as an abstraction on top of yjs: https://docs.yjs.dev/. Eweser adds schemas in the form of typescript types to make using it simpler, more structured, and interoperability easier.
- Ask HN: What is new in Algorithms / Data Structures these days?
- How does Google docs send the changes done by other users in real-time?
solid
-
Simple Lasts Longer
This doesn't support the various consumer cloud storage APIs, but you've just reminded me of a project I ran into years ago that seems to still be around: https://remotestorage.io/
There's also Solid which attempts to do something similar: https://solidproject.org/
-
The current state of the Web and what is the next step in its evolution.
It is surprising to me this is not talked about more. I see little to none online news, podcasts, YouTube videos or anything else where this is discussed. I only found out about it because of research I did on Tim Berners-Lee in preparation for a Career Day talk at my kids middle school. Otherwise I would have probably not known about it still today. And even after I found out and started watching YouTube videos on the topic, YouTube won't even suggest any related videos about it even after already watching multiple videos on the subject (Web 3.0, Solid Project, Decentralized Web...etc).. is Big Tech trying to keep the web from evolving into what Sir Tim Berners-Lee is proposing?
-
Write libraries instead of services, where possible
It's only an unreasonable amount of work if you assume that the user is managing a separate storage backend for each library. If you take the Tim Berners-Lee approach (re: https://solidproject.org/) then each user is only managing one storage backend: the one that stores their data. The marginal cost of hooking in one more library low.
We just have to get a little more fed up with all of these services and then the initial cost of setting it up in the first place will be worth it. Any day now...
-
Manas: Storage servers confirming to Solid protocol
Solid is a web native protocol to enable interoperable, read-write, collaborative, and decentralized web, truer to web's original vision.
-
Manas: Solid protocol storage server in Rust for decentralized web
Manas project(https://github.com/manomayam/manas/tree/main) aims to create a modular framework and ecosystem to create correct, robust storage servers adhering to Solid protocol in rust.
[Solid](https://solidproject.org/) is a web native protocol to enable interoperable, read-write, collaborative, and decentralized web, truer to web's original vision.
Solid adds to existing Web standards to realise a space where individuals can maintain their autonomy, control their data and privacy, and choose applications and services to fulfil their needs.
-
My vision of the semantic web...correct me if I'm wrong.
You're describing Solid, not the Semantic Web. Granted, Solid uses Semantic technologies to achieve it. https://solidproject.org/
- Threads : ร peine lancรฉ, le concurrent de Twitter crรฉe par Facebook compte 10 millions de membres
-
The problem with federated web apps
Tim Berners-Lee's Solid project is working on that. Put data in "pods" that are stored on pod servers, which are federated. You can self-host.
It could be a federated layer of identity & personal content decoupled from social platforms.
https://solidproject.org/
-
Update of the RDF and SPARQL (RDF star) families of specifications
Check out https://solidproject.org (If you want a short intro I recently gave a ~30min talk about it: https://noeldemartin.com/fosdem)
- Solid, a spec that lets people store their data securely in decentralized Pods
What are some alternatives?
automerge - A JSON-like data structure (a CRDT) that can be modified concurrently by different users, and merged again automatically.
Mastodon - Your self-hosted, globally interconnected microblogging community
liveblocks - Liveblocks is a platform to ship collaborative features like comments, notifications, text editors in minutes instead of months.
logseq - A local-first, non-linear, outliner notebook for organizing and sharing your personal knowledge base. Use it to organize your todo list, to write your journals, or to record your unique life.
automerge-rs - Rust implementation of automerge [Moved to: https://github.com/automerge/automerge]
orbitdb - Peer-to-Peer Databases for the Decentralized Web
crdt-woot - Implementation of collaborative editing algorithm CRDT WOOT.
Peergos - A p2p, secure file storage, social network and application protocol
milkdown - ๐ผ Plugin driven WYSIWYG markdown editor framework.
kanidm - Kanidm: A simple, secure and fast identity management platform
MobX - Simple, scalable state management.
Nullboard - Nullboard is a minimalist kanban board, focused on compactness and readability.