# State of IPFS PubSub

**URL:** <https://discuss.ipfs.tech/t/state-of-ipfs-pubsub/8032>\
**Category:** Help\
**Created:** [May 20, 2020, 1:41am UTC](https://discuss.ipfs.tech/t/state-of-ipfs-pubsub/8032 "2020-05-20T01:41:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pineappleman](https://avatars.discourse-cdn.com/v4/letter/p/a5b964/32.png) [@pineappleman](https://discuss.ipfs.tech/u/pineappleman)\
**Post date:** [May 20, 2020, 1:41am UTC](https://discuss.ipfs.tech/t/state-of-ipfs-pubsub/8032/1 "2020-05-20T01:41:55Z")

</div>

I was wondering if the IPFS pubsub feature is still considered an experimental feature. I understand OrbitDB is built on top of it and AvionDB is built on top of that. So is the Pubsub feature stable enough to build applications on top of it or is the protocol still subject to change in a breaking manner?

---

<div class="post-metadata">

**Author:** ![zicmama](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/zicmama/32/3722_2.png) [@zicmama](https://discuss.ipfs.tech/u/zicmama)\
**Post date:** [May 20, 2020, 3:46pm UTC](https://discuss.ipfs.tech/t/state-of-ipfs-pubsub/8032/2 "2020-05-20T15:46:44Z")

</div>

I have the same question as you…

I am actually activating “pubsub gossip mode” like that:

```auto
ipfs config Pubsub.Router gossipsub

```

```auto
ipfs daemon --enable-pubsub-experiment --enable-namesys-pubsub 

```

Is it still relevant to do so with ipfs 5.0.1 ?

---

<div class="post-metadata">

**Author:** ![zicmama](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/zicmama/32/3722_2.png) [@zicmama](https://discuss.ipfs.tech/u/zicmama)\
**Post date:** [May 20, 2020, 7:28pm UTC](https://discuss.ipfs.tech/t/state-of-ipfs-pubsub/8032/3 "2020-05-20T19:28:21Z")

</div>

interesting revelations

[![](https://us1.discourse-cdn.com/flex020/uploads/ipfs1/original/2X/7/7ab2932787c477f1aa38eb04b468fbb138ccf5eb.jpeg "go-IPFS 0.5 Updates - Steven Allen") ](https://www.youtube.com/watch?v=S8a1xzdWjN0)

---

<div class="post-metadata">

**Author:** ![pineappleman](https://avatars.discourse-cdn.com/v4/letter/p/a5b964/32.png) [@pineappleman](https://discuss.ipfs.tech/u/pineappleman)\
**Post date:** [May 21, 2020, 5:48am UTC](https://discuss.ipfs.tech/t/state-of-ipfs-pubsub/8032/4 "2020-05-21T05:48:28Z")

</div>

The closest thing I could find in regards to this is coincidentally a post from today in regards to updates to gossipsub:

[http://blog.ipfs.io.ipns.localhost:8080/2020-05-20-gossipsub-v1.1](http://blog.ipfs.io.ipns.localhost:8080/2020-05-20-gossipsub-v1.1)

Non-IPFS link: [Gossipsub v1.1 brings hardening extensions to PubSub](https://discuss.ipfs.tech/t/gossipsub-v1-1-brings-hardening-extensions-to-pubsub/8037)

---

<div class="post-metadata">

**Author:** ![stebalien](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/stebalien/32/156_2.png) [@stebalien](https://discuss.ipfs.tech/u/stebalien)\
**Post date:** [May 22, 2020, 2:55am UTC](https://discuss.ipfs.tech/t/state-of-ipfs-pubsub/8032/5 "2020-05-22T02:55:39Z")

</div>

A new version of the underlying pubsub protocol will be included in 0.6.0. However, we aren’t yet going to enable it by default, unfortunately.

> <https://github.com/ipfs/go-ipfs/issues/6621>
>
> In js-ipfs we're integrating gossipsub and moving pubsub out of "experimental" status. There are some changes we want to make to...