TZUTC: -0500
MSGID: 7631.asian_li@1:275/100 2454b8e1
REPLY: 2:221/1.58@fidonet ec02c8fb
PID: Synchronet 3.14a-Win32  Dec 31 2006 MSC 1200
TID: SBBSecho 2.11-Win32 r1.182 Dec 31 2006 MSC 1200
  Re: only check/reply to messages every 2 months or so?
  By: August Abolins to Carol Shenkenberger on Fri Jan 01 2021 11:47 am

 > Hello Carol!
 > 
 > ** On Friday 01.01.21 - 10:01, Carol Shenkenberger wrote to August Abolins:
 > 
 >  >> PMFJI, but I still have fidonet messages tagged for replies that
 >  >> have accumulated beyond 2 months.  :(
 > 
 >  CS> LOL!
 > 
 > Often, when I revisit the older-than-2month "tagged for replies"
 > messages, I can't remember Wtf I had in mind as a reply.  :/
 > Sometimes it comes back to me in a few seconds, so then I may
 > decide to keep them on the back-burner a little while longer.
 > 
 > Sometimes I later realize that someone else may have delt with
 > the topic.
 > 
 > This is part of the reason I think sysops should never let an
 > echo to completely purge of all (old) messages.  Instead, try to
 > keep at least a modicum selection of say "the last 200" or so.
 > 
 > 
 >  CS> BTW, saw some silly dust ups about the telegram bit.  Best
 >  CS> to tell them it's from our standpoint much like a fancy OLR
 >  CS> that works well in a world of tablets and such technology..
 > 
 > Thank you for that. I'd like to forward your full comment to the
 > FIDONET.TELEGRAM echo.  It may serve to educate new sysops/users.
 > 
 > 
 >  CS> Technically when Dale Shipp was feeding me traffic on the
 >  CS> USS McHenry then USS Essex, we dove off to an email to email
 >  CS> delivery with OLR on each end.  Similar in concept.
 > 
 > OMG.. "our" data was being transmitted to various USS ships
 > without our prior knowledge!  What about privacy, what about our
 > rights! What unsavoury servers are utilized on those ships?  Or..
 > even what over-the-air non-FTN techonolgy was used for
 > transmissions?  The horror.
 > 
 > I know one sysop who implemented a mechanism to forward netmail
 > to his user's cell phones in the early 2000's.  Surely, a lot of
 > "unkown" servers and systems would be involved in-between.  Noone
 > seemed to be bothered by that.
 > 
 > 
 >  CS> Explain it more simply like that and the yahoos will quiet
 >  CS> down.
 > 
 > Too late. Less than just 2 weeks of implementation, a couple of
 > modertors changed their minds (they approved the transmissions
 > previously) about this alternate OLR after only a couple other
 > people raised questions.
 > 
 > The experiment lost WIFI, X-FILES, NZ_FIDONET, WHAT'S_HOT! &
 > RETAIL_HORROR ..all good candidates for the independent chat
 > style of messaging.
 > 
 > Maybe you can help dispell any fears?
 > 
 > 
 >  CS> I'm sure all here will happily help with any formatting
 >  CS> issues.  I opened the gateways for testing here some 10
 >  CS> years ago and no one has ever minded!
 > 
 > A lot of formatting issues have already be delt with. It is still
 > a work-in-progress. Inner-message quoting like in this reply
 > would be somewhat awkard on a smartphone - but I have done it.
 > 
 > MSGID/REPLYID was implemented very quickly. Even netmail delivery
 > to the Telegram user was streamlined.
 > 
 > If the goal is to make echomail accessible to the ways that
 > people use devices now, the Telegram app is a fine OLR-type of
 > thing. The desktop app is really not much different than having
 > to use an OLR program just to read QWK packets.
 > 
 > It's great even just to get annoucments that echomail has
 > arrived.
 > 
 > BTW, are you still biding your time on USS ships?
 > --
 >   ../|ug
 > 

Grin retired since 2009 from the Navy but still working!  You are welcome to
pass my message where need be.

LOL, humm, transited cable company email  (RR?  COMCAST?  COX?) to Navy servers
(pre-NMCI), then the UARNOC to the NOC in Hawaii then probably diverted
depending on ships location to Austrailia, India, or Bahrain for pickup on
board the ship, then ISNS servers on board to my email, then floppy to laptop. 
Replies would have followed same chain to ship servers but would have bursted
to Australia, Yokusuka, India, Bahrain outbound (whichever was current PtP
site at the time).  Shall we add a variety of satillites that are not
commercial?  Oh, EHF and SHF come to play.  UHF lily-pad might have been used
at times (where you burst to a larger deck's servers in close range and they
carry it onwards).

Key thing is in the end, it functionally was an OLR.

I'm the only ZC to have functioned from a US Navy ship at sea. 

Folks questioned it at the time but I kept low key answers on 'using email'
which quieted them.  For your methods, it really is operationally an OLR.  It
may be driven by BinkP pickup or something else, but it remains 'P2P'.

  xxcarol
--- SBBSecho 2.11-Win32
 * Origin: SHENK'S EXPRESS, shenks.synchro.net (1:275/100)
SEEN-BY: 1/123 18/200 57/0 90/1 105/81 114/705 120/340 123/120 131
SEEN-BY: 153/250 220/70 226/17 30 227/114 229/101 424 426 452 664
SEEN-BY: 229/1016 1017 240/5832 249/206 317 400 250/5 8 267/800 280/464
SEEN-BY: 298/25 305/3 317/3 322/757 340/1000 342/200 633/280 770/0
SEEN-BY: 770/1 100 330 340 772/0 1 210 220 230
PATH: 275/100 261/38 320/219 203/0 280/464 770/1 317/3 229/426