Closed
Description
The web app and documentation should advocate for all topics that aren't "well known names" to have high entropy components. Common cryptographic wisdom is that a 2^-32 event is "not going to happen", so by the birthday bound the appropriate level of entropy is (32 + log2(num_topics_created)) * 2 bits.
64 bits / 6 bits per base64 character = 10.6 characters of base64 (minimum recommendation: 11)
96 bits / 6 bits per base64 character = 16 characters of base64 - sufficient for servers with 65k random topics
128 bits / 6 bits per base64 character = 21.3 characters of base64 (reasonable maximum recommendation: 21)
- The web app "Subscribe to topic" dialog should include a button to append a hyphen and 16 base64 characters to what's already typed in the dialog box.
- https://ntfy.sh/docs/publish/ should say "Pick something with about 96 bits of entropy (16 base64 characters)" instead of "that's not easily guessable" and an interactive component to generate one in the browser.