orbitdb
superhighway84
orbitdb | superhighway84 | |
---|---|---|
32 | 40 | |
8,140 | 672 | |
0.8% | - | |
9.2 | 5.8 | |
6 days ago | 16 days ago | |
JavaScript | Go | |
MIT License | GNU General Public License v3.0 only |
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.
superhighway84
-
Would we still create Nebula today?
https://github.com/gravitl/netmaker
Honorable mention:
SuperHighway84 - more of a Usenet-inspired darknet, but I love the concept + the author's personal website:
https://github.com/mrusme/superhighway84
-
Open source P2P alternative to Slack and Discord built on Tor and IPFS
While I do like the idea behind a P2P E2EE chat, I believe that unless you're willing to invest heavily into OrbitDB and IPFS, this project will stay niche at best.
The performance issues that come along with running OrbitDB/IPFS on a machine, let alone a mobile device, are still significant unfortunately. Adding Electron on top of what is already a heavy-weight application is probably going to make people's devices go brrrrr all the time. Not only that, but I would argue that for instant communication this stack might not be the best idea in terms of performance in first place.
Besides, the way IPFS has been (and still keeps) changing their dozens of libraries doesn't make development particularly smooth either. OrbitDB is always behind the latest IPFS version due to all these changes that are being introduced. Hence unless you're planning to allocate developer time on these two things as well, my guess is that you probably won't have too much fun with your back-end.
The integration with Tor is another thing that will likely be a time drain for developers, as other people here already pointed out, and that will lead to even more performance issues down the line.
Don't get me wrong, I really like the idea behind this project. However, I feel like the aspirations are unrealisticly high and the actual outcome might be realtively frustrating for the average end-user. Having that said, I would love my gut feeling to be proven wrong!
Disclaimer: I'm the developer of Superhighway84 (https://en.wikipedia.org/wiki/InterPlanetary_File_System#App..., https://github.com/mrusme/superhighway84), a USENET-inspired, uncensorable, decentralized internet discussion system running on IPFS & OrbitDB.
-
Ask HN: Is it time to resurrect a Usenet clone?
Someone created a Usenet-like thing on IPFS. https://github.com/mrusme/superhighway84
It's kind of dead. IIRC the dev put that on the back burner in favor of a new BBS-like app. https://github.com/mrusme/neonmodem
-
YouTube is seeming like a less and less viable platform... they should do the Patreon early-access and uncensored route
If anybody wanted to, anybody could start a RLM SuperHighway84 where we could just talk about RLM stuff all day.
-
We need a community archiving effort for YouTube channels. What's most crucial to protect and how do we get organised?
SuperHighway84 - Is this handy for organization? I like the usenet-style where it sorts itself if people use proper newsgroup names. If people used a 'youtube.channelname' format at least people could maybe scroll down to channels/videos people are talking about.
-
How do you/we share the stuff we hoard so those looking for stuff find it?
In my mind something like superhighway84 would be a better platform, then it's automatically organizing itself to some degree if people post in appropriate newsgroups. People looking for lost youtubers could post in youtube.channelName. That person looking for old VCDs & screeners could post in vcds.screeners.
- We have to prepare ourselves for the possibility that Reddit might try to pull a Tumblr soon
-
Showing off your hoard?
SuperHighway84 is like a usenet style board where people can create whatever newsgroups they want. Anybody could start a 'Datahoarder' highway.
-
10+ years of Sumo GONE
I like the idea of something like SuperHighway84 for talking about our collections. We could make one called YoutubeGraveyard or something. There's also r/DHExchange
-
What do you guys think? (Using ChatGPT)
Have you heard of SuperHighway84?
What are some alternatives?
ipfs - Peer-to-peer hypermedia protocol
berty - Berty is a secure peer-to-peer messaging app that works with or without internet access, cellular data or trust in the network
web3.storage - DEPRECATED ⁂ The simple file storage service for IPFS & Filecoin
searxng - SearXNG is a free internet metasearch engine which aggregates results from various search services and databases. Users are neither tracked nor profiled.
gun - An open source cybersecurity protocol for syncing decentralized graph data.
go-orbit-db - Go version of P2P Database on IPFS
js-libp2p - The JavaScript Implementation of libp2p networking stack.
hubs - Duck-themed multi-user virtual spaces in WebVR. Built with A-Frame.
Gosora - Gosora is an ultra-fast and secure forum software written in Go that balances usability with functionality.
solid - Solid - Re-decentralizing the web (project directory)
awesome-ipfs - Community list of awesome projects, apps, tools, pinning services and more related to IPFS.