# Take a look at pubsub on IPFS | IPFS Blog & News
**URL:** https://discuss.ipfs.tech/t/take-a-look-at-pubsub-on-ipfs-ipfs-blog-news/10755
**Category:** Blog Posts
**Created:** [April 8, 2021, 4:45pm UTC](https://discuss.ipfs.tech/t/take-a-look-at-pubsub-on-ipfs-ipfs-blog-news/10755 "2021-04-08T16:45:08Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@system](https://discuss.ipfs.tech/u/system)
#### Post date: [April 8, 2021, 4:45pm UTC](https://discuss.ipfs.tech/t/take-a-look-at-pubsub-on-ipfs-ipfs-blog-news/10755/1 "2021-04-08T16:45:08Z")
We recently merged a simple, experimental pubsub implementation into IPFS. This implementation is just a beginning. It is far from the performance and security goals we will achieve in our long-term target. However, even this early implementation opens the doors to several useful and interesting new applications.
* * *
This is a companion discussion topic for the original entry at [https://blog.ipfs.io/25-pubsub/](https://blog.ipfs.io/25-pubsub/)
---
### Author:  [@idkwhatmyuseris](https://discuss.ipfs.tech/u/idkwhatmyuseris)
#### Post date: [July 28, 2025, 9:21pm UTC](https://discuss.ipfs.tech/t/take-a-look-at-pubsub-on-ipfs-ipfs-blog-news/10755/2 "2025-07-28T21:21:39Z")
Will pubsub ever get custom validation hooks, rather than just keys on who can write to the topic. This way you could have more complex systems run on pubsub, with finer-grained control over what the protocols allow.
```javascript
await libp2p.services.pubsub.registerTopicValidator(
'my-topic',
msg => function(){
return signature_matches(msg) && validtimestamp(msg) // etc
}
)
```
This would make it easier to prevent spam on public pubsubs, where anyone can write.
---
### Author:  [@system](https://discuss.ipfs.tech/u/system)
#### Post date: [July 28, 2025, 9:21pm UTC](https://discuss.ipfs.tech/t/take-a-look-at-pubsub-on-ipfs-ipfs-blog-news/10755/3 "2025-07-28T21:21:39Z")