nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q Another quality of life improvement would be publisher attribution on long form. I've only ever seen "N/A" in this field.

Reply to this note

Please Login to reply.

Discussion

nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 which app did you publish this article with?

Has bare hands, asking the squirrels to do the hashing and signature math for him.

It is known

An app called https://fiatjaf.com/.

if you post with yakihonne it gives you yakihonne

That would be obvious, yes.

others do not post the client tag, habla has an alt tag to say you can read it on habla with the link

Unfortunate, that should be done via nip-89. The alt-tag should describe what it is.

Not the end of the world, but still

Exactly yes

A kind 31990 event of any client that handles writing articles should be published, and reference it inside each article written in that client so it could be displayed like this. It’s N/A because no event of that kind of such client was found.

My point is that you could check for that condition and either not display the field or display something for useful than “N/A”.

Ah okay i understand, what do you suggest as an alternative?

I’m no designer, but logically, if the field has no/null value, hide the field.

Makes sense yeah, we will look into that.