Writing an article about how you're frustrated with Nostr apps and having various formatting in the article being broken on various Nostr apps is peak Nostr.
Discussion
Sounds like something Semi would do.
This is not to knock him at all lol, heβs a great dev.
nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj is Batman.
Few know this.
I love it lol
π«
I'm still bullish as hell, but the frustration is building.
And that's why the fire burns fren β€οΈβπ₯
#thefrustrationisreal
Yeah. Long-form needs some collective love. I've run into a bunch of unexpected things since trying to write more frequently. I've found my comfortable workarounds for most client deficiencies for now, but that doesn't change the formatting or the string-too-short event errors. It'll get there, though. π«
if you want quote the npub is nostr:npub1...
someone should write a NIP markdown-nostr for user
ok for titles I use
# headings
what about underlined?
and
# == february 07 2025
test to hide
We only cover
# headings
and
headings
=======
No underline. That would be confusing UX because hyperlinks are underlined.
underline was picked for this purpose because it's formal use in writing stuff is by proofreaders, it doesn't belong in a finished text
Yakihonne has ~~h5eh5~~ strikethrough
You didn't read what I wrote, did you?
Did you click the link and read the GitHub comment?
I read it yesterday but forgot about it this morning, the double thing confuses me a bit
I have single and double doing the same thing, for bold, italic, and strikethrough.
No underlines, since they're reserved for hyperlinks.
ok!
Habla has underline ++test++
so you will have to support this?
πͺπΌ