@sir "This information is used to hack your brain" - I liked that one!
@sir You are doing good work.
@sir You forgot the best upside of plaintext email...
Never receive e-mails written in comic sans again.
They stopped it eventually, but 10 years ago Microsoft sent minified html and I could tell by the way lines ran together that they generated the plain text version by using a tag stripper on *that* 💩
I never recovered the courage to trust email providers to generate a clean text/plain message in multipart 😂😂😂
> A: Because it reverses the logical flow of conversation.
> Q: Why is top posting frowned upon?
On the other hand, one advantage I can think of for top posting is that it puts the new and therefore salient information first.
@Hyolobrika this implies all information should be present, and it should not be. Old information is available for reference in your archives. Only quote the important parts of the previous message.
What do you mean?
One can still snip out irrelevant text either way.
@sir I support plaintext email, but I don't get the hard wrapping at 72 chars. Surely you want to soft wrap at a comfortable width, rather than forcing users on thin screens to scroll or read a mess of combined hard-wrapping and soft-wrapping?
The LKML is unreadable on mobile due to the 72-char hard wrap.
I find it extra weird from programmers, because unconditionally wrapping at 72 chars breaks code.
@sir Nice work, but let me ask one question:
Who is this page targeted to? People who use plaintext email or those who don't?
Because just by the way it's written I guess it's a lot more appealing to people who use plaintext emails anyway.
@sheogorath the former, as an instructional guide to fixing their client and a list of reasons to do so.
@sheogorath also to the authors of email-writing software, addressed near the bottom
»The few advantages they offer for end-users, such as links, inline images, and bold or italic text, aren't worth the trade-off.«
Sorry, but: not true.
@sr_rolando begone demonic spectre
@sir I had to google* that one. 😳
(*using ecosia, but still)
@sir the section here for roundcube here is incomplete and incorrect
on a provider i use that uses roundcube for webmail, bottomposting is default
top or bottom posting can be configured by setting [ Preferences -> Composing Messages -> When Replying ] to "start new message below the quote"
there is also an option to avoid quoting entirely
it also uses format=flowed by default (i see no way for it to be disabled)
@ky0ko ack, thanks
@ky0ko can you send me an email so I can verify format=flowed is working correctly? It's often implemented wrong
@sir sent a few emails
@ky0ko ah, please send test emails with lines longer than 80 characters, otherwise format=flowed doesn't kick in. I should have mentioned that
@sir it appears roundcube truncates everything to fit in 72 characters, is that expected behavior
@ky0ko yep! thanks very much
@ky0ko hm, it only appears to do that for quotes. The email you wrote to me initially is not truncated correctly nor marked as format=flowed
@ky0ko so I think I can give it marks for bottom posting but not for format=flowed
@sir that's weird, because if i view the source it shows as format=flowed on my end
@sir unless you're talking about one from disroot.org - those are from rainloop
the only ones sent by roundcube are from the address with my name in it
@ky0ko ah. I never saw an email from you from ingalls.rocks which had long enough lines to test if they were being flowed.
@sir it automatically truncates quotes in replies to 72 and makes the text fit. is there something specific you'd like me to send to test this?
@sir i could manually craft "quoted" text that is longer than 80 lines if that is what you want
@ky0ko just some lipsum would do fine. Quotes aren't the problem here
@ky0ko got the email - it's perfect. Thank you!
@sir imagine if plaintext didn't have two confusing meanings though
- plaintext email: non-rich-text email
- plaintext email: unencrypted email
cmpwn.com is a private Mastodon instance for friends of SirCmpwn.