MSGID: 2:221/1.0 6624f214
REPLY: 2:221/1.0 66249cba
PID: SmapiNNTPd/Linux/IPv6 mxo 20240419
NOTE: HotdogEd/2.13.5 (Android; Google Android; rv:1) Hotdoged/1712127426000
HotdogEd/2.13.5
RFC-Content-Type: text/plain; charset=UTF-8; format=flowed
RFC-Content-Transfer-Encoding: 8bit
BBSID: MXO
CHRS: UTF-8 4
TZUTC: 0300
TID: hpt/lnx 1.9 2024-03-02
Hello, Tommi Koivula.
On 21/04/2024 4.57 you wrote:

 TK> On 20.04.2024 16:52, Nicholas Boel wrote:
 NB>> So, if HotdogEd doesn't support format=flowed, wouldn't it be better to
 NB>> use 'flowed=off'?
 NB>> Or while using HotdogEd with flowed=off, it still wraps at the 72/79
 NB>> columns set by jam/smapinntpd, which then HotdogEd would still wrap the
 NB>> text early because it doesn't have that many columns on the screen?
 TK> In my phone screen the width is about 58 characters. So it wraps first
 TK> at 58, then at 79. :(
 TK> The weird thing is that using a "real" nntp server this is not
happening...
 TK> 'Tommi
 TK> ---
 TK>   * Origin: smapinntpd/lnx (2:221/1.0)

Quote test hotdoged nntp.

--- 
 * Origin: smapinntpd/lnx (2:221/1.0)
SEEN-BY: 15/0 90/1 103/705 105/81 106/201 124/5016 128/260 135/220
SEEN-BY: 135/225 153/757 7715 154/10 30 203/0 218/700 221/1 6 242
SEEN-BY: 221/360 226/30 227/114 229/110 112 113 206 307 317 426 428
SEEN-BY: 229/470 664 700 240/1120 5832 266/512 280/464 5003 5555 282/1038
SEEN-BY: 291/111 292/8125 301/1 310/31 320/219 322/757 341/66 234
SEEN-BY: 342/200 396/45 423/81 120 460/58 256 1124 467/888 633/280
SEEN-BY: 712/848 770/1 5020/400 5054/30
PATH: 221/1 280/464 460/58 229/426