71–80 of 156 posts
IPFS still has a long way to go until it is useable in my opinion. The default configuration for the desktop client will gladly keep open 1000+ peer connections and will happily degrade your usual internet experience. In addition the ecosystem is filled with technical/community debt that makes navigating the system a nightmare for anyone who isn't an expert. As an example: https://github.com/ipfs/go-ipfs/issues/1482…
Hey IPFS person here. We actually made a change to ipfs-desktop back in Feb of last year to reduce the default connection limit to ~300 ( https://github.com/ipfs-shipyard/ipfs-desktop/pull/828 ), and also to set desktop nodes into DHT-client mode (so they don't get lots of requests from other nodes for where to find content). If you've been running your node since back then, you can change your defaults in the deskto…
I love the idea of IPFS, but let me ask you the question, when is it finally going to be ready for people to easily deploy? A year from now, 3 years, 5 years? Or maybe you have no idea?
Don't give some vague answer about how you are working on it. Give me a reasonably specific prediction, or say you have no idea.
If you replace the word "IPFS" with "BitTorrent," this article is still true. Similarly, if you replace "IPFS" with "BitTorrent" in most of the comments here, the comments are still true. If you understand how BitTorrent works -- including its strengths and limitations -- you'll understand how IPFS works.
Minor nit: BitTorrent does not allow one to maintain a persistent URI to changing/updated data, as IPNS does.
If you replace the word "IPFS" with "BitTorrent," this article is still true. Similarly, if you replace "IPFS" with "BitTorrent" in most of the comments here, the comments are still true. If you understand how BitTorrent works -- including its strengths and limitations -- you'll understand how IPFS works.
Minor nit: BitTorrent does not allow one to maintain a persistent URI to changing/updated data, as IPNS does.
Stopped reading after "Medium's engineers are much better at all of this than you will ever be"; can't take this writer seriously.
"I struggle, you struggle, (thus) we relate!"
I blame it on the spirit that being last in school is way cooler than being first, and I suspect it's as old as humanity.
Stopped reading after "Medium's engineers are much better at all of this than you will ever be"; can't take this writer seriously.
Earlier quoted context omitted.
Minor nit: BitTorrent does not allow one to maintain a persistent URI to changing/updated data, as IPNS does.
Depending on how you measure it: RSS feeds for updates fit this bill, and they've been around for a decade or more: https://github.com/KDE/ktorrent/blame/3ce105f4d1c3b4c178aaf3...
Earlier quoted context omitted.
Depending on how you measure it: RSS feeds for updates fit this bill, and they've been around for a decade or more: https://github.com/KDE/ktorrent/blame/3ce105f4d1c3b4c178aaf3...
RSS feeds are centralized and rely on web servers and DNS and are thus straightforward to censor or otherwise force offline via government orders, ddos, provider legal threats, et c.