Beside not bugging the relay, (which is not my main concern) it's better to connect to the relay if an actual client is seeking service to provide better statistics for the metrics page.
Also you may don't wanna count these "false-alerts" in the status message of the add-on as it indicates a greater usage of the proxy than actually present.
I asked why I get these errors that FF can't connect to ws:xxx:9000 on Trac.
People using the bundle most likely don't set-up port-forwarding as they "just" use the bundle that includes Flash Proxy.
Please, see the response by arlolra. https://trac.torproject.org/projects/tor/ticket/9008#comment:1 and the commit https://gitweb.torproject.org/flashproxy.git/commit/c1768feacccd71bbba821299b95c809c82c2dee1
Beside not bugging the relay, (which is not my main concern) it's better to connect to the relay if an actual client is seeking service to provide better statistics for the metrics page.
The diff listing the changes: https://gitweb.torproject.org/flashproxy.git/blobdiff/e992fc9f441e3dd71ff6ac3e11aa9c27361a5abc..c1768feacccd71bbba821299b95c809c82c2dee1:/proxy/flashproxy.js
Also you may don't wanna count these "false-alerts" in the status message of the add-on as it indicates a greater usage of the proxy than actually present.
Edit: Fixed spelling mistake in the title