diet256
hyperhyperspace-core
| diet256 | hyperhyperspace-core | |
|---|---|---|
| 3 | 10 | |
| 11 | 194 | |
| - | 0.5% | |
| 1.5 | 5.7 | |
| 12 months ago | 7 months ago | |
| Go | TypeScript | |
| Mozilla Public License 2.0 | 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.
diet256
-
Ask HN: What Are You Working on This Year?
I'm working on INET256, an API for secure identity based networking. The reference implementation, mesh256 is a mesh network using a distributed routing algorithm. There is also diet256, which is a centrally coordinated network with direct connections using QUIC over The Internet.
https://github.com/inet256/inet256
https://github.com/inet256/diet256
- Diet256 is a Centrally Coordinated INET256 Network using QUIC
- Show HN: Diet256 Is a Centrally Coordinated INET256 Network
hyperhyperspace-core
- 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).
What are some alternatives?
stun - Fast RFC 5389 STUN implementation in go
svelt-yjs - A library for your Svelte app that lets you build Svelte stores from Yjs types.
yomo - 🦖 Stateful Serverless Framework for building Geo-distributed Edge AI Infra
solid - Solid - Re-decentralizing the web (project directory)
hyprspace - A Lightweight VPN Built on top of IPFS + Libp2p for Truly Distributed Networks.
fusionauth-issues - FusionAuth issue submission project
speaklikeabrazilian.com - Speak Like A Brazilian
token-list - The community maintained Solana token registry
fortio - Fortio load testing library, command line tool, advanced echo server and web UI in go (golang). Allows to specify a set query-per-second load and record latency histograms and other useful stats.
examples - Serverless Examples – A collection of boilerplates and examples of serverless architectures built with the Serverless Framework on AWS Lambda, Microsoft Azure, Google Cloud Functions, and more.
quic-go - A QUIC implementation in pure Go
miniflare - 🔥 Fully-local simulator for Cloudflare Workers. For the latest version, see https://github.com/cloudflare/workers-sdk/tree/main/packages/miniflare.