Genuine question: If every nostr app adds support for “Olas” images, then what’s the point of having a separate event kind for images at all?
Discussion
Kind 20 images are like "high quality" (if you wish) images. Stuff you want to share and keep in a gallery. Screenshots are not something I want to keep and share in my gallery.
Yes... this makes much sense for business that relay on visual. I can't imagine having my woodworking photos in the Twitter like clients...but a gallery like Olas, that's great. The beauty of nostr for sure.
Perhaps clients like Amethyst, Nostur, Coracle, etc need to give users a way to filter their galleries (do they have galleries? I know Nostur does). It would be good to have an option to “view all” or “view high quality only” for instance.
I added it personally to ametyhst. It automatically adds Olas images, but you can also manually add regular images.
Makes it easier to have better image/feed rendering UX
If you want to have an image only feed you don't have to check every single note for it when assembling the feed
Client segregation of network content to accommodate user intent? Instagram was awesome before Facebook bought it and added an algorithm for moms and zombies. It used to be a place where you posted photos of what you were up to, and active people could find similar active people and get a lens into their world in what felt like real time. That’s a different feel than Twitter for me. Primal is a Twitter clone/improvement. I’d love to have an Instagram back. And having a content-segregated feed like Reddit would be nice too.
I don’t like how I have to post all of my interests to all of my followers. I don’t think they’re interested in me as a person with diverse interests and views on life. I think they’re interested in seeing the areas of my interests that overlap with theirs.
For example, I like European travel, and I like building and using guns. I’m guessing that’s two different audiences, and my feed may feel messed up to them—so they’re likely to unfollow. I want segregation of content posted to different audiences and interests. Even privatized categories or groups would be nice.
I know it’s early for nostr. Not griping. I’m just clarifying saying that the more levers we give clients with content types, category designations, geo-tagging of event locations and relevance locations, the more use cases the protocol can elegantly accommodate.
Sure, but you don’t have client segregation because the twitter clients are adding support. At least 3 already have.
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.
It might end up a great thing. Right now it’s a disjointed and confusing mess for users 😂
Compatability of kinds in many clients doesn't make the specificity of a kind without purpose. Think of the wider adoption of Nostr and how congested it would be with different media types shoved into a kind later utilized for a specific use.