Discussion, talk and tips
https://forum.puppylinux.com/
I can run .sfs as spot or standalone apps copied into the spot folder as spot, but I cannot run a symlinked standalone app as spot.
Is this a sign of the limited user working and the boundaries of what is possible?
I symlinked from Opera-portable and Zoom-portable which stored on sdb3 to /home/spot on a Fossapup64 installation on sdb2. The Opera failed to run due to profile related errors, but not permission errors as may be expected. I didn't investigate if I could get it to run any further.
With the Zoom portable it ran successfully, although I had a strange issue. When I attempted to log in I was not able to enter an @ symbol for my email address. I tried typing it in a test file and copy/paste, but the @ symbol was dropped. Characters entered with the Shift key were not typable. I had no issues like this as root. I then attempted to access a meeting I have for Monday, I received the waiting for host screen. I was however able to successfully test audio/ video.
To run the portable, in a terminal I cd'd to the /home/spot/Zoom-portable, then issued the command run-as-spot ./LAUNCH. Note that the name appears spot in the log in window.
@TerryH I've noticed profile-related errors too but did not monitor the feedback of every attempt. I guess I am trying to understand if spot symlinks are categorically foolish or a special condition.
I was in Zoom this week too via Brave in 64 Xenial. For the client I am skeptical about diminished privacy (like Android apps), but one thing I noticed different this week's meeting vs. last (not recent) Zoom session is the comment/chat function.
This week there was only a raise hand feature for a/v participation via browser or call-in. I had no feedback either in the browser or from the meeting about my hand being recognized. I don't know if it worked.
I assumed chat for a meeting can be disabled by the facilitator, if features have not been changed or just limited to the client. Last meeting they worked well.
It does not seem possible that limited users can thwart typing the same way they thwart media access outside of spot. Function, yes, but dropping typed characters?