orbitdb
terminusdb
orbitdb | terminusdb | |
---|---|---|
32 | 51 | |
8,140 | 2,638 | |
0.8% | 1.3% | |
9.2 | 8.9 | |
6 days ago | about 1 month ago | |
JavaScript | Prolog | |
MIT License | Apache License 2.0 |
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.
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.
terminusdb
-
Ask HN: What is new in Algorithms / Data Structures these days?
How about some succinct data structures and delta encoding for modern databases [1]. Succinct data structures are a family of data structures which are close in size to the information theoretic minimum representation (while still being queryable).
[1] https://github.com/terminusdb/terminusdb/blob/dev/docs/white...
- TerminusDB v11 Released (temporal, Datalog graph DB
-
Datomic Is Now Free
There are already some open source alternatives to datomic. TerminusDB (https://github.com/terminusdb/terminusdb) for example is implemented in prolog (and Rust) so has the datalog variant query power that makes datomic so powerful. If you want free as in speech (thou I love free beer).
- Show HN: TerminusCMS – Headless CMS for Devs
-
Putting the Graph in GraphQL Query
You should try it out. You can either use TerminusDB by downloading it from our repositories, or you sign up for a free TerminusCMS account at dashboard.terminusdb.com.
-
Help with some python DB client installation errors please
Hey, I'm trying to install TerminusDB. They have the python client installation instructions here
-
Is there a terminusdb package?
Hi, I wanted to check if there's a NixOS package for TerminusDB
-
Rust Database - Ranking | OSS Insight
terminusdb
-
TerminusDB - Now with GraphQL
Head on over to GitHub for a full list of enhancements and bug fixes.
- TerminusDB Internals Part 2: Change Is Gonna Come
What are some alternatives?
ipfs - Peer-to-peer hypermedia protocol
dolt - Dolt – Git for Data
web3.storage - DEPRECATED ⁂ The simple file storage service for IPFS & Filecoin
datahike - A durable Datalog implementation adaptable for distribution.
gun - An open source cybersecurity protocol for syncing decentralized graph data.
nvim-treesitter-context - Show code context
js-libp2p - The JavaScript Implementation of libp2p networking stack.
excel_as_code - Blog on excel as code
berty - Berty is a secure peer-to-peer messaging app that works with or without internet access, cellular data or trust in the network
Papercups - Open-source live customer chat
solid - Solid - Re-decentralizing the web (project directory)
slowbug - Slowbug is a VS Code extension for debugging your code in slow-mo!