[flagged]
Why do you want rarbg to die?
[flagged]
Show HN: Rarbg on IPFS
21–30 of 138 posts
Re: Show HN: Rarbg on IPFS
#22Earlier quoted context omitted.
That would hold true if IPFS would be a specific application. 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.
By default, what the GP says is true. If you can point to specific popular clients that do not have that behavior by default then I think that would be more convincing than saying "Well technically there's no requirement " when it's impossible to avoid in practice without writing your own custom implementation from scratch
Afaiu, [Lassie](https://github.com/filecoin-project/lassie/) is the latest and greatest of IPFS clients and it does not store/provide any data that you access
Re: Show HN: Rarbg on IPFS
#23[deleted]
These are magnet links directly to torrents.
Re: Show HN: Rarbg on IPFS
#24Look if you want to find isos to Linux (wink wink) off the web just use Usenet.
Re: Show HN: Rarbg on IPFS
#25A note of caution for those unfamiliar with how IPFS works. 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.
I think your post needs to clarify this is true only if you use the ipfs client to access things hosted on ipfs.
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.
Re: Show HN: Rarbg on IPFS
#26Looking for some recent (last week) content doesn't appear. What's the cutoff here for the DB?
Re: Show HN: Rarbg on IPFS
#27A note of caution for those unfamiliar with how IPFS works. 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.
I think your post needs to clarify this is true only if you use the ipfs client to access things hosted on ipfs. 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.
That's true, and I should have clarified that.
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.
Re: Show HN: Rarbg on IPFS
#28Re: Show HN: Rarbg on IPFS
#29A note of caution for those unfamiliar with how IPFS works. 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.
Using Brave it makes this very clear, the above link won't open by default without the user choosing to run a local node or use a public gateway instead. It explains the implications of both options.
Screenshot: https://i.imgur.com/ZP6AgPp.png
Re: Show HN: Rarbg on IPFS
#30How does it get updates?
Now IPNS is a thing. Months ago it just didn't work, at least for me, now something is happening in the way IPNS works.
IPNS kind of sucks but it’s “worked” for me for years. (sucks = very slow name resolution and slow update propagation, at least when I was using it a couple years ago)