Here’s an interesting idea: When writing a headline, add substantial context so we know what the article is about.
I think your mistake was assuming users woudd read the subtitle you had put in a space Lemmy users are used to seeing dedicated to much more detailed summaries of, or even the entire, content. Even if subtitles are closer to the intended use of that space and you did provide plenty of context with the subtitle.
Try expecting less of people. I assure you it will save you a world of pain and a lot of yelling at clouds.
what subtitle? all i see is the title “Such an interesting idea!” and a link with a thumbnail. is there more information that my client isn’t displaying?
At the top level, I can’t even see the subtitle – just the headline, a cropped and highly pixelated thumbnail, and the domain of the linked article. I had to click to get the subtitle, and I wouldn’t have done even that if the headline were more explicit.
from the thumbnail, i really thought this was gonna be a joke about reinventing paragraphs
Not being intended as a joke makes it even funnier. I mean, the lack of awareness is amazing.
A maximum line length of 80 characters is RECOMMENDED.
This is a terrible recommendation. It defeats the purpose of semantic line breaks if you insert them for non-semantic reasons as well. It also makes editing much more difficult. Let client software handle soft line wrapping, so the user can customize it as it makes sense for them. If your client software doesn’t handle soft line wrapping in a sensible way, find better software.
Reminds me of this blog post I read a while back: https://sive.rs/1s
