Show HN: Rarbg on IPFS
ipfs.io
ipfs.io
FYI, this dump has 826'201 magnets (torrents) with an associated imdb ID and 2'017'490 without, including lots of porn but also random music and software.
Category breakdown (careful though, most items aren't categorized or use a category code I couldn't interpret):
XXX ( 1): 2,255
XXX ( 4): 607
Movies (14): 3,206
Movies (17): 117,440
TV (18): 198,314
Music (23): 11,621
Music (24): 471,161
Music (25): 1,339,739but not all
I have a question for you as even playing with this or creating oss project using this sounds like inviting trouble. So if any programmer wants to create an open source project using this data (just for kicks) then apart from using a VPN and throwaway email do you need to be careful about anything else? Any tips?
Can ask dang to remove
Is there any incentive for nodes to do so?
Is it possible to see a statistic about how many nodes mirror it?
What do you mean with "torrents work fine"? Do you have any statistics on the lifetime of torrents?
Everything ever written to the Bitcoin blockchain is still available and massively distributed. It seems very unlikely anything will ever get lost during our lifetime. So I would say that is an example that monetary incentives do work?
This isn't useful for 99% of stuff and pushing every video and music file on earth through a global state machine with the performance characteristics of an Atari from the 80s would render the thing inoperable. The entire Bitcoin network has a bandwidth of like 1mb every 10 minutes, the total size of the blockchain is half a TB in total, people torrent more porn in the time it took me to type this.
Maintaining a global, complete history of transactions only ever made sense for one problem, double spending, and is utterly useless for sharing files.
but nobody said otherwise
Lol no... I dont like interviewing for a new job, why would i agree to get tested for something as stupid as piracy? (Unless... mention me ONE private tracker that doesn't have piracy).
So for 99% of people, my point stands.
There are definitely private trackers that don't have anything like that though (iirc they're called "semi-private trackers"). One i remember using is t411 when it was still running
Disclaimer: I wrote that article and was somewhat involved in the other sqlite over ipfs project this is forked from.
Yes, for MB size files just downloading the whole thing will be faster and much easier - even if running in the browser. I'd say the boundary is somewhere around 10MB compressed (~20-200MB uncompressed). Looks like the sqlite dump used here is ~400MB in size, ~180MB compressed. Loading that in the browser would probably work but it wouldn't be too great.
As I understand it, the purpose of using SQLite is indexing and querying, ie. being able to efficiently search through the data via a website.
The HTTP part is also not censorship-resistant. ipfs.io has a DMCA process, and they could also be asked to reveal the IP of users.
In practice it's very rare for me to see a direct ipfs protocol link, almost all the traffic goes through HTTP gateways (which frequently cache the content as well). Hard to imagine that they don't become a target for "hosting" pirated content if / when IPFS becomes more than a negligible platform for piracy. (A significant amount of Library Genesis traffic is already using IPFS via these same gateways.)
As you mention, there's a DMCA process for some of the gateways, but that might not be enough to ward off attention.
It's very similar to BitTorrent with how content distribution happens. Your local node will broadcast which content it has available (downloaded).
If you access a piece of content you automatically become a host for it so you still need to use a VPN if you live in a country where you can get sued.
If you access a piece of content over ipfs.io for example, I would think you just make https requests like to every other website.
But it is a protocol.
I would not expect that the protocol specifies that a complient client shares what it downloaded. That sounds more like a choice the client developers make on their own.
But I'm happy to be corrected if someone has a link to the protocol definition and it says different.
If my understanding is correct, it can't be considered a complete IPFS client.
https://docs.filecoin.io/storage-provider/architecture/netwo...
There's an entire cottage industry of IPFS pinning and gateway providers that exist largely because of the challenges of running your own IPFS node for anything beyond casual use.
Accessing ipfs.io/ipfs/ doesn’t do anything you mentioned. Its just a gateway.
You could take the link on the main submission. And replace ipfs.io with any (most, because some are offline) of the links here https://ipfs.github.io/public-gateway-checker/
And it will still work.
However, is using a proxy like ipfs.io really using ipfs?
If everyone did that, there's no point to using this protocol. The strength of the network comes from the fact that the content gets replicated/distributed when accessed. That doesn't happen when accessed through a proxy.
Yes! Because the gateway can go down and you can still access the content via local IPFS node or by using another gateway.
Screenshot: https://i.imgur.com/ZP6AgPp.png
1. Has at least 20 results
2. None of the first 20 results is porn content
I even tried with Math and Chess. No dice.
That was my second attempt, I tried "physics" first but oh boy was I naive.
Very cool, but does ipfs support verification of partial reads like this? (or would I need to download the whole DB and check the hash?)
I can think of some ways it could work using merkle trees or similar, but I have no idea what ipfs does under the hood, if anything.
However with local ipfs, bitswap doesn't support range requests, so you're at least downloading the enclosing blocks which could be 2 MiB for 1 KiB requested data, or 2000X more data than you need.
Got a message from the cybersecurity team being like, "pls don't do that". Thanks HN.
Pretty cool though, interested in how IPFS develops in the future.
IPNS is essentially DNS over the IPFS network. IPNS domains point to a specific IPFS file (or a set of files, like we see here). IPNS domains are signed with a private key; when you want to update your IPNS entry, you add your new content to a new IPFS file and then you update the IPNS entry by signing it with a public key.
[0] "RARBG Torrent Files (QUICK SORTED) [v0.1].7z"
I live in Germany, and they are pretty harsh when it comes to downloading.
I opened this up while browsing HN without knowing what it was....
See: - https://docs.ipfs.tech/how-to/address-ipfs-on-web/#subdomain... - https://specs.ipfs.tech/http-gateways/subdomain-gateway/
Fuck yeah <3
"DB worker could not be created
TypeError: second argument must be a function"
edit: the "Getting Started ->" is actually a dropdown.
There is a lot of weird pornographic films with "Blackberry" in the name.
Currently RARBG primary domain is:
https://rarbg.to (actually links to https://rargb.to, note the bg/gb) echo "magnet:?xt=urn:btih:${info_hash}"
ipfs basically feels like "this is it guys, our entire access pattern is going to be this"The trackers are outside of info section, I assume so the list of trackers can be modified without effecting the info hash.
Though, some magnet links include an optional xs parameter which points at an http url containing the .torrent file, which would include the trackers.
In my experience, you don't receive the trackers from other peers (though maybe other bittorrent clients can?). However, if at least one peer you discover via DHT supports the peer exchange protocol, and has the trackers, your client can quickly query all the relevant peers.
Please don't do that with the non-static data. This is okay only for archived project, except the moment when my PC downloads SQLite indexes from some blockchain based paifully slow storage for the first time. BTW, how about a user-governed local data cache, is there any recent quirks in browsers for that? LocalStorage is still inconsistent and unreliable, right?