torrent-paradise
orbitdb
torrent-paradise | orbitdb | |
---|---|---|
15 | 32 | |
407 | 8,127 | |
- | 0.6% | |
0.0 | 9.2 | |
4 months ago | 11 days ago | |
JavaScript | JavaScript | |
- | 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.
torrent-paradise
-
Ask HN: I've Built a DHT Torrent Sniffer and Search Engine. Should I Release?
There’s also this which has since gone down but remains up on IPFS and its index hasn’t updated since January…
https://github.com/urbanguacamole/torrent-paradise
https://cloudflare-ipfs.com/ipfs/QmQjsKamNFZRvCMXDvZXQmRYjsm...
-
Torrent Paradise 2.0 is dead
For what its worth the source code is still up if anyone wants to create a new site using the code https://github.com/urbanguacamole/torrent-paradise
- I made a decentralized torrent search site with IPFS
-
Any replacement for Torrent Paradise ml ?
For years after we missed torrentz.eu, torrent-paradise.ml was my best torrent search engine. Clean, powerful and uptodate. Sadly it is disabpear in mid january 2022 for reason that I don't know. I'm wondering if there is any clone/alternatives, as the source code is available here
-
Please seed a backup of Torrent Paradise
The code and instructions are still at https://github.com/urbanguacamole/torrent-paradise
-
Database-Less Torrent Website
related: https://torrent-paradise.ml/ Also based on IPFS with this HTTP gateway. I find a lot of torrents in there.
-
Torrent Search Engines
Torrent Paradise
-
Did they really thought we will pay for all of this
I'm only on private, invite only torrent sites right now, so I'm not much help with regard to public trackers. I do have https://torrent-paradise.ml/ bookmarked which seems to be an aggregator of many other trackers.
- Privacy using our Tor-inspired onion routing
-
Please add Torrent Paradise in Synclers provider packages...
It would be great to add this very interesting and valuable torrent site in already awesome provider packages for Syncler. Here is the link for the site https://torrent-paradise.ml/
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?
Magnetico - Autonomous (self-hosted) BitTorrent DHT search engine suite.
ipfs - Peer-to-peer hypermedia protocol
tribler - Privacy enhanced BitTorrent client with P2P content discovery
web3.storage - DEPRECATED ⁂ The simple file storage service for IPFS & Filecoin
torrenthistory-public
gun - An open source cybersecurity protocol for syncing decentralized graph data.
i2p.i2p - I2P is an anonymizing network, offering a simple layer that identity-sensitive applications can use to securely communicate. All data is wrapped with several layers of encryption, and the network is both distributed and dynamic, with no trusted parties.
js-libp2p - The JavaScript Implementation of libp2p networking stack.
passerby - Peer-to-peer location services for the decentralized web -- discover what's around you, no central authority required
berty - Berty is a secure peer-to-peer messaging app that works with or without internet access, cellular data or trust in the network
torrent-net - Distributed search engines using BitTorrent and SQLite
solid - Solid - Re-decentralizing the web (project directory)