25 Oct 15 09:36, you wrote to you:   
      
    NB> @MSGID: 1:154/10.1 a6b8f70f   
    NB> @PID: Hotdoged/2.11/Android   
    NB> @TID: jNode/Android   
    NB> @CHRS: UTF-8   
    NB> @REPLY: 592.hotdoged@1:154/10 1a921ff3   
    NB> Hello, Nicholas Boel.   
    NB> On 10/25/15 9:30 AM you wrote:   
      
      
    NB>> Changed that up. Let's see if it works now.   
      
    NB> And there you have it. Had to tinker with my tossed a bit to avoid   
    NB> circular path detection.   
      
    NB> Does hotdoged put it's 3d address in the path before sending the   
    NB> message out?   
      
   path and seenbys are only 2D...   
      
    NB> Since my boss node is the same 3d address.. It causes this circular   
    NB> path detection and wasn't sending the message onward. Disabling this   
    NB> check fixed it but I can't see that as a long term solution.   
      
    NB> --   
    NB> Regards,   
    NB> Nick   
      
    NB> Posted from my Android device (LG G3)   
    NB> --- Hotdoged/2.11/Android   
    NB>  * Origin: thePharcyde_ mobile Android device.. (1:154/10.1)   
    NB> @PATH: 154/10 10 123/500 3634/12   
      
   at least one of your systems is adding your /10 to the path line twice... what   
   tosser is your boss node using to process these messages from your android??   
      
   )\/(ark   
      
   ... Torontonians get freaked out when people on the subway talk to them.   
   ---   
    * Origin:  (1:3634/12.73)