nielliesmons on Nostr: Now that we have Apps (kind 32267), the Application Handlers (Nip-89) thing becomes ...
Now that we have Apps (kind 32267), the Application Handlers (Nip-89) thing becomes silly. Since it makes more sense to specify the content types an App supports **in the App publication** than anywhere else.
With this you could go beyond just Nostr content handling.
š Supported content types: kind 9, kind 30023, mp3, PDF, ...
For recommending Apps, it also makes more sense to recommend the Apps themselves, instead of a (now redundant and confusing) application handler event.
Published at
2025-06-11 08:02:44Event JSON
{
"id": "36a228fbf692e2292d7b34755778080f2d62c0879dce2b26c14626caa23dae70",
"pubkey": "a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be",
"created_at": 1749628964,
"kind": 1,
"tags": [
[
"client",
"noStrudel",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"
]
],
"content": "Now that we have Apps (kind 32267), the Application Handlers (Nip-89) thing becomes silly. Since it makes more sense to specify the content types an App supports **in the App publication** than anywhere else. \n\nWith this you could go beyond just Nostr content handling. \nš Supported content types: kind 9, kind 30023, mp3, PDF, ...\n\nFor recommending Apps, it also makes more sense to recommend the Apps themselves, instead of a (now redundant and confusing) application handler event. ",
"sig": "98066f77bf5b75653d3a1bee20ca2b18817ba7dc285d6170cad66521515b3c9723c7e69f81be9b5bcb2603e003400c870dc3f783a321f3e42db32b674c5b6d39"
}
