Subj : Re: Join Networks To : Ogg From : Gamgee Date : Thu Sep 08 2022 19:39:00 -=> Ogg wrote to acn <=- a> If I see the thread view correctly, it really shows one a> problem: the subject of the thread changes with (almost) a> every message. Why is that happening? Og> First, anyone in Fidonet can change a subject, or have none all Og> too for that matter. ;) True, but irrelevant. It only happens with Telegram users. Og> But from the Tg side, the challenge is to provide a reasonable Og> Subject to fit the Fidonet expectation of having one (or not), Og> when the Tg environment operates without needing a Subject. So..... Telegram is admittedly broken. Og> But Stas made a very clever innovation and simply uses the Og> first 40 chars of the body of the message as the Subject. That's not an "innovation", it's a KLUDGE. A very poor one. Og> Looking at it from the Fidoside, it serves to be a kind of Og> message preview. I think it's good and better than absolutely Og> nothing, or just three dots which was the result of earlier Og> implementations. No, it just further contributes to the dumpster fire that any echo with Telegram users turns into. Og> Further along into development the feature to actually include Og> a Subject was added. Oh! But apparently it doesn't work? Very confusing, you've claimed two different things on this, right in this very message. Og> Now, IF a TgBBS user fails to enter a Subject, the system will Og> take the 1st 40 chars of the message. Which turns the threading functions into garbage. Og> What particularly one (and only one) user is doing in the Og> LITRPG echo is failing to enter a Subject *and* not using the Og> typical R)eply feature to some messages. :( That person should be prevented from posting. Og> However it's fairly straight forward to follow the thread since Og> most messages are FEW, and chronological and in sequence, and Og> MSGID and REPLYIDs are utilized. But, the thread CAN'T be followed, because there is NO QUOTING or CONTEXT visible. Just random one-line "messages" that have ZERO relation to anything. Og> Further discussion about all this is best in the dedicated Fido Og> FIDONET.TELEGRAM echo. Yes, that way it won't get wide coverage/discussion, and the "masses" will continue to not know what a mess it is. .... All the easy problems have been solved. === MultiMail/Linux v0.52 --- SBBSecho 3.15-Linux * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138) .