A remote session would need the following four pieces:
1. An API for the remote access tool to request a remote display and
authenticate. This could involve a headless greeter session for remote
login or direct authentication of some sort.
2. A way for the login manager to launch a session in head
Thinking about this more, I'm not really sure extending the existing
Portal API makes sense.
Given that remote assistance (well served by the existing API) wants
* Explicit user consent to share
* To allow the local user to select what to share
* To mirror the selected existing displays / windows
> We are definitely interested in working in this area. We have a lot of
> the proposed core infrastructure that's listed in that proposed
> specification; pipewire, creation of virtual screens, libei access is
> coming soon. It's "just" a case of gluing everything together.
That's great to hear!
I'm on the Chrome Remote Desktop team at Google, and I am working to
add support for Wayland-based desktop environments. While our initial
focus will be on getting it to work with GNOME, we'd love the
functionally to be based on standardized APIs that can be used across
desktop environments, so I'm
