2 ms·

> Which component is that? The SMTP protocol? According to [1], the maximum line length allowed by SMTP is 1000 octets, which is well over any maximum hard-wrap

> Which component is that? The SMTP protocol? According to [1], the maximum line length allowed by SMTP is 1000 octets, which is well over any maximum hard-wrapped line length for typical source code lines. The wetware component enforcing some line length - some old maintainer stuck in his ways. I don't see what you're trying to achieve ignoring that? > Hardwrapped text is only a problem for displays that cannot display lines as long as the hardwrapped line length You're incorrect, it's a problem on wider screens as well. > Mobile email clients are not suited for reviewing patches due to the fact that they typically use variable width fonts and do not provide a way to post replies inline with quoted text. Again, that's an issue caused by non-HTML e-mail that's currently enforced in way too many places. It's not a problem with any e-mail system that is even somewhat modern. > Why can't those tools work when I'm getting 5 to 10 kB per second downstream? That's not the issue, your network's QoS is bad. > Exactly how much experience do you have on the internet at dial-up speeds? Years, more than enough to know it was absolute shit. >> Nah, this reply is given to even insiders that don't want to deal with that obsolete shit. > Citation please. https://lkml.org/lkml/2020/5/28/1457 https://lkml.org/lkml/2020/5/28/1457 Here. Linus shut him down nicely though. :)

u801e 6y ago
> The wetware component enforcing some line length - some old maintainer stuck in his ways You need to be more specific about what you're referring to when you bring something up. I already stated that email clients can be set to use longer line lengths. Are you aware that the default line length for hard-wrapped emails is 72 characters, not 80? It shouldn't take 4 posts for you to be specific enough for one to get what you're referring to and then basically ignoring the point I already brought up pertaining to that issue. > You're incorrect, it's a problem on wider screens as well Given the level of nesting in this sub-thread, the large amount of blank screen space to the left of the post is not posing any issues in terms of readability. I'd rather avoid "embarrasing line wrap" due to hard wrapped lines that are too long for the display. Also, the format=flowed option has solved this issue. > Again, that's an issue caused by non-HTML e-mail I assume you're aware of the problems caused by HTML email where people end up getting phished because of the anchor element with the hfref property set to make the link look like a legitimate website like their bank? Email should be plain text only. Leave the HTML to the web browsers. > That's not the issue, your network's QoS is bad. If the QOS was bad, then email and IRC would not work. They still do on the slow downstream and upsstream connection. And even if your claim of QoS was true, that doesn't explain why I experience the same issue on my mobile with a GPRS connection.

u801e 6y ago

> The wetware component enforcing some line length - some old maintainer stuck in his ways You need to be more specific about what you're referring to when you bring something up. I already stated that email clients can be set to use longer line lengths. Are you aware that the default line length for hard-wrapped emails is 72 characters, not 80? It shouldn't take 4 posts for you to be specific enough for one to get what you're referring to and then basically ignoring the point I already brought up pertaining to that issue. > You're incorrect, it's a problem on wider screens as well Given the level of nesting in this sub-thread, the large amount of blank screen space to the left of the post is not posing any issues in terms of readability. I'd rather avoid "embarrasing line wrap" due to hard wrapped lines that are too long for the display. Also, the format=flowed option has solved this issue. > Again, that's an issue caused by non-HTML e-mail I assume you're aware of the problems caused by HTML email where people end up getting phished because of the anchor element with the hfref property set to make the link look like a legitimate website like their bank? Email should be plain text only. Leave the HTML to the web browsers. > That's not the issue, your network's QoS is bad. If the QOS was bad, then email and IRC would not work. They still do on the slow downstream and upsstream connection. And even if your claim of QoS was true, that doesn't explain why I experience the same issue on my mobile with a GPRS connection.