home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   TUXPOWER      Advocacy for the Linux operating system      1,237 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 234 of 1,237   
   Maurice Kinal to mark lewis   
   one last check   
   08 Jun 15 01:51:21   
   
   -={ Sunday, 07 June 2015, 21:51:21 -0400 }=-   
      
   Hey mark!   
      
    ml> ok, so you're shipping a raw MSG file of your own format from your   
    ml> point to your node, right?   
      
   Yes except it really isn't my own seeing what is there resembles what would be   
   there in a packed msg as per specs.  I used to use a rfc-3339 DateTime but   
   later changed it back to the regular FTN formatted DateTime and added the   
   extra-special '-={ }=-' DateTime stamp at the top of the printable msg_body   
   which has evolved since it was first done to be configurable on-the-fly to   
   language and timezone, en_US.utf8 and EST5EDT (EDT) in this particular reply.    
   The point isn't currently set up to handle replies but could be if it turns   
   out to be something I am interested in continuing.  At the momemt I am using   
   it to test out the BSO idea for wireless mesh text messaging using binkd.  I   
   am guessing it will change soon but might live on to see brighter days in the   
   future.  No biggie if it doesn't though since I still have the node which I   
   will still use.  I honestly like using it especially given native utf8 support   
   etc. of vim.  I was thinking of writing a special vim msg syntax file for it   
   but so far I haven't bothered.   
      
    ml> on your node you have your own special tosser that handles your   
    ml> format   
      
   WeBeBashing on the node tacks on the binary parts as well as a pkt header.  In   
   this case, this reply is being done directly on the node but even then the   
   preliminary reply is exactly the same as it would be if I were using the   
   point's setup.  Only the uplink's packed messages require the binary data as   
   well as things like PATHs, etc.  Currently I don't display the tagline,   
   tearline and Origin to myself but I might start if I decide to split it off   
   into it's own field called footer, which seems to be an apt name for it.   
      
    ml> and does what is necessary to send on to other FTN systems?   
      
   Yes.   
      
   Life is good,   
   Maurice   
      
   ... Don't cry for me I have vi.   
   --- GNU bash, version 4.3.33(1)-release (x86_64-atom-linux-gnu)   
    * Origin: Pointy Stick Society - Ladysmith BC, Canada (1:153/7001.0)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca