Jonas Ådahl

After some IRC discussion, we'll need wireplumber to set up "roles" or something for the missing device classes. A starting point for this is https://gitlab.freedesktop.org/pipewire/wireplumber/-/merge_requests/455.

Something that came to mind during a related discussion: might want to create a new interface entry point, e.g. `org.freedesktop.portal.Devices` to avoid confusion about the existing method that's useless from...

One thing that comes to mind is, IMO it makes sense to allow the remote desktop portal to hook into the clipboard, but might be a good idea to split...

Just want to point out that on demand app provided PipeWire streams for previews for things the share can internally share is a much much much larger task than tweaking...

This should probably be something handled via PipeWire stream re-negotiation, not via the portal, since that is the place these things take place. For example, with virtual monitors, resizing can...

> Agreed. It will be nice to have portal/APIs to read/write from clipboard. That should probably be part of the remote desktop API.

> Virtual machines to replicate what spice-vdagent does I don't think the `vdagent` case is something that fits what portals are meant to solve; it works more like a driver...

Perhaps something like ```patch diff --git a/data/org.freedesktop.portal.RemoteDesktop.xml b/data/org.freedesktop.portal.RemoteDesktop.xml index 0a93ea4..6bc2ca6 100644 --- a/data/org.freedesktop.portal.RemoteDesktop.xml +++ b/data/org.freedesktop.portal.RemoteDesktop.xml @@ -134,6 +134,15 @@ more information about the @handle. + + hint s + +...

> I'd have chosen `description` for the name, but I agree it makes sense to have this Works for me.

> I would also like such option be available for the ScreenCast portal? I see no reason to limit it to the remote desktop portal. The remote desktop and screen...