/ipfs/ - IPFS thread

Why did you make a new thread? The old one was fine >>771999

You have no clue what you're talking about. The only non-backwards compatible change they made was in April 2016 when they released 0.4.0. Since then all changes have been backwards compatible with new releases.

It had no image.

Launch it with
ipfs daemon --routing=dhtclient
to reduce the amount of connections it uses.

Additionally, some progress has been made limiting the extent of the problem, though the issue of closing connections doesn't appear to be touched yet.

Issues to watch on this subject:
github.com/ipfs/go-ipfs/issues/4029
github.com/ipfs/js-ipfs/issues/962

If you're going to make a new thread, at least post some updates.

js-ipfs 0.26 Released
blog.ipfs.io/30-js-ipfs-0-26/

New InterPlanetary Infrastructure
>You might have noticed some hiccups a couple of weeks ago. That was due to a revamp and improvement in our infrastructure that separated Bootstraper nodes from Gateway nodes. We’ve now fixed that by ensuring that a js-ipfs node connects to all of them. More nodes on github.com/ipfs/js-ipfs/issues/973 and github.com/ipfs/js-ipfs/pull/975. Thanks @lgierth for improving IPFS infra and for setting up all of those DNS websockets endpoints for js-ipfs to connect to :)

Now js-ipfs packs the IPFS Gateway as well

Huge performance and memory improvement
>With reports such as github.com/ipfs/js-ipfs/issues/952, we started investigating what were the actual culprits for such memory waste that would lead the browser to crash. It turns out that there were two and we got one fixed. The two were:

>>browserify-aes - @dignifiedquire identified that there were a lot of Buffers being allocated in browserify-aes, the AES shim we use in the browser (this was only a issue in the browser) and promptly came with a fix github.com/crypto-browserify/browserify-aes/pull/48 👏🏽👏🏽👏🏽👏🏽

>That said, situations such as github.com/ipfs/js-ipfs/issues/952 are now fixed. Happy file browser sharing! :)

Now git is also one of the IPLD supported formats by js-ipfs

The libp2p-webrtc-star multiaddrs have been fixed

>You can learn more what this endeavour involved here github.com/ipfs/js-ipfs/issues/981. Essentially, there are no more /libp2p-webrtc-star/dns4/star-signal.cloud.ipfs.team/wss, instead we use /dns4/star-signal.cloud.ipfs.team/wss/p2p-webrtc-star which signals the proper encapsulation you expect from a multiaddr.

New example showing how to stream video using hls.js
>@moshisushi developed a video streamer on top of js-ipfs and shared an example with us. You can now find that example as part of the examples set in this repo. Check github.com/ipfs/js-ipfs/tree/master/examples/browser-video-streaming, it is super cool 👏🏽👏🏽👏🏽👏🏽.
>HLS (Apple’s HTTP Live Streaming) is one of the several protocols currently available for adaptive bitrate streaming.

webcrypto-ossl was removed from the dependency tree

PubSub tutorial published
>@pgte published an amazing tutorial on how to use PubSub with js-ipfs and in the browser! Read it on the IPFS Blog blog.ipfs.io/29-js-ipfs-pubsub.

do ipfs still use the ipfs (((package))) app that
throws away the cryptographic integrity of git?

do ipfs still use the ipfs (((package))) app that
throws away the cryptographic integrity of git?

NixOS will have IPFS as well WEW

this is nice but i can do without the pedoshit links

Call us when it can use both i2p/tor. Until then, it's inferior to bittorrent for filesharing. Why? Because the only client availables (github.com/Agorise/c-ipfs isn't ready enough) are in GC using retarded langages.

They're working on it. c-ipfs seems promising as well.