If I want to store a web resource (basically an RSS item) what is the best NIP to use? I think 51 and kind 30003 or 30004 but I'd like to use the metadata from 30023
Discussion
I don't know about nip, but 30003 can be found on nostree me and 30004 long form curations on yakihonne and highlighter
I'd say 30003 if it's a url, but what do you mean about using the metadata from 30023?
I screwed up that reply, see above comment. Basically I have a news digest that is email based (newstr.social) but I want the data to be Nostr native. I could just make a long form content post but I think it would be better in a list or atomically put together in a list
From Nip 23:
"title", for the article title"image", for a URL pointing to an image to be shown along with the title"summary", for the article summary"published_at", for the timestamp in unix seconds (stringified) of the first time the article was published
But was just thinking of https://ogp.me/ and Twitter metadata in web pages. I guess it's just tags and they can be up to my app?
I see, if you're shooting for interoperability I wouldn't add that stuff to lists, although if you look at NIP 51 kind 300xx can include title, image, and description. Are these lists DM'd to your users, or how are they used?
Currently I get them via an email or RSS, but like I said, the goal is to free them back into Nostr, so it isn't proprietary data. I doubt users would want a DM (I don't know) so in an ideal world they'd be displayed in clients , and in a less ideal world, my client at least. It's similar to link sharing in a Hacker News or Reddit style client, just curated ina different way, so I can't see making an HTTP round trip to display an associated image and summary is performant, so I want the metadata to travel with the event, if that makes sense
I see, I'm not sure there's anything that does exactly that. You could create a new kind, but keep interoperability in mind — that's much more important than performance. Sharing lists around is useful, if you can get over the fact that they'd be created by your pubkey only.
Yeah I've been thinking about the single pubkey dillema. I suppose in DVM scenario the deliverable could be JSON or Markup, which the user could perhaps then publish themselves. Not sure, but thanks for giving me some direction