| 15 Mar 2026 |
 sterni | I think wolfgang doesn't have the time for it at the moment, but I'm not sure. | 13:42:04 |
| sterni | the thing is also that the Haskell opentracing implementation seems to be maintained still (had a release last year) and does not actually depend on any of the upstream opentracing packages. | 13:43:49 |
| sterni | so it does not seem to me like it needs to be removed | 13:44:01 |
 eveeifyeve | But the protocol has been deprecated/archived, so it will not work. | 13:48:57 |
| eveeifyeve | * But the protocol has been deprecated/archived for open telemetry, so it will not work. | 13:49:40 |
| eveeifyeve | See https://github.com/opentracing/specification/issues/163 | 13:50:33 |
| eveeifyeve | * See https://github.com/opentracing/specification/issues/163 for more info | 13:50:38 |
| sterni | well i mean if you still have an opentracing compatible server and client it will continue to work the same as it used to | 13:55:51 |
| eveeifyeve | Lightstep has been deprecated/archived so that can be removed. I have also opened up an issue upstream: https://github.com/kim/opentracing/issues/55 | 13:56:28 |
| sterni | i agree it doesn't make sense to keep maintaining this stuff, but it's also not like anything bad is going to happen if it's still around | 13:56:45 |
