@Tech Dev Oldsmar wrote:
This would be a killer feature. Hope it might happen.
😁 Better don't rely too much. Not on the Dropbox at least.
"would be a killer feature": why would be? 🧐 it is actually. While Dropbox application is installed on your machine and works properly, the feature is available there. Dropbox application is listening on loopback ports 17600, 17601, and 17602 where any other application can connect and communicate to the application. That's exactly what Dropbox website does (or tries to at least) when you select on the site to send a command to open particular file/folder (and other commands).
It's another story that all available already features (the one mentioned within current thread and many other features too) are completely undocumented and so difficult to use. 😕 Such ideas are relevant to Dropbox application developers work, not to web API developers, unfortunately. Proven over time developers of the application are too lazy (just take a look on application release pages and try count word "lazy" in posts there from different users and not only) - just opposite of API (web by default) developers and support.
If you are DIY fan try be a man on the middle. 😉 Listen on 17600 (before Dropbox application launch) for websocks queries and forward them to 17601 for example (one to one). Log entire traffic and analyze it. In such a way you would be able catch and reproduce the pattern and perform proper queries to the Dropbox application through your own application while mimics the Dropbox web site. 🙂