Anything new on the development front?
The part sending messages from Fido has been completely rewritten.
Now I am watching and testing. In the meantime, I am radically
rewriting a part from Telegram to Fido. There, unfortunately, not everything is so simple. There will be new opportunities in this
part.
PS: After small rasp processing, the gate can be used instead of
the tosser. ;) Have nice nights.
Stas Mishchenkov.
--- Мудрость - это когда ты всё понимаешь, но уже не огорчаешься.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
I have noticed something different with your reply here.
I posted my message in Telegram.
Ordinarily, my NNTP feed would flag your reply as to me, but my
Points wouldn't. However, all 3 currently do. I have a new Webpoint address I haven't entirely set up yet, but I suspect it would as well.
Anything new on the development front?
Slightly changed the appearance of messages from Fido to Telegram.
;)
Slightly changed the appearance of messages from Fido to Telegram.
;)
August has been bothering you about that? ;P
Hi, Charles!
28 сен 20 17:54, Charles Pierson -> Stas Mishchenkov:
Anything new on the development front?
Slightly changed the appearance of messages from Fido to Telegram. ;)
Have nice nights.
Stas Mishchenkov.
Looks good! A suggestion for future consideration: With smartphone texting in mind, how about allowing for a shorter two-char version
for --Subj: when composing a message ?
--Subj: or --Sb: or --sb:
And then as you may come up with other --Header: tags, provide a
two-char version that would work too.
two-charAnything new on the development front?
Slightly changed the appearance of messages from Fido to Telegram. ;)
Looks good!
A suggestion for future consideration:
With smartphone texting in mind, how about allowing for a shorter
version for --Subj: when composing a message ?
--Subj: or --Sb: or --sb:
And then as you may come up with other --Header: tags, provide a
two-char version that would work too.
Looks good! A suggestion for future consideration: With smartphone
texting in mind, how about allowing for a shorter two-char version
for --Subj: when composing a message ?
--Subj: or --Sb: or --sb:
Honstly, I never even remember that. And Subj: is more familiar
A suggestion for future consideration:
With smartphone texting in mind, how about allowing for a
shorter two-char version for -- Subj: when composing a
message?
--Subj: or --Sb: or --sb:
I will consider this proposal. It was originally designed
as a purely technical label. It seems to me that such a
simplification can lead to false positives of recognition.
A suggestion for future consideration:
With smartphone texting in mind, how about allowing for a
shorter two-char version for -- Subj: when composing a
message?
--Subj: or --Sb: or --sb:
I failed to include the lowercase --subj: version of the tag to the
above list, for completeness.
I will consider this proposal. It was originally designed
as a purely technical label. It seems to me that such a
simplification can lead to false positives of recognition.
Just to clarify, I was only suggesting the use of the 2-char
versions when *creating* or *writing* a message on the Telegram side.
The full version of --Subj: on incoming messages is fine, and should probably remain unchained.
WRT false positives, I can appreciate the problem you foresee. If
there are alternatives to a header then it could be just as easy to mistype --Sb: as --sj: or --su: or something like that.
Therefore, maybe consider a rule for the shorter form to be just the
first 2 letters (since --To: and --to: are like that). That would be consistent and easier to remember.
.: --Subj: or --subj: or --Su: or --su: ..might be better?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 410 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 97:53:30 |
| Calls: | 8,588 |
| Calls today: | 1 |
| Files: | 13,228 |
| Messages: | 5,934,264 |