Here's an interesting idea: When writing a headline, add substantial context so we know what the article is about.
this post was submitted on 03 Mar 2024
45 points (97.9% liked)
Technology
37727 readers
609 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
Wow try being nicer I assure you it doesn’t hurt :)
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?
I second the question but from the looks of a web UI maybe the subtitle is what appears under the link?
That bottom text, yeah, and a lot of posts will have the entire content or a thorough summary embedded there, or archive.org/12ft.io versions of the link. On my instance, its collapsed behind a plus sign right after the title, like a comment, but above all the stats and action buttons.
Gotta tap on the plus sign 
next to their exclamation point ...
If your client doesn't show that, then yes: absolutely, 
You're missing out on the full Lemmy experience. Killer feature IMHO.
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.
Such a weird thing for a Lemmy client(or instance?) to neglect to impliment:
Killer feature, IMHO. You're missing out on the full Lemmy experience.
Thanks for pointing that out -- I didn't notice that [+] before (I use the web interface, btw). My original point remains though -- I still have to click something to know what we're talking about.
You don't even have to leave the feed view or wait for anything to load though. The fact there isn't an option to auto-expand such text(or is there? idk) is not OP's problem. They used the functions available to them as intended.
All except "effective communication skills", and I still had to take some action besides scrolling.
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.
I'm not even sure I understand it if it's not a joke, and I read the entire thing 😳
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.
The idea is to keep significant bits of thought under 80 characters.
That should be out of scope for a spec which "MUST NOT alter the final rendered output of the document."
It's not the place of a markup language/spec to influence writing style.