Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    SYNCHRONET    |    Rob Swindell fetishistic worship forum    |    43,341 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 40,862 of 43,341    |
|    deon to Digital Man    |
|    JS Object save_msg()    |
|    19 Dec 24 20:45:14    |
      TZUTC: 1100       MSGID: 50218.dove-syncdisc@12:1/2 2bc9e554       REPLY: 50217.dove-syncdisc@12:1/2 2bc9d90b       PID: Synchronet 3.20a-Linux master/7b932f63e Dec 9 2023 GCC 10.2.1       TID: SBBSecho 3.23-Linux master/c33ca5aac Dec 18 2024 GCC 12.2.0       COLS: 80       BBSID: ALTERANT       CHRS: CP437 2       NOTE: FSEditor.js v1.105        Re: JS Object save_msg()        By: deon to Digital Man on Thu Dec 19 2024 07:52 pm              Howdy,              Following on from my previous message, I think I understand what is going on -       doesnt make sense to me why, but I get it.              I raised this thread, because a message I just saved with save_msg(), when       immediately read would display a message of "11hrs from now".              I looked further into the code, and understand what age_of_posted_item() with       smb_tzutc() is doing.              When Sync starts, xpTimeZone_local() shows the offset from UTC, and sends a       warning message on the console on startup, in my case its 660.              When saving a message with save_msg(), when_written_time, is populated with       time() if no value is provided, which is the UTC time when the function is       called.              When displaying the message, the age is calculated between the value of       when_written_time (which is utc), and time() [utc] minus xpTimeZone_local()       plus an offset (which might be negative) derived from scfg -> System -> Local       Time Zone. Since I had UTC there, it would be zero, so the age of the messages       is immediately 660s old (utc minus 660 plus 0).              Thus when when scfg -> System ->Local Time Zone equals xpTimeZone_Local(),       they cancel each other out and age_of_posted_item() is truely however many       seconds ago the message was stored. (utc minus 660 plus 660).              If this is what is intended, then OK, I get it. Why somebody would find this       useful I guess I dont understand.              :)                     ...лоеп              ---        ю Synchronet ю AnsiTEX bringing back videotex but with ANSI        * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)       SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10       SEEN-BY: 154/30 203/0 218/700 221/0 226/30 227/114 229/110 114 206       SEEN-BY: 229/317 400 426 428 550 700 705 240/1120 5832 266/512 280/464       SEEN-BY: 280/5003 5006 282/1038 291/111 292/8125 301/1 310/31 320/219       SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124       SEEN-BY: 467/888 633/280 712/848 770/1 902/26 5020/400 5054/30 5075/35       PATH: 103/705 280/464 460/58 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca