51–60 of 98 posts
> Determine if the BlueJeans desktop application is already installed. This allows us to offer a new installation or launch the existing app based on the user's machine.
If the "Detector" is installed, but the desktop app is not the user removed the BlueJeans app at some point because they didn't want it. How is silently installing it again against the user's prior wishes a reasonable behaviour?
Earlier quoted context omitted.
join.me seems to have solved this problem effortlessly, and taking a gander at procs, I only see a client running. The BlueJeans rationale here isn't passing my anecdotal sniff-test...
Only problem I've found with join.me is performance. My experience may not be common, but there is so much stuttering with join.me that it's unusable... And I've tried it multiple times on different days with different people.
Why is this news? A lot of desktop applications do this. The Spotify client used to do it to enable play/pause controls from any webpage. Dropbox also definitely used the same method for single sign on, maybe still does, I don't use it anymore.
I guess I'm losing touch with the user-hostile "innovations" coming out of the valley.
Earlier quoted context omitted.
Ahem. https://developer.apple.com/terms/apple-developer-agreement/...
And you are not forced to abide by the developer terms to release a program for the Mac just as I said. Despite all of the HN conspiracies, you can develop for and release code on the Mac without Apple’s permission. You don’t have to abide by those terms.
If you want to distribute an unsigned app and guide users into bypassing Gatekeeper for it, by all means, do so... but that's not what's happening in this case, nor is it particularly common due to the intentional hoops they make you (or more accurately, every single prospective user of your app) jump through.
Earlier quoted context omitted.
Ahem. https://developer.apple.com/terms/apple-developer-agreement/...
And you are not forced to abide by the developer terms to release a program for the Mac just as I said. Despite all of the HN conspiracies, you can develop for and release code on the Mac without Apple’s permission. You don’t have to abide by those terms.
For those who don't want to (or cannot, due to the nature of their application) use the Mac App Store to distribute software, the requirements will only continue to get more specific until (to the extent possible) all executable code and resources are notarized and signed with an identity.
The "log out" part is because the webserver will presumably continue running in memory after deleting the app until you force it to quit. It's possible that it watches for the app to be thrown away, but I don't have any way of testing that right now.
It looks like if you delete Blue Jeans.app and then restart (or log out), the webserver won't relaunch. It will attempt to run on load, but the actual script to start it invokes the app binary with a special argument, so deleting the app is sufficient. The "log out" part is because the webserver will presumably continue running in memory after deleting the app until you force it to quit. It's possible that it watches…
I don't understand the rationale here: > Determine if the BlueJeans desktop application is already installed. This allows us to offer a new installation or launch the existing app based on the user's machine. If the "Detector" is installed, but the desktop app is not the user removed the BlueJeans app at some point because they didn't want it. How is silently installing it again against the user's prior wishes a reas…