fireproof
orbitdb
fireproof | orbitdb | |
---|---|---|
4 | 32 | |
181 | 8,127 | |
16.0% | 0.6% | |
9.8 | 9.2 | |
5 days ago | 14 days ago | |
JavaScript | JavaScript | |
GNU General Public License v3.0 or later | 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.
fireproof
- Current Progress of IPFS
-
New realtime database for IPFS
Doing a js-ipfs backend would be straightforward and wouldn't change the app API, so it totally makes sense to do that. I tend to see it as a both/and situtation, and the current core makes no assumptions about network either way. Adding web3.storage was just a ~200 loc React hook, so I bet the js-ipfs bridge would also be that easy.
-
Announcing my new realtime database, Fireproof
Here's the Fireproof GitHub repo, and here's the website. Thanks! Chris
orbitdb
- OrbitDB reaches version 1.0 after 8 years of development
-
Open source P2P alternative to Slack and Discord built on Tor and IPFS
OrbitDB is not well-funded, but there's fresh work happening recently by some dedicated volunteers: https://github.com/orbitdb/orbitdb/commits/main
- Current Progress of IPFS
-
orbit-db VS db3 - a user suggested alternative
2 projects | 15 Jan 2023
- Jack Dorsey texts Elon Musk (March 26, 2022)
- Decentralised public immutable database
-
Ask HN: Is there a descentralized DB with a simple social conflict resolution?
I've been thinking it might be practical to build a simple decentralized database, where agents just know each other, so conflict resolution does not need to be so strong and can rely on the social layer.
I think this applies to most databases, but I'm particularly thinking of internal enterprise databases, some social networks, any federated database system, and different devices of a single user
I'm thinking of this features:
1- Append-only?, full history of operations. Deletes / edits do not remove data, they only modify the "active state"
2- Agents are public keys or similar (DIDs?)
3- Operations are signed, and receivers verify if operation is valid, and sender is allowed
4- Operations form a Merkel-DAG (similar to git, they link to the tips of current "active state", like a commit/merge in git)
So far I think I've basically described [OrbitDB](https://github.com/orbitdb/orbit-db)
Consensus is where things get real hard, [OrbitDb seems to use a last-write-wins CRDT](https://news.ycombinator.com/item?id=22920204), and although I don't know the details of orbitDb, I think for many simple use-cases, conflicts can just be resolved on the social layer. But I think we need to provide agents with good tools to resolve conflicts
I'll try my best here with some ideas:
- When merging, we can order operations by their timestamp, if operations enter conflict, raise it to the conflicting agents, or someone with permission to solve them.
If an agent makes public an operation that forks its own history, mark agent as malicious or compromised, alert other agents, this needs resolution on the social layer, you have proof of misconduct, an agent has signed diverging operations
Any operation becomes fully settled if you have proof that all agents of your system have referenced it directly or indirectly through newer operations.
Timestamps can be upgraded by using @opentimestamps to get proof that an operation existed at time X (prevents creation of operations in hindsight). Though this does not prove operation has been made public
-
How to make a crowdsourced distributed metadata database?
Both use OrbitDB: Peer-to-Peer Databases for the Decentralized Web. JavaScript. MIT license. repo
-
Release: New features for Nalli
I think a wallet-agnostic memo solution is definitely the way. Having wallets that end up (partly) incompatible is only gonna hurt the UX. Maybe a decentralised DB solution like OrbitDB or GunDB can be the best way forward, although I haven't dove deeply into the docs yet.
-
Building a decentralized database
Checkout this https://github.com/orbitdb/orbit-db peer-to-peer database for the decentralized Web.
What are some alternatives?
web3.storage - DEPRECATED ⁂ The simple file storage service for IPFS & Filecoin
ipfs - Peer-to-peer hypermedia protocol
dejavu - The Missing Web UI for Elasticsearch: Import, browse and edit data with rich filters and query views, create search UIs visually.
IceFireDB - @IceFireLabs -> IceFireDB is a database built for web3.0 It strives to fill the gap between web2 and web3.0 with a friendly database experience, making web3 application data storage more convenient, and making it easier for web2 applications to achieve decentralization and data immutability.
gun - An open source cybersecurity protocol for syncing decentralized graph data.
noosphere - Noosphere is a protocol for thought; let's discover it together!
js-libp2p - The JavaScript Implementation of libp2p networking stack.
react-redux-provide
berty - Berty is a secure peer-to-peer messaging app that works with or without internet access, cellular data or trust in the network
redux-batched-subscribe - store enhancer for https://github.com/reactjs/redux which allows batching subscribe notifications.
solid - Solid - Re-decentralizing the web (project directory)