You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that Syncthing-fork is the "official" Android client, I wonder where usage/crash report data is sent. Is it sent to @Catfriend1 or The Syncthing Foundation?
I ask because if The Syncthing Foundation receives a crash report generated by Syncthing-fork, I'm guessing it would be ignored?
If that's what's currently happening, I'd be inclined to file an enhancement request for that data to be sent to @Catfriend1.
The text was updated successfully, but these errors were encountered:
If it's in Syncthing Options, it appears to just control the configuration (xml) for the underlying binary of official Syncthing, which sends reports to The Syncthing Foundation.
I think that xml thing applies to anything in Syncthing options.
I don't think abrupt closes with no panics are reported, which is how it would behave if the Syncthing-Fork wrapper completely crashed, or was force stopped.
The reports are sent to the Syncthing-Foundation. They are the people creating the SyncthingNative binary, which this wrapper includes.
The main Syncthing project documents which data is sent, if you accepted the consent screen. You can also manually enter a different url using Syncthing's web ui and configure your own endpoint to receive reports.
Now that Syncthing-fork is the "official" Android client, I wonder where usage/crash report data is sent. Is it sent to @Catfriend1 or The Syncthing Foundation?
I ask because if The Syncthing Foundation receives a crash report generated by Syncthing-fork, I'm guessing it would be ignored?
If that's what's currently happening, I'd be inclined to file an enhancement request for that data to be sent to @Catfriend1.
The text was updated successfully, but these errors were encountered: