I wrote an IRC frontend for Bird-lg-go some time ago, with a custom parser to display traceroute output more compactly. However, I didn't realize at the time that Bird-lg-go uses its own format as well, leading the parsing results to be a bit inaccurate (it expects, for example, that destinations timing out have * at the end of the trace). Rather than change the code to fit bird-lg-go's format, I thought it'd be useful and more portable to optionally provide the raw traceroute output instead.
I wrote an IRC frontend for Bird-lg-go some time ago, with a custom parser to display
tracerouteoutput more compactly. However, I didn't realize at the time that Bird-lg-go uses its own format as well, leading the parsing results to be a bit inaccurate (it expects, for example, that destinations timing out have*at the end of the trace). Rather than change the code to fit bird-lg-go's format, I thought it'd be useful and more portable to optionally provide the raw traceroute output instead.