Thomas Eizinger

> Similar to the macOS client, does it make sense to disable the automatic upgrade check for packages managed by apt? When that notification pops up and the user clicks...

This can be merged once we release a new version of the GUI client.

How to find the TUN FD in Swift: https://github.com/WireGuard/wireguard-apple/blob/master/Sources/WireGuardKit/WireGuardAdapter.swift#L60-L90 How to open a new TUN FD on MacOS without a network extension: https://github.com/isotes/tun-open

In terms of testing, it might better to (automatically?) install draft releases on several Macs, have them connect to the QA env and then run automated scripts there. Because if...

cc @melekes Depending on how many problems you run into once you deploy `libp2p-webrtc`, we might want to consider devoting _some_ time to try this out instead of patching `webrtc-rs`.

@mxinden Any chance we can get this on the roadmap?

> @mxinden Any chance we can get this on the roadmap? If we want to do https://github.com/libp2p/specs/issues/544 (which I think is a really good idea), I believe this issue is...

I've opened an issue for the failed SDP parsing which is where we hit a roadblock when @mxinden and I last explored what it would take to switch: https://github.com/algesten/str0m/issues/164

The playground @mxinden and I have been using is here: https://github.com/thomaseizinger/str0m/tree/libp2p-webrtc-playground Will keep exploring on the side.

> The playground @mxinden and I have been using is here: [thomaseizinger/str0m@`libp2p-webrtc-playground`](https://github.com/thomaseizinger/str0m/tree/libp2p-webrtc-playground?rgh-link-date=2023-05-05T09%3A58%3A50Z) > > Will keep exploring on the side. I've tried #164 out and with an additional small change...