# Current status of js-ipfs web and go-ipfs interop

**URL:** <https://discuss.ipfs.tech/t/current-status-of-js-ipfs-web-and-go-ipfs-interop/4610>\
**Category:** Help\
**Tags:** js-ipfs\
**Created:** [January 4, 2019, 3:30am UTC](https://discuss.ipfs.tech/t/current-status-of-js-ipfs-web-and-go-ipfs-interop/4610 "2019-01-04T03:30:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![reconbot](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/reconbot/32/1608_2.png) [@reconbot](https://discuss.ipfs.tech/u/reconbot)\
**Post date:** [January 4, 2019, 3:30am UTC](https://discuss.ipfs.tech/t/current-status-of-js-ipfs-web-and-go-ipfs-interop/4610/1 "2019-01-04T03:30:59Z")

</div>

I’ve been playing with js-ipfs and have been quite enjoying it. I notice however, when running it in a web browser and in the go cli, If I pin a file one place it’s not visible from the other. For example I have [this](https://gateway.ipfs.io/ipfs/QmXbP2smaKe5QLzZyMrdchHmxdDFVrfRJmS5DLWNcQ85g9) pinned in go-ipfs and it’s found without issue, but not by js-ipfs. But [this](https://gateway.ipfs.io/ipfs/Qmf2Lf9VXyacGfKrSh5Gg4nfwT8azu5dFyA6JmNVChsAZv) is pinned in my browser with js-ipfs only and it can’t be found via go-ipfs.

_update_: looks like eventually both can be accessed from both locations, there’s obviously some discovery delay or something. I’m still curious what the interop story is, and what we’re exited about for js-ipfs to land in the future.

Thanks!