Is a default content topic really necessary?

[D4nte]

Looking at the JS-Waku API, I have made the content topic optional so that if it is not passed, it default to /waku/2/default-content/proto.

Getting more famliar with Waku, I question this choice.

• Do we really need a default content topic?
• What kind of content do we expect on the topic?
• Should we instead force developers to get famliar with topics so they have to choose a content topic?

[jm-clius]

I agree with you. Now it's clearer how content topics must be used by applications it should probably become a mandatory field on the API.

In general, this is already what we do for the nim-waku API. It's only in the JSON-RPC API where the content topic is still optional.

[oskarth]

Agree, don't really need it. Mostly for chat2 dogfooding but that is separate now

[oskarth]

Generic message follows

I'm going to go ahead and close this discussion as:

1. It is quite old and we are moving away from GH discussions (in favor of either forum.vac.dev or normal issues)

2. Existing discussion has evolved and is captured in more targeted issues already

If you feel like this is in error, please create a thread on Vac forum or a new issue.