Another approach would be to integrate Firefox-specific D-Bus proxying inside of waypipe. Have waypipe listen to where Firefox normally does, if one is spawned

Another approach would be to integrate Firefox-specific D-Bus proxying inside of waypipe. Have waypipe listen to where Firefox normally does, if one is spawned on the remote host. I can imagine this being useful for more things, like portals going forward: one could imagine forwarding sound, video (both trough pipewire, negociated over D-Bus) and files this way.