xla

> This conversation seems related to #589 and maybe we should try to flesh out a GRAND plan for telemetry and introspection :) RFC much

@geigerzaehler If you could conjure up debug logs from seed that correspond to the upstream peer that would help with narrowing down the interaction that is causing this.

Is this overlapping/superseding #68?

This is still relevant, but likely futile before the repository has further matured - which will likely coincide with proper versioning and a more stable spec. Until then this can...

@viraptor If you are feeling adventurous you can hop on the latest stack by running branches of Upstream and the Seed: https://github.com/radicle-dev/radicle-upstream/tree/xla/1236-thank-you-next https://github.com/radicle-dev/radicle-bins/tree/seed-net-next This will set you up with the...

What's the output of the `/membership` endpoint on the seed frontend when you run into this?

> More details to come. 

> How would we feel about having a separated package for our git stuffz that `radicle-link` and `radicle-surf` could depend on? eyes `radicle-stringly`

I think it would aid for library users, was hoping contribution back the streaming disco outlined here: https://github.com/radicle-dev/radicle-upstream/blob/c767063ecadae897cf4de37bc8c5f07a2a740f66/proxy/coco/src/config.rs#L117-L157

> Yes would be good, so we can replace it with a more efficient implementation. :100: