/ipfs/ - IPFS Thread #2

░░░░░░▒▒▓▒▒▓▒▓▒▒▒█████████████████████████████████████████████▓▓▓▓
░░░░░░▒▓▒▓█▓▒▒▓▒▓██████████████████████████████████████████████▓▓▓ >muh private file sharing
░░░░░▒▓▒██▓▒▒██▓▓██████████████▓▓▓▓▓▒▒▒▒▒▒▒▒▓▓▓▓████████████████▓▓ IPFS is for content distribution. If you don't want it
░░░░▒▒▓███▒▓█████████████████████████████████▓▓▓▒▒▒▒▒▒▒▓▓▓██████▓▓ to be public, don't bother using IPFS. Use SFTP or
░░░▒▓██▓█▓▓█████████████▒██████████████████████████████▓▓▒▒▒▒▒▒▓▓▓ something like that.
░░▒███▒████████████████▒▒▓████████████████████████████████████▓▓▓▓
░▒▒█▓▒███████████████▓▒░░▒████████████▓▓████████████████████████▓▓ >shitty meme software written in javascript and go (((Google)))
▒▒██▒▒███████████▒██▒░░░░▓████████████▒▓█████▒██████████████████▓▓ IPFS is a protocol. As long as the protocol is implemented
▒▒█▒▒▓██████████░██░░░░░░░░██████████▒▒░████░▒▓██████████████████▓ correctly, I don't give a shit about what language it is
▒█▓▒▒██████████░▒▒░░░░░░░░░▓████████▒▒░░▓██▒░▒▓██████████████████▓ written in unless I have to write code which interfaces with
▒█▒▒▒█████████░░░░████████░░███████▒▒░░░░██░░░░▓█████████████████▓ it. Google has nothing to do with IPFS.
▒█▒▒▓████████▓░░░░██████░░░░▒█████▓░░▒▒███████▓▒█████████████████▓
▒█▒▒█████████▒░░░░█████▓░░░░░▓████░░░░░██████░░░▓███████████████▓▓ Torrents don't have content-addressability. Webpages can't be
▒▓▒▒█████████░░░░░█████▒░░░░░░███░░░░░▒██████░░░▓███████████████▓▓ conveniently hosted on a torrent. Torrents reveal your IP
▓▓▒▒▓████████░░░░░▓██▓█░░░░░░░░▓▒░░░░░▒█████▓░░░████████████████▓▓ to everyone who is uploading or downloading from you.
▒▒▒▒▒████████░░░░░░░░░░░░░░░░░░░░░░░░░▒█████░░░░████████▒░██████▓▓
▒▓▒▒▒▓███████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░██████▓█▒░██████▓▓
▒▓▒▒▒▒▓██████▒░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░▒██████▒█▓▒██████▓▓
▒▓▒▒▒▒▒▓█▓████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░▓██████▒░████████▓▓
▒▒▒▒▒▒▒▒█▒█████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░▓█████▒▒█████████▓▓
▒▒▒▒▒▒▒▒▒▓▒██████▓░░░░░░░░░░░░░░░░░░░░░░░░░░░░░▓████████████████▓▓
▒▒▒▒▒▒▒▒▒▒▓███████▓░░░░░░░░░░░▒▒▒▒░░░░░░░░░░░░░█████████████████▓▓
▒▒▒▒▒▒▒▒▒▒▓██████████▓░░░░░░░░░░░░░░░░░░░░░░▓███████████████████▓▓
▒▒▒▒▒▒▒▒▒▒▓████████████████▓▒░░░░░░░░░▒▓████████████████████████▓▓
▒▒▒▒▒▒▒▒▒▒▓██████████████████▓▒▒▒▒▒▒▒███████████████████████████▓▓
▒▒▒▒▒▒▒▒▒▒▓█████████████████▒▒▓▓▒▓▒▒▒▒▓████████████████████████▓▓▓
▒▒▒▒▒▒▒▒▒▒▓██████████████▓▓█▓▓███▓▓▒▒▓▓▓▓██████████████████████▓▓▓
▒▒▒▒▒▒▒▒▒▒▒████████▓▒▓▓▓▓▓▓█████████████▓▓▓▓███████████████████▓▓▓
▒▒▒▒▒▒▒▒▒▒▒█████▒▒▒▒▒▓▓▓▓▓▓▓▓▓████████▓█▓█▒▒▒▒█████████████████▓▓▓

You have no idea how torrents work. Thats what a magnet link does for the DHT.
We live in a society
Oh shit I should only use this tool if I want to share it with everyone! Fuck sharing among friends or using it in a company. Really this lack of a basic feature is a good thing.
I can use I2P and shit with torrents. Not with IPFS.
I'm sure their javascript is perfect

Attached: DZZKxxSUMAAzDGF.jpg (610x349, 29.72K)

...

Magnet links contain the hash of the torrent file itself, not the actual contents of the torrent.
But webtorrent is javascript and according to you javascript is bad. Serving IPFS over the web doesn't require the use of any javascript anywhere.
Yes.
Actually you can use IPFS to share private information. Just be sure to encrypt it first.
You can use IPFS through tor, I believe.
Use the Go implementation then.

Attached: 9a4f9c230d8f17b04d3aa6ac23d23de6cddaf8b9e741c32d8d629b5c93e9e824.png (432x429, 237.37K)

Why the fuck do you think that is a response. You said:
That is exactly what a magnet is.
Or they could implement basic access controls. Having to encrypt everything would be a massive PITA making the whole easy filesystem part worthless.
Its been "in development" for years.
Yep, thats why I don't use it or any of the web shit.

Attached: DZgsLTVVMAEtvjM.jpg (960x960, 54.34K)

The magnet allows you to address the .torrent file. It does not allow you to address the content (i.e. what you want to download), whereas IPFS does.
And how are they going to do that? How are they going to identify who has access to the file besides by using a password? If they did that you might as well use encryption from outside IPFS, which is simpler and more secure.
You can use IPFS gateway through a hidden service. However, yes it is true that the IPFS daemon itself can't be run through Tor without deanonymization.
This is still better than torrents, which can't be run through Tor at all.
The language being invented by Google isn't a reason not to use all software programmed in it. It's a compiled language so it's all the same in the end.
You can't use webtorrent, but you can use IPFS (through the gateway) without using any javascript.

Again this is just wrong.
Via the node key they already generate for authentication purposes. Or a password.

You've fucking run out of arguments now.
so they would need to send me a long ass public key, instead of telling them a simple password? nice "solution" you got there.
You can download stuff from IPFS through tor. This is a fact and you can't ignore that. That is already better than torrents.
Now you've run out of things to say. The Go compiler is free software. Many people from non-google backgrounds work on it. The fact that the best implementation of IPFS is written in Go doesn't affect you in any way whatsoever, unless you are working on the code, because it's a compiled language which generates static executables.

Nice try anime poster. He cries out as he strikes you.
Nice way to cut off that quote