That’s on the clients. They’re currently just migrating successful app structures; Twitter, insta, etc. Imagine when they truly embrace the capabilities of having a protocol that can access all content types and deliver convenient and diverse UX and use cases for users based on how the user sets that they want to engage with the content of each type.
For example. Maybe I have primal as it is, but with Olas image content added, I configure settings to just throw a 9-up tile of the 9 most recent Olas images of each user I follow into my main feed each day. If I engage with it, it’ll either take me to my Olas image content type feed in Primal or in Olas or to that user’s image feed specifically.
Or maybe Olas images that correlate with an event content type that is happening within 10 miles of me (see my NIP-G0 draft in github) gets an in-app notification for me because I hate blanking on cool stuff going on in town that I would have gone out to enjoy.
There’s so much more potential than cloning existing centralized app functionality. We don’t have a grid of walled gardens any longer. It’ll take devs time and experiments to expand the clients to capitalize on the capabilities.
SwBratcher
npub1gk…cyk5m
2025-02-12 19:33:11
in reply to nevent1q…twfp
Author Public Key
npub1gkgyk28lurjuhyfjlxsga9mw6lc0c47c8pmcr65usre9d3qjcx6q9cyk5mPublished at
2025-02-12 19:33:11Event JSON
{
"id": "b593afd9fdddd9fe4bc6e894435703b9f01e7e547b3fa04a973b49ccb8efbdc5",
"pubkey": "45904b28ffe0e5cb9132f9a08e976ed7f0fc57d8387781ea9c80f256c412c1b4",
"created_at": 1739388791,
"kind": 1,
"tags": [
[
"e",
"f270d83d1f00199afa279d2085f98e1ca91bd214b47d94247b0d29c8d1008fbd",
"wss://pyramid.fiatjaf.com/",
"root"
],
[
"e",
"2105efda09bd97951af18e16e4cc8182d8eae90bc9ba9c36b3d47192bd1e2785",
"wss://pyramid.fiatjaf.com/",
"reply"
],
[
"p",
"f8e6c64342f1e052480630e27e1016dce35fc3a614e60434fef4aa2503328ca9"
]
],
"content": "That’s on the clients. They’re currently just migrating successful app structures; Twitter, insta, etc. Imagine when they truly embrace the capabilities of having a protocol that can access all content types and deliver convenient and diverse UX and use cases for users based on how the user sets that they want to engage with the content of each type. \n\nFor example. Maybe I have primal as it is, but with Olas image content added, I configure settings to just throw a 9-up tile of the 9 most recent Olas images of each user I follow into my main feed each day. If I engage with it, it’ll either take me to my Olas image content type feed in Primal or in Olas or to that user’s image feed specifically. \n\nOr maybe Olas images that correlate with an event content type that is happening within 10 miles of me (see my NIP-G0 draft in github) gets an in-app notification for me because I hate blanking on cool stuff going on in town that I would have gone out to enjoy. \n\nThere’s so much more potential than cloning existing centralized app functionality. We don’t have a grid of walled gardens any longer. It’ll take devs time and experiments to expand the clients to capitalize on the capabilities.",
"sig": "ed4bb762d940be47319adff73e6a7093056046828c8ce3b24c7a81f698321f991254bfa5eb235770cee6bb1032e254567af778bb8285b6d1a405069b69e990a3"
}