This TBH github.com
/ipfs/ - IPFS Thread #3
Mason Stewart
James Jenkins
After seeing
I take back what I said here
What I should have said was, we shouldn't diverge into language wars. It's not really critical to the concepts and can change at any time if people find enough merit in the concept, to warrant the effort of implementing it.
No Jai, no buy. Obvious trash.
Liam Sanchez
Ah, you have no respect for security or privacy.
Seems you've never installed your own tracker.
I don't sell projector screens.
What's your github account? I don't use Social Networks, esp. Microsoft ones.
I'm fine libtorrent.org
Sell me IPFS when we're making history:
en.wikipedia.org
Ryan Thomas
I get the impression you're being insincere for the sake of attention and are not actually interested in discussing this. Maybe you should use social media instead of trying to do that here. Or try /g/.
Aiden Price
Renaming a filename without changing the hash is disrespecting your security and privacy?
Gavin Wright
Renaming a file*
Caleb Cooper
How is swarm merging in concept a breech of security or privacy?
Security is completely irrelevant and privacy can be maintained in the same way you would if swarms where not merged. It's exactly the same as BT except automated.
If you want privacy, use anonymous routing or a private network.
What do trackers even have to do with this and what protocol are you even talking about? KAD, Bittorrent, and IPFS all use DHT for this, not trackers. Merging is handled clientside for all.
IPFS seems to have actual implementations for a lot of these concepts. What are you trying to say by posting an advertisement to a conceptual "Future internet".
If something does come out like that, what difference would it make since it's content addressed? All the IPFS developers would need to do is figure out a way to resolve NDN hashes and fetch content from their nodes. That's the whole point of IPLD
There are already implementations to add support for native hashes of various other formats and networks.
github.com
I'm not really confident in some research project that hasn't yielded anything since 2006 suddenly being relevant.
As for IPFS you can already work with git commits over HTTP, and ethereum blocks over whatever their network is. And Bittorrent is on their planned list.
I love the idea of having 1 program handle all my hashes/magnets. It's much better than having multiple different clients open, connected to multiple different networks independently.
If I request data, I want the program to get that data, through any means, over any network ,using whatever URN is considered optimal that day.
The whole benefit of IPFS is that these things can change.
How routing is done, what hash algorithm is used, what chunking method is used, what encryption method is used, what transport is used, etc. but the interface stays the same "ipfs get URN", "ipfs add ~/dont_click/boku_no_pico.xvid"
Maybe someone sent you a bittorrent hash and they're only hosting over i2p, the IPFS program should eventually be able to resolve that. Maybe a fork already does.
What's so great about NDN and why should I wait more decades for it when this exists today?
Charles Scott
Full automation: misleading bit, download the whole repo.
You want semi automation, the more you can control the better, even if it runs mostly by itself.
Yeah, I concluded from you as much.
A windmill is also automated. Does it work like a windmill?
Does it not need my intervention if I made the typo?
A lot. It's what you are claiming trackers don't have: a way to publish updates, even for typos.
We have prototypes, empirical evidence, and scientists working on this. Not hobbyists that wrote a thesis paper.
named-data.net
named-function.net
Nodev, got it.
It's ok to ignore the 10 years worth of work in CCN, and working implementations.
Reminds me ZeroCoin.
Be sure to run it in ring 0, so you can't expect any breaches.
This is the systemd of statements.
The same question Linux have in Desktop adoption, and display server support: lack of support.
Bittorrent works here and now, and a proven solid track record, while IPFS still begs to complete it's not so sound ideals.
It's snake oil, and you don't even see it.
Eli Gonzalez
IPFS already has the openBazaar fork with TOR/I2P but it has not been mainlined as the development is slow as shit.
Joseph Evans
Yeah, that's what I thought of IPFS when it was announced, and thanks to you, even more refined.
Anything IPFS says it wants to do, Bittorrent software already provides, and more.
But we're done with conversation Nodev.
In the next ten years, we'll see Bittorrents on post quantum crypto, making it impossible to spy and tamper, unneeding TOR & I2P.