Hi Tommi,sequence number. Because if you re-install the application (within 3 years), it will probably restart at 0 again, and you have created duplicate MSGID's...
On 2020-10-12 16:02:08, you wrote to me:
@MSGID: 2:460/58 00000354
MSGID looks fine now.
Well, normally you want to base your MSGID on the time, and not use a
Bye, Wilfred.Not only that, but if/when this gate software is used on other systems, it could be a problem when the msgids all resume from 00000001. A better formula might be a combination random hex number+serial hex.
Well, normally you want to base your MSGID on the time, and not use
a sequence number. Because if you re-install the application (within
3 years), it will probably restart at 0 again, and you have created
duplicate MSGID's...
Not only that, but if/when this gate software is used on other
systems, it could be a problem when the msgids all resume from
00000001.
A better formula might be a combination random hex number+serial hex.
Not only that, but if/when this gate software is used on other
systems, it could be a problem when the msgids all resume from
00000001. A better formula might be a combination random hex number+serial hex.
Not only that, but if/when this gate software is used on other
systems, it could be a problem when the msgids all resume from
00000001.
No, because the combination of node number and ID should be unique,
not just the ID.
A better formula might be a combination random hex number+serial
hex.
No, you can't use a random number, because of the small size of the
ID, there is a too high chance you generate an identical ID.
it could be a problemWell, normally you want to base your MSGID on the time, and not use a sequence number.
Because if you re-install the application (within 3 years), it will probably restart at 0
again, and you have created duplicate MSGID's...
Bye, Wilfred.
Not only that, but if/when this gate software is used on other systems,
when the msgids all resume from 00000001. A better formula might be acombination random hex
number+serial hex.
Well, normally you want to base your MSGID on the time, and not use
a
sequence number. Because if you re-install the application (within 3
years), it will probably restart at 0 again, and you have created
duplicate MSGID's...
Hi August.a sequence number.
12 Oct 20 17:27:10, you wrote to Wilfred van Velzen:
Well, normally you want to base your MSGID on the time, and not use
probably restart at 0Because if you re-install the application (within 3 years), it will
systems, it could be a problemagain, and you have created duplicate MSGID's...
Bye, Wilfred.
Not only that, but if/when this gate software is used on other
a combination random hexwhen the msgids all resume from 00000001. A better formula might be
combination of fido address and 8 char hex string. :)number+serial hex.
The other system is not using the fido address 2:460/58. MSGID is a
'TommiI hear ya. MSGID is defined as node # and 8-char hex. There is plenty of uniqueness right there. But in the case of a reinstall within 3 years, unless the gate software knows where it left off the last time, the new messages after the reinstall may end up being treated as dupes by other systems?
---
Not only that, but if/when this gate software is used on otherThe other system is not using the fido address 2:460/58. MSGID is
systems, it could be a problem when the msgids all resume from
00000001. A better formula might be a combination random hex
number+serial hex.
a combination of fido address and 8 char hex string. :)
From what I understand, each gate would be a unique "user" not sharing Telegram Groups, and having different Fido addresses. By this I am referring to the idea of multiple gates for the same echo. Nor do I necessarily see very much overlap in gate/echo combinations.
As I said in another reply, I don't understand all of the technical aspects, but in this case, I don't really see an issue.
Hi, Charles!sharing
12 окт 20 09:53, Charles Pierson -> August Abolins:
From what I understand, each gate would be a unique "user" not
like BBS.Telegram Groups, and having different Fido addresses. By this I am referring to the idea of multiple gates for the same echo. Nor do I necessarily see very much overlap in gate/echo combinations.
As I said in another reply, I don't understand all of the technical aspects, but in this case, I don't really see an issue.
Strictly speaking, this is not exactly a gate in Telegram. It looks more
Have nice nights.In that, you are right. As long as the matching group is Private on the TgM side, the messages are not really gated anywhere and just remain on your BBS. So the bot is not really gate in the traditional sense. It's just a facilitator to use Telegram as a reader not unlike someone would prefer to use QWK or a newsreader from an nntp feed.
Stas Mishchenkov.
Strictly speaking, this is not exactly a gate in Telegram. It
looks more like BBS.
Have nice nights.
Stas Mishchenkov.
--- Каждый раз бухай как последний. Потому что однажды так и
будет. * Origin: Lame Users Breeding. Simferopol, Crimea.
(2:460/5858)
I hear ya. MSGID is defined as node # and 8-char hex. There is plenty ofuniqueness right there. But in the case of a reinstall within 3 years, unless the gate software knows where it left off the last time, the new messages after the reinstall may end up being treated as dupes by other systems?
A random number segment in the 8-char string (even if it was as short as3 hex chars) would significantly reduce that headache.
(BTW.. this message also serves as test to see if the Subj from your fidomessage is inherited in my Reply.)
--subj:CR required, or false positives--the attachment (the photo) tripped the parser somehow?
Hello Stas. I'm pretty sure I had added the CR after that post. Maybe
I see. So it acts more as a node or point system off of yours. Not
quite as complicated as I thought, but still complicated enough.
I'm surprised you've done as much as you have in about a year or so?
Hi, Charles!that August pushed me to convert the gate into a tosser when he noticed that in some letters the text after some characters is lost. Since then, no more than two or three weeks have passed.
12 окт 20 17:06, Charles Pierson -> Stas Mishchenkov:
I see. So it acts more as a node or point system off of yours. Not quite as complicated as I thought, but still complicated enough.
I'm surprised you've done as much as you have in about a year or so?
In fact, quite recently, everything worked very differently. I can say
Have nice nights.Indeed. That is quite an achievement.
Stas Mishchenkov.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 409 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 52:23:16 |
| Calls: | 8,571 |
| Calls today: | 1 |
| Files: | 13,222 |
| Messages: | 5,929,366 |