solid
orbitdb
Our great sponsors
solid | orbitdb | |
---|---|---|
117 | 32 | |
8,173 | 8,114 | |
0.0% | 0.9% | |
0.0 | 9.3 | |
over 1 year ago | 6 days ago | |
HTML | JavaScript | |
MIT License | 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.
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
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?
Mastodon - Your self-hosted, globally interconnected microblogging community
ipfs - Peer-to-peer hypermedia protocol
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.
web3.storage - DEPRECATED ⁂ The simple file storage service for IPFS & Filecoin
Peergos - A p2p, secure file storage, social network and application protocol
gun - An open source cybersecurity protocol for syncing decentralized graph data.
kanidm - Kanidm: A simple, secure and fast identity management platform
js-libp2p - The JavaScript Implementation of libp2p networking stack.
Nullboard - Nullboard is a minimalist kanban board, focused on compactness and readability.
berty - Berty is a secure peer-to-peer messaging app that works with or without internet access, cellular data or trust in the network
hyperhyperspace-core - A library to create p2p applications, using the browser as a full peer.
ipfs-chat - Real-time P2P messenger using go-ipfs pubsub. TUI. End-to-end encrypted texting & file-sharing. NAT traversal.