You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
JS moq-publish: Announce is required to be subscribed by moq-watch #5703
I don't have a test for this but it's trivial. Is this the expected behaviour. The publish broadcast and connection is set to enabled. However announcing is also required to be set to be subscribed. The subscriber with a specific name won't begin unless both enabled and announcing are active. If I disable announcing the subscriber won't begin playback. I tried setting announced="false" on the moq-watch element and it won't subscribe, I don't know what that setter is for.
So it seems to be expecting announcements to the relay. Is this the intention ? It might be a requirement to not announce a stream requiring manually setting the name. So the name doesn't show up on the relay.
Yeah so announcements are required otherwise the relay has no idea how to route a subscription. A broadcast.
The toggles are mostly in there because some IETF folks that haven't implemented announcements, or for apps that hard-code routing (ex. client always knows that server produces "foo/bar").
But yeah I think announcements should be required, at the very least as an "online/offline" indicator.
This is expected: if you never announce, the relay has no idea you are the publisher for that route. announce="never" can only work when a client and server pre-share the intent to publish a broadcast, and in @moq/publish the catalog is only created on the first announce, so it serves nothing.
Decision: delete announce="never" from @moq/publish. To keep a broadcast unlisted on the relay, use a hidden path: a .-prefixed segment is left out of announcement discovery but can still be watched by name.
Activity
kixelated commentedon Oct 19, 2026
Yeah so announcements are required otherwise the relay has no idea how to route a subscription. A broadcast.
The toggles are mostly in there because some IETF folks that haven't implemented announcements, or for apps that hard-code routing (ex. client always knows that server produces "foo/bar").
But yeah I think announcements should be required, at the very least as an "online/offline" indicator.
kixelated commentedon Oct 19, 2026
This is expected: if you never announce, the relay has no idea you are the publisher for that route.
announce="never"can only work when a client and server pre-share the intent to publish a broadcast, and in@moq/publishthe catalog is only created on the first announce, so it serves nothing.Decision: delete
announce="never"from@moq/publish. To keep a broadcast unlisted on the relay, use a hidden path: a.-prefixed segment is left out of announcement discovery but can still be watched by name.Tracked by
quest/m2/publish-announce-never.md.Planned in #5969. Anyone who wants to donate tokens can run
/quest-start quest/m2/publish-announce-neverto pick it up.(Written by Claude Opus 5.5)