PABLOF7z on Nostr: nostr:note1d8hgcwt0gj38tfgmxuqy2av9rwesk2c08j46d5pte69406ts8ezqxx5z8a Talking about ...
For a long time I didn’t realize Nostr wasn’t useful just for “social networking” things. I wonder what else could have been better designed in the relay-client interface if the needs of non-social-networking apps were kept in mind.
Talking about social-media vs non-social-media use cases for me sometimes feels weird.
Most of the stuff that nostr improves *is* social media, understanding that term as "things that benefit from a social graph". In that sense, i.e.
Zapstr (npub1zap…qhp9) is a social media client, it's just not focused on short-text as the main driver but rather songs and podcasts.
With that caveat out of the way:
yes, as a developer mostly focused on non-twitter-like interactions, often I find myself having to think around the design constraint of kind:1s being, well, #1. -- I don't think is a big deal, but would be nice if all use cases had mostly equal footing in the protocol.
Published at
2023-08-12 22:12:32Event JSON
{
"id": "cf4a1fc8d3bcc9c15e546a1ed4b97ffa16f6e169f03e9d516754deaa6d295b24",
"pubkey": "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52",
"created_at": 1691878352,
"kind": 1,
"tags": [
[
"q",
"69ee8c396f44a275a51b37004575851bb30b2b0f3caba6d02bce8b57e9703e44",
"quote"
],
[
"k",
"9802"
],
[
"e",
"69ee8c396f44a275a51b37004575851bb30b2b0f3caba6d02bce8b57e9703e44"
],
[
"p",
"1743058db7078661b94aaf4286429d97ee5257d14a86d6bfa54cb0482b876fb0"
]
],
"content": "nostr:note1d8hgcwt0gj38tfgmxuqy2av9rwesk2c08j46d5pte69406ts8ezqxx5z8a\nTalking about social-media vs non-social-media use cases for me sometimes feels weird.\n\nMost of the stuff that nostr improves *is* social media, understanding that term as \"things that benefit from a social graph\". In that sense, i.e. nostr:npub1zapstrdhq7rxrw224apgvs5ajlh9y473f2rdd0a9fjcys2u8d7cqzxqhp9 is a social media client, it's just not focused on short-text as the main driver but rather songs and podcasts.\n\nWith that caveat out of the way:\n\nyes, as a developer mostly focused on non-twitter-like interactions, often I find myself having to think around the design constraint of kind:1s being, well, #1. -- I don't think is a big deal, but would be nice if all use cases had mostly equal footing in the protocol.",
"sig": "34e41cbcf1d430cebcd165a253457537241d4d063fef61a336778dc37fb5d433ecc01f75fa141b0ae06b0fe832a23f9764709b7e5b13719932b02fa464e116a3"
}
