Good day, Sir!
Just a thought about messages and timezones...
Whenever I read through QWK and FTN-based messages, I see each message tagged with a timezone or offset.
This is great, yet I also feel it isn't
necessary. Instead, why can't we inquire with the user during sign-up and within the Default User Config.
Asking the user their timezone, utilizing a similar manner to that of RHEL and Debian-based /usr/share/zoneinfo/zone1970.tab could help populate the request from the user. Then, when displaying messages, all messages are displayed based upon the offset and not the original source message.
Just a thought...
I've considered it. Users do move around however, sometimes between time zones. The BBS usually stays in one time zone.
I kind of like seeing the originating timezone and the local time myself however. <shrug> --
Re: Message Timezones
By: Digital Man to Dream Master on Thu Mar 31 2022 12:48:52
I've considered it. Users do move around however, sometimes between time zones. The BBS usually stays in one time zone.
Just a thought...
What if the time zone was derived from the location of the user's IP address?
Re: Message Timezones
By: Digital Man to Dream Master on Thu Mar 31 2022 12:48:52
I've considered it. Users do move around however, sometimes
between time zones. The BBS usually stays in one time zone.
Just a thought...
What if the time zone was derived from the location of the user's IP
address?
Unreliable, especially if
the user is using the web based telnet
interface or using dialup via a modem.
Digital Man wrote to Dream Master <=-
Re: Message Timezones
By: Dream Master to Digital Man on Thu Mar 31 2022 10:47 am
Whenever I read through QWK and FTN-based messages, I see each message tagged with a timezone or offset.
Unfortunately, not all messages are.
This is great, yet I also feel it isn't
necessary. Instead, why can't we inquire with the user during sign-up and within the Default User Config.
I've considered it. Users do move around however, sometimes between
time zones. The BBS usually stays in one time zone.
If the standard was to timestamp messagse in UTC, then at least for message creation, it would be a moot point (what zone the BBS or the author was in), but unfortunately, that's not how existing BBS message networks work. The date/time stamps of messages are generally expected
to be in the local time of the BBS.
A message reader could already do that in theory: just display a
message's timestamp in UTC or convert to the user's preferred zone on
the fly.
I kind of like seeing the originating timezone and the local time
myself however. <shrug> --
On 03-31-22 12:48, Digital Man wrote to Dream Master <=-
I've considered it. Users do move around however, sometimes between
time zones. The BBS usually stays in one time zone.
If the standard was to timestamp messagse in UTC, then at least for message creation, it would be a moot point (what zone the BBS or the author was in), but unfortunately, that's not how existing BBS message networks work. The date/time stamps of messages are generally expected
to be in the local time of the BBS.
Asking the user their timezone, utilizing a similar manner to that of RHEL and Debian-based /usr/share/zoneinfo/zone1970.tab could help populate the request from the user. Then, when displaying messages, all messages are displayed based upon the offset and not the original source message.
Just a thought...
A message reader could already do that in theory: just display a
message's timestamp in UTC or convert to the user's preferred zone on
the fly.
I kind of like seeing the originating timezone and the local time
myself however. <shrug> --
digital man (rob)
On 03-31-22 15:53, Martin Rayburn wrote to Digital Man <=-
@VIA: VERT/ANSUN
Re: Message Timezones
By: Digital Man to Dream Master on Thu Mar 31 2022 12:48:52
I've considered it. Users do move around however, sometimes between time zones. The BBS usually stays in one time zone.
Just a thought...
What if the time zone was derived from the location of the user's IP address?
On 03-31-22 17:46, Nelgin wrote to All <=-
Unreliable, especially if the user is using the web based telnet
interface or using dialup via a modem.
I've considered it. Users do move around however, sometimes between
time zones. The BBS usually stays in one time zone.
Really? Why would users move around? If our users are connecting into our
What if the time zone was derived from the location of the user's IP address?
What time zone is 10.43.21.14 in? ;) For technical reasons, I access my BBS over a ZeroTier virtual LAN when I'm away from home. That is my actual IP that the BBS sees. ;) And I can be anywhere in the world with that IP. Currently 1300km away from home and an hour behind in Brisbane.
interface or using dialup via a modem.
hahah!
how about if monkeys flew out my ass.
think I'm trying to compare BBSes and our users to that of business
e-mail and messaging systems (Teams, Slack, Exchange, etc.) where each
is configured to the user's timezone and the BBS is configured to
whatever timezone it is sourced at. Even if we configure everything to UTC, user offsets could still be a "thing".
Really? Why would users move around? If our users are connecting
into our
People move for the usual reasons, like maybe they got a job somewhere else, or maybe they want to move somewhere with a lower cost of living, or to be closer to family, etc., etc...
interface or using dialup via a modem.
hahah!
how about if monkeys flew out my ass.
Using dialup is for those rare eccentric (re: crazy) people that are WAY TOO nostalgic. The days of dial-up sucked, but for a long time it was the only thing going.
Sometimes I move around just to prevent blood clots, bed sores, and muscle atrophy. None of this movement has brought me to a different time zone recently, but I did leave my neighbourhood for about an hour a few months ago.
MR> > interface or using dialup via a modem.
MR>
MR> hahah!
MR>
MR> how about if monkeys flew out my ass.
Using dialup is for those rare eccentric (re: crazy) people that are WAY TOO nostalgic. The days of dial-up sucked, but for a long time it was the only thing going.
Digital Man wrote to Dream Master <=-
Re: Message Timezones
By: Dream Master to Digital Man on Thu Mar 31 2022 10:47 am
Whenever I read through QWK and FTN-based messages, I see each message tagged with a timezone or offset.
Unfortunately, not all messages are.
Standards, it seems that we lack standards. :)
This is great, yet I also feel it isn't
necessary. Instead, why can't we inquire with the user during sign-up and within the Default User Config.
I've considered it. Users do move around however, sometimes between time zones. The BBS usually stays in one time zone.
Really? Why would users move around?
If our users are connecting into our
systems, they still have a "home" location, such as PST8PDT or MST7MDT (old school, but America/Los Angeles or America/Denver). I think I'm trying to compare BBSes and our users to that of business e-mail and messaging systems (Teams, Slack, Exchange, etc.) where each is configured to the user's timezone and the BBS is configured to whatever timezone it is sourced at. Even if we configure everything to UTC, user offsets could still be a "thing".
If the standard was to timestamp messagse in UTC, then at least for message creation, it would be a moot point (what zone the BBS or the author was in), but unfortunately, that's not how existing BBS message networks work. The date/time stamps of messages are generally expected to be in the local time of the BBS.
Very valid point. Just one of those "nice to have" things.
A message reader could already do that in theory: just display a message's timestamp in UTC or convert to the user's preferred zone on the fly.
I kind of like seeing the originating timezone and the local time myself however. <shrug> --
I'd love to see a message reader do that. Now, if I can only find the time in my overly hectic life to add something to our message readers. And your shrug, I support it. I do like seeing where people are at, generally speaking.
Using dialup is for those rare eccentric (re: crazy) people that are WAY TOO nostalgic. The days of dial-up sucked, but for a long time it was the only thing going.
dialup age was amazing...
dialup age was amazing...
At the time, it was amazing. In hindsight or comparison to today's broadband Internet? Yeah, not so much... :-)
dialup age was amazing...
At the time, it was amazing. In hindsight or comparison to today's broadband Internet? Yeah, not so much... :-)
Nightfox wrote to Dream Master <=-
Re: Re: Message Timezones
By: Dream Master to Digital Man on Thu Mar 31 2022 09:29 pm
I've considered it. Users do move around however, sometimes between
time zones. The BBS usually stays in one time zone.
Really? Why would users move around? If our users are connecting into our
People move for the usual reasons, like maybe they got a job somewhere else, or maybe they want to move somewhere with a lower cost of living,
or to be closer to family, etc., etc...
SYS64738 wrote to Dream Master <=-
think I'm trying to compare BBSes and our users to that of business
e-mail and messaging systems (Teams, Slack, Exchange, etc.) where each
is configured to the user's timezone and the BBS is configured to
whatever timezone it is sourced at. Even if we configure everything to UTC, user offsets could still be a "thing".
Excellent point concerning this already being done by business email servers.
Just a thought...
What if the time zone was derived from the location of the user's IP address?
El 1/4/22 a las 09:52, SYS64738 escribi:
MR> > interface or using dialup via a modem.
MR>
MR> hahah!
MR>
MR> how about if monkeys flew out my ass.
Using dialup is for those rare eccentric (re: crazy) people that are WAY TOO nostalgic. The days of dial-up sucked, but for a long time it was the only thing going.
dialup age was amazing...
Using dialup is for those rare eccentric (re: crazy) people that are WAY TOO nostalgic. The days of dial-up sucked, but for a long time it was the only thing going.
dialup age was amazing...
At the time, it was amazing. In hindsight or comparison to today's
broadband
Internet? Yeah, not so much... :-)
What if the time zone was derived from the location of the user's IP address?
It's a possibility.
approximate location based on their IP address. However, whenever I use it, the result is always Roswell, NM (weird on many different
Does anyone have any idea where I may be going wrong or what I can do to fix it? Below is the HTML code:
Re: Message Timezones
By: Digital Man to Martin Rayburn on Thu Mar 31 2022 15:34:48
What if the time zone was derived from the location of the user's IP address?
It's a possibility.
This just so happens to coincide with a project I have been working on. I came across this HTML code that is supposed to display the visitors
The code you shared is fine, nothing to fix. They really just think that you're in Roswell. They think I'm in Smiths Falls, Ontario, which is a lot closer to Ottawa than it is to Toronto, where I really am.
These services are rarely very accurate. You can try some others, but you'll get similar results, or it'll be accurate for you but not somebody else.
What if the time zone was derived from the location of the user's IP address?
It's a possibility.
This just so happens to coincide with a project I have been working on.
I came across this HTML code that is supposed to display the visitors
can you please post on the bottom
can you please post on the bottom
On the bottom of what? My comments were below (at the bottom) under the quotes.
Wow. I wonder why they even bother if it can't at least get you within a few miles of the actual location. I live nowhere near Roswell, NM, but that's where the geo-locate ip service thinks I am.
Re: Re: Message Timezones
By: Digital Man to Ragnarok on Fri Apr 01 2022 05:56 pm
dialup age was amazing...
At the time, it was amazing. In hindsight or comparison to today's broadband Internet? Yeah, not so much... :-)
True, not so much now, but I always thought it was pretty cool that the tech m to transfer computer data over them many years later.
Nightfox
This just so happens to coincide with a project I have been working
on. I came across this HTML code that is supposed to display the
visitors approximate location based on their IP address. However,
whenever I use it, the result is always Roswell, NM (weird on many
different levels...lol).
Does anyone have any idea where I may be going wrong or what I can do
to fix it? Below is the HTML code:
Wow. I wonder why they even bother if it can't at least get you
within a few miles of the actual location. I live nowhere near
Roswell, NM, but that's where the geo-locate ip service thinks I am.
True, not so much now, but I always thought it was pretty cool that
the tech m to transfer computer data over them many years later.
Nto that much different than saving data to cassette tape or sending morse code
Sysop: | Chris Anderson |
---|---|
Location: | Murfreesboro, TN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 39:39:36 |
Calls: | 58 |
Files: | 3 |
Messages: | 20,289 |