I think you may have misunderstood. Or mis-stated what you see as a problem. I don't think it is in the power of a single company like RealVNC to 'withdraw' VNC. (They are of course at liberty to introduce a charge for conveying your network traffic via their servers. As are Raspberry Pi.)Thank you. I understand that VNC is being withdrawn in less than a month from now and I am heavily reliant on VNC because all my Pi's run headless, so it appears that even in the short term, I will have to opt for a VNC subscription, unless labwc is a option, sooner rather than later?It will work on earlier Pi's once we move to using labwc as a compositor across all devices (rather than as it is currently with Wayfire on Pi 4,5 and X on 0,1,2,3)
Is all access to your RPi systems from remote workstations not on your own home LAN? (Because I don't think this change affects peer-to-peer connections within your own LAN.)
Do you need more potential remote access connections than RealVNC will continue to offer for free? (Because RealVNC continue to offer a free tier subscription.)
And finally, but not checked, maybe the solution identified by a senior RP Developer will work now if you take the steps needed to configure your target systems appropriately. (Because as stated the current default compositor in RasPiOS Bookworm remains based on X11 for lower-powered, low-memory systems.)
Statistics: Posted by B.Goode — Mon May 27, 2024 7:06 am