Hello mark!   
      
   14 Feb 17, mark lewis wrote to Kai Richter:   
      
    ml>>>>> sbbsecho works properly   
      
    KR>>>> Then why the original poster is asking how to fix it?   
      
    ml>>> he wasn't asking how to fix golded or sbbsecho... he was asking   
    ml>>> how to fix the double tear and origin lines...   
      
    KR>> ...with golded and synchronet. I recived his mail too, that's why   
    KR>> you can't trump me with "alternate facts".   
      
    ml> don't insult me like that ever again... it is/was a configuration   
    ml> problem, not a software code problem as your statement indicated...   
    ml> your brush was too broad and the wrong color... i pointed that out and   
    ml> now you are the one dumping crap like that? piss off...   
      
   Calm down, review your arguments and you will understand why your point of   
   view deserves such a comment.   
      
   If you understand "fix a problem" by hunting bugs in software code, then you   
   know now why you didn't understand. For my point of view a solution for a   
   problem with the configuration is a fix too.   
      
   Or in other words: A misconfigured software does not work properly.   
   (even it's called sbbsecho, or whatever...)   
      
   You can draw even if you find out what the default behavior of sbbs is.   
   If sbbs does not touch an existing origin line by default, then i agree that   
   sbbs does work properly. In that case the sysop was responsible for the   
   misconfiguation.   
   If sbbs does replace the origin line by default, i still call it a bug, even   
   if the code works as designed. Modification of the origin line without   
   explicit configured by the sysop is a design bug in my point of view.   
      
   In any case, it was a not properly working system with golded and sbbs, which   
   is fixed now.   
      
   Regards   
      
   Kai   
      
   --- GoldED+/LNX 1.1.4.7   
    * Origin: Flying an airwave calypso (2:240/1351.7)