# Subscribing to message type and src node ID

**URL:** <https://forum.opencyphal.org/t/subscribing-to-message-type-and-src-node-id/210>\
**Category:** LibCyphal\
**Created:** [October 22, 2018, 1:19pm UTC](https://forum.opencyphal.org/t/subscribing-to-message-type-and-src-node-id/210 "2018-10-22T13:19:55Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\
**Post date:** [October 22, 2018, 2:06pm UTC](https://forum.opencyphal.org/t/subscribing-to-message-type-and-src-node-id/210/2 "2018-10-22T14:06:14Z")

</div>

> [@deekay](#):
>
> Or does the subscriber application need to collect all messages of that type and then ignore all node id:s not interesting?

Yes, currently this is the only possible approach in UAVCAN v0. In the first stable release we’re currently working on (termed UAVCAN v1.0), the case you’re describing will be supported much better. Here is an overview: [Stockholm Summit recap](https://forum.opencyphal.org/t/stockholm-summit-recap/170)

---

_[View the full topic](https://forum.opencyphal.org/t/subscribing-to-message-type-and-src-node-id/210)._