The text describes a workflow involving two events, `kind:31989` and `kind:31990`, which are used to recommend an application that can handle a specific event kind and redirect users to it respectively. The recommended app's details are included in the `kind:31989` event as tags, while the redirect is advertised by applications through `kind:31990`. The `kind:31990` event includes a `k` tag with the supported event kind(s) and a URL for the application to load. The URL contains a `bech32` value that should be replaced by clients with the NIP-19-encoded entity that should be loaded by the application. Multiple tags might be registered by the app, following NIP-19 nomenclature as the second value of the array. A tag without a second value in the array SHOULD be considered a generic handler for any NIP-19 entity that is not handled by a different tag.

For example, User A might recommend Zapstr as a `kind:31337`-handler by publishing an event recommending Zapstr as

Link: https://github.com/nostr-protocol/nips/blob/master/89.md