Huge shout out to nostr devs!
I posted an article and there was a problem with it not showing on some clients. They’ve spent a ton of time trying to figure out how to fix the problem. I appreciate it.
I think 2 parts are crucial actually 2.5:
- the `root issue that i mentioned earlier, when the content is not short notes.
- Damus (maybe others not sure) assume the mentionned content is a shot note thats why we can see the note1, however due it is clearly not kind-1, so wrong encoding in here, perhaps the quoting triggered it.
- the .5 part is that: some clients handle the mentions while others handle quotes exclusively and not both.
Thats why I suggested nostr:npub1yye4qu6qrgcsejghnl36wl5kvecsel0kxr0ass8ewtqc8gjykxkssdhmd0 to minimize the actions to one client, and we see how we notify others to fix such things.
Discussion
Thank you for your patience! It is extremely valuable for devs to get this kind of feedback and detailed information about an issue. This way everyone can help to make nostr better!
No problem. I’m grateful that hopefully it won’t happen in the future too much.
Is there already a result on how we should publish long-form content if we want it to appear everywhere without issues?
I’d give it a minute.
Nostr is everything in space of communication
Many of them simply wouldn't respond to me about it when for like half a year my articles wouldn't show up in some clients like Highlighter. They didn't respect me for continuing to post here and having faith it would get better instead of going somewhere else.
Beware trusting some of them. This is fundamentally a reflection of how important you are to nostr, not how trustworthy these devs are.
This experience by elizableu posting an artical on nostr is unfortunate. This will drive the best content away.
Here is a first draft of what I think is needed by publishers if a client is to support long form articles. Publishers: please add your must have's to this list. Developers: please indicate what your client supports in this list.
Clients should indicate if they support these features for long form content:
1. Markdown Rendering
2. Comment Rendering
3. Find Article by paste event hash in url or search field
4. Light or Dark Mode Option
5. Read without Login
6. User can select relays
7. Complete client key management onboarding |or| nsec login
I'm working on a client matrix specific to long form content... please reply for the purpose of publishing a complete list of client compatibility. This will help writers decide how to publish their content in a way that is encouraging.
These clients indicate they support Long Form Content (what clients are missing from this list?)
Amethyst
Coracle
Damus
Flycat
Gossip
Habla
Nos
nostr.band
noStrudel
Nostur
YakiHonne
Consider submitting your findings to https://github.com/nostrability/nostrability
I use Yakihonne, you can post on habla, Yakihonne and Highlighter, there is also freerse
Flycat is not updated for over a year, so can be sluggy...
the other are read clients so not important
Forgot about highlighter...
1. Markdown Rendering - yes
2. Comment Rendering - yes
3. Find Article by paste event hash in url or search field - yes: highlighter.com/a/ + nevent1...
4. Light or Dark Mode Option - yes
5. Read without Login - yes
6. User can select relays - no? I am not seeing ability to change it, or even discosing what relays it uses
7. Complete client key management onboarding |or| nsec login - yes
looks like Freerse is mobile: android/ios. does Freerse render comments on Articles?
I tried the app in October 2023, I don't think that will be updated either, opensats denied the contribution and the developer lost a bit of hope.
You can write long form on Nostrmo https://github.com/haorendashu/nostrmo, but no draft