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?
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?
Discussion
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