^-^-^-@@-^-^-^
(..)-----;
||---||
^^ ^^
... A Møøse once bit my sister ...
So another version of your tagline generator?
Missing the TZUTC flag! ;-)
As I'm not sure any software actually uses the TZUTC flag it would be better, although it's not a fidonet standard afaik...
I was aware of people working on using TZUTC but have yet to see it in action.
Missing the TZUTC flag! ;-)
As I'm not sure any software actually uses the TZUTC flag it would be
better, although it's not a fidonet standard afaik...
The time of post is not necessarily critical. But it is cool to recognize that when a post is dated and uses tzutc, and processed with a capable reader, it reveals the time relative to one's own local time.
Anyhow it is doable but requires additional processing in order to
honour an obsolete datetime stamp (two digit year) and a corrupted utc offset which lacks the required '+' prefix for timezones east of prime meridian.
Again, that is not a requirement for the fidonet TZUTC flag.
Again, that is not a requirement for the fidonet TZUTC flag.
By default, it is for the RFC-3339 flag. Same with the full year.
It even has the proper C0 control codes in it as per specs.
But that's not the TZUTC flag. ;)
UTC is correct for this node.
Is that node located in the 0 meridian timezone?
I'm guessing it's not, so that wouldn't be correct...
they also know their location and offset to UTC, so they can
present the correct localtime.
FTS-4008 Is right by definition. It's the fidonet standard.
has it made any difference there in any meaningful way?
Only if it's not 'TZUTC: 0000'. ;)
they also know their location and offset to UTC, so they can
present the correct localtime.
When it presents the localtime exactly what information is it providing?
FTS-4008 Is right by definition. It's the fidonet standard.
My country right or wrong?
FTS-4008 is a seriously flawed document.
It takes a legitimate concept (utc offset) and bastardizes it for no apparent reason. It should get the heave-ho. Something like the
RFC-3339 flag would be a much better approach for compensating for the current flaws in fidonet standards.
has it made any difference there in any meaningful way?
Only if it's not 'TZUTC: 0000'. ;)
Within this msg is one that presents a legitimate utc offset (-0800) encased in a TZUTC flag. Does it make a difference?
Asking the question is answering it: localtime.
What does your country have to do with it?
It is how it is in fidonet. I would say almost impossible to
change. So you will just have to live with it.
I think that's usefull information.
Where the real magic resides, I find, is in a program that can utilize
the TZUTC info in such a way it organizes the message in true chronological order in a thread - and not based on arrival time. For instance, if don't read an echo for days, but different people write messages with true replies prior to that at different times, the
actual order of the messages in a thread are connected to a parent
message in the time order that people thus spoke.
It is how it is in fidonet. I would say almost impossible to
change. So you will just have to live with it.
Or ignore it which is probably what I will end up doing soon. However I do
not cede my right to bitch about it again in the future if it strikes my fancy.
I think that's usefull information.
If that is all you require then I'd suggest the RFC-3339, or something like
it, is the way to go. No harm, no foul.
I know it isn't perfect, but most of the time it works...
Does it actually matter whether I wrote this at 11:45 am (actual time for me) or 11:45pm?
I know golded can when properly configured.
If so then please explain "CHRS: UTF-8 2" with respect to FTS-5003. Also golded corrupts utf-8 characters (same with msged) when it tries to actually use them, with or without a CHRS flag. I haven't noticed if it makes adjustments when it encounters a TZUTC flag. Does it?
If you don't like what they do, you should join them, so you can
change that! ;)
I'll get right on that.
I can also ask my RC to nominate him, if he wants to be
nominated...
Nominated for what?
Close. It's called the 'Richard Principle': promote them on to
another suck^h^h^h^hluckless supervisor.
Hey Carol!
Well, from what I see it's the normal resistance
Which is much less than I usually got there when bringing up such topics in past. Mind you most (all?) of that came from the previous moderator/chairperson.
Most interesting was all the real feedback posting the major alteration to fts-0001.016 generated within FTSC_PUBLIC. I haven't see that happen since forever?
Life is good,
Maurice
... Mon sceal... gebidan þæs he gebædan ne mæg.
One must wait for what cannot be hastened.
I'm a little behind there but I'll catch up.
I'm a little behind there but I'll catch up.
Hey Carol!
I'm a little behind there but I'll catch up.
I replied to this on the node but am having some connection issues so I'm go to see what happens when I use this link. Please feel free to ignore this reply.
Life is good,
Maurice
... Ne wurðe þe næfre to þys wa, þæt ðu þe ne wene betran.
Never become so sorrowful that you do not hope for better things.
It's ok! I just spent a 3 week very heavy work schedule with 3
RADM briefs all within the same week. Lots of work! BBS sat to
the side.
-={ 2021-01-30 18:24:24.737908806+00:00 }=-
Hey Carol!
It's ok! I just spent a 3 week very heavy work schedule with 3
RADM briefs all within the same week. Lots of work! BBS sat to
the side.
Sounds to me like standard operating procedures. From this angle it appears you didn't miss anything so I agree that 'it's ok!'
Life is good,
Maurice
... Soþ hit sylf acyþeð.
Truth will make itself known.
| Sysop: | Coz |
|---|---|
| Location: | Anoka, MN |
| Users: | 2 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 157:51:30 |
| Calls: | 162 |
| Files: | 5,334 |
| Messages: | 221,585 |