hyperhyperspace-core
Feedstuff
| hyperhyperspace-core | Feedstuff | |
|---|---|---|
| 11 | 1 | |
| 211 | 4 | |
| 0.9% | - | |
| 3.6 | 1.8 | |
| 7 months ago | about 4 years ago | |
| TypeScript | Python | |
| 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.
hyperhyperspace-core
- Hyper Hyper Space: Make all data local
- Ask HN: What Are You Working on This Year?
- HyperHyperSpace – Make all data local. Communicate only through data sync
- Thin Platforms
-
I was wrong. CRDTs are the future
Not all CRDT libraries focus on text editing. For example, I'm working on a Byzantine fault tolerant general-purpose data sync library loosely based on CRDTs: https://www.hyperhyperspace.org
I'm finding it painfully difficult but it is evolving steadily.
-
AWS is playing chess, Cloudflare is playing Go
I'm thinking there's an interesting parallel between my browser-based p2p project [1] and cloudflare workers / DurableObjects. Instead of DurableObjects, we got HashedObjects [2], and instead of workers running on an edge network somewhere, we got in-browser p2p nodes running a browser-to-browser mesh network.
[1] Hyper Hyper Space: https://www.hyperhyperspace.org
-
The Future Needs Files
I agree with the author on the merits of the file abstraction, but I think the concept should be updated for networked devices. We need file formats that support both offline usage and seamless sync over the network.
For example, here I use a merkle DAG-based file format to represent CRDT-like types:
https://www.hyperhyperspace.org
The resulting abstraction can be universally looked up using a hash (or short sequence of words), can be modified offline and synchronized flawlessly. It's still WIP (for example, you still can't export it to an actual file, hehe).
-
The data model behind Notion's flexibility
> I've been kicking around the idea of writing a CRDT-based editor using this model.
I got around to creating a data layer (p2p, browser-based, CRDT-backed) for something like this:
https://github.com/hyperhyperspace/hyperhyperspace-core
I'd be interested in collaborating on your editor
-
The Web’s Missing Interoperability
I'm working on it, Ben [1].
Believe me, it is not easy thing to do.
[1] https://github.com/hyperhyperspace/hyperhyperspace-core
-
Solid Project: All of your data, under your control
Look at Hyper Hyper Space!
https://github.com/hyperhyperspace/hyperhyperspace-core
Its goals are similar, the approach is more pragmatic (p2p data layer using standard web browsers and webrtc).
Feedstuff
-
The Web’s Missing Interoperability
That's a big reason why I'm excited about repl.it. You can self-host a github repo in about 2 clicks (not including account setup). I could see it increasing the reach of self-hosted apps a lot.
Actually I made a little proof of concept for this a week ago: https://github.com/jacobobryant/Feedstuff
What are some alternatives?
webmonetization - Proposed Web Monetization standard
solid - Solid - Re-decentralizing the web (project directory)
fusionauth-issues - FusionAuth issue submission project
svelt-yjs - A library for your Svelte app that lets you build Svelte stores from Yjs types.
token-list - The community maintained Solana token registry