A follow up…
First, it is disappointing finding out that different methods are adopted without ensuring clean support across many different aspects. I’m looking at the adoption of Wayland - and the abandonment of wayfire without cleaning up the mess left behind. Especially on the R Pi 5!
To fix some of my display issues with the “Official” 7 inch display, I ended up re-flashing my SD to Raspberry Pi OS Lite - 64 bit Bookworm. Then I installed the GNOME Desktop through tasksel. I’ve enabled some GNOME extensions which have improved the display interactions and on-screen keyboard. I’m quite satisfied with this outcome - except …
I mentioned not wanting to do this because of Raspberry Connect. It does not work with the RPi OS Lite Edition WHEN using another Desktop Environment. Only the SSH side works - not what I want. I’ve looked into other VNC and RPD solutions - but there are downsides here, either because of transition to Wayland (RealVNC and TeamViewer), or because to get it to work, you have to create a different user “account” on the pi. That defeats the purpose of trying to access the existing user account either from another device on the same LAN, or completely remote (away from home). There is also the desire (my requirement) of not having to use special firewall port breaks - I just don’t want the hassle, and possibility of comprise with exposure to my Smart Home devices - especially, because the RPi I want to connect to will be displaying a dashboard for the Smarthome.
I’ve come back to the technology explanation behind Raspberry Connect - WebRTC - web Real Time Communication. It seems most implementations of this method are with the audio and video sharing. The data sharing side of this implementation seems to still be “getting off the ground.” I’m still looking.
First, it is disappointing finding out that different methods are adopted without ensuring clean support across many different aspects. I’m looking at the adoption of Wayland - and the abandonment of wayfire without cleaning up the mess left behind. Especially on the R Pi 5!
To fix some of my display issues with the “Official” 7 inch display, I ended up re-flashing my SD to Raspberry Pi OS Lite - 64 bit Bookworm. Then I installed the GNOME Desktop through tasksel. I’ve enabled some GNOME extensions which have improved the display interactions and on-screen keyboard. I’m quite satisfied with this outcome - except …
I mentioned not wanting to do this because of Raspberry Connect. It does not work with the RPi OS Lite Edition WHEN using another Desktop Environment. Only the SSH side works - not what I want. I’ve looked into other VNC and RPD solutions - but there are downsides here, either because of transition to Wayland (RealVNC and TeamViewer), or because to get it to work, you have to create a different user “account” on the pi. That defeats the purpose of trying to access the existing user account either from another device on the same LAN, or completely remote (away from home). There is also the desire (my requirement) of not having to use special firewall port breaks - I just don’t want the hassle, and possibility of comprise with exposure to my Smart Home devices - especially, because the RPi I want to connect to will be displaying a dashboard for the Smarthome.
I’ve come back to the technology explanation behind Raspberry Connect - WebRTC - web Real Time Communication. It seems most implementations of this method are with the audio and video sharing. The data sharing side of this implementation seems to still be “getting off the ground.” I’m still looking.
Statistics: Posted by KriegAdlerAU — Sat Aug 31, 2024 8:17 pm