Can you share a 1-2 examples of app implementing this in practice?

Reply to this note

Please Login to reply.

Discussion

No, that is the problem, because it should be implemented everywhere by everyone in all cases

I don’t see a shopstr link anywhere in the linked article when I open with havla

The alttag is here:

"Product listing: Sunflower - Testing"

This should be enough and is fine. Eventhough the client you are using does not render kind30402 events, it can display that string making it clear what it is, i.e. a product listing, of a sunflower.

Nip 89 integration should subsequently give you the hints as to what clients you could use to render the event, if you are interested.

Is this not in the user facing UI?

Is it solely in JSON blob, and not surfaced to the user?

I dont understand, can you clarify?

Where are you seeing “Product listing: Sunflower - Testing"

In the example long form article as seen by habla?

I see that in the JSON of the second example he mentioned, under the tag 'Alt'. The JSON can be inspected on njump at the bottom by clicking 'Show more details'.

In the first example, the alt tag is:

"This is a long form article, you can read it in https://habla.news/a/naddr1qvzqqqr4gupzpwa4mkswz4t8j70s2s6q00wzqv7k7zamxrmj2y4fs88aktcfuf68qqjk67fdwajk26mn955rzwptxyujjttfdckhyetkd9jhwtfjxqhnqdf0xgcrydg2sg8h5"

The idea behind the alt tag is that any client that supports it, but does not support the kind in question, will render what is in the alt-tag, instead of breaking (showing some error like "cant load event" or whatever)

Excellent. Note that although i might have preferences on what is out in the alt-tag, it does not really matter all that much, anything is better than it not being there.

Combine it with nip89 and Nostr as a whole functions so much better.

This way you can always just reference whatever event in a kind1 note, and be rest assured nothing breaks and is at worst, suboptimal. Also takes away pressure from kind1 clients to keep up with stuff if they dont want to.

yes but you have to paste nostr:event (preview) if you paste nostr:naddr assume that the reader is in a client that shows that kind