#asknostr

Hey, Writers,

***HELP!***

I wrote a new Long Form article today using the YakiHone client. I put a lot of work into it. The article appears beautifully formatted on YakiHone, but looks AWFUL on Amethyst...😜😢

Is there any hope of widespread standard adoption for how clients parse and display basic markup languages like Markdown and HTML?🤔

Is there a subset of either or both of these languages (or any OTHER language) that will display reliably across the vast majority of clients?

Can you recommend a particular client editor for long form articles that you are pleased with? That works well for you?🤔

Thanks in advance for any help you can offer. 🙏🥰👍

Reply to this note

Please Login to reply.

Discussion

needs to be markdown uniformity. 👍

Plain flavor Markdown is the standard

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

But the short answer is no. Kind 1 focused clients could probably easily support markdown but how they do that matters and IF they want to do that matters.

Maybe it's time to use Obsidian with Nostr Writer plugin. I did that for a few reads, and they look really good on Primal.

Uugh. Have you ever formatted an ebook? Each reader displays it differently. If you do anything more than changing fonts for titles, it will only look good on a single app.

That's a bummer...😢

Epub readers are a mess...