GreatMarko

No, no forum bug; moderators will merge very similar/identical posts on the same topic/problem into single threads. This makes it easier for devs to track and gauge the scale of a particular issue, allows users to share experiences/workarounds with others experiencing the same thing, and allows devs to respond to everyone affected by the same issue in one go.

all, I've moved this topic over to the Feature Requests forum; feel free to add your +1's, etc to this thread if you've not already contributed, so that the developers can gauge the popularity of this. The latest word on Android x86 support is as per RomanZ's post above from earlier this year: "We would like to add it in future, but I can't share ETA for now" Please bear in mind that BitTorrent Inc's resources are finite, and therefore priority has to be given in the first instance (especially whilst Sync remains in "beta") to the more popular operating systems/architectures. For example, in this forum there also are expressions of desire from the community for Sync support on Blackberry, Windows RT, MIPS, Firefox OS, Chrome OS, Illumos / Smartos... to name but a few, in addition to Android x86 support! (and there's dedicated threads in this forum for each of these as well) So, as the developers have indicated, they are aware of a desire for Android x86 support, and would like to add it in the future. In the mean time, the best advice would be to add your +1's to this thread so the devs can gauge the level of interest in this.

The correct link should be: http://www.bittorrent.com/sync/api ...and click the "Request API Key" button. I'll get this to be updated on Sync-Help, but thanks for reporting!

I'm sure RomanZ will take you up on your offer, but FYI, the current version is actually 1.4.83.

The correct link should be: http://sync-help.bittorrent.com/customer/portal/articles/1642672-android-ui-sharing-backup-key- I'll get this to be updated on Sync-Help, but thanks for reporting!

It should be right under those:

I encounter a very similar problem with Office (2010) and Sync 1.4.x also! When saving a file to a folder that Sync is monitoring, maybe about 1 out of every 10 saves produces this: I did identify this in the early "alpha" stages of 1.4 (and it's still present with the latest 1.4.83 build too), unfortunately though, I seemed to be the only one to encounter this, and the devs were unable to reproduce. May I ask what version of Office you're using?

Have a look at "Why can't I connect to the Web UI on myip:port in 1.4? - I could in 1.3!" in the Unofficial Troubleshooting FAQ

See this post

That's because only one bug was fixed between .82 and .83, and it wasn't that one! (see the first post in this thread)

@adonnan, please continue Yosemite-related discussions in this dedicated thread, where RomanZ has already asked you what exactly isn't working for you.

Whilst this issue is know to the devs, it was not fixed in time for 1.4.83 - see this post.

Not to my knowledge! Firstly, not every beta build ends up getting pushed via auto-update, those that do are often not until several weeks after they first become available for manual download. Which beta builds are chosen (and when) to be pushed via auto update is essentially based upon which are considered more "stable" (for a beta) to be released to users en masse via auto-update. So, please keep providing your feedback on 1.4.x builds on the forums, so that the devs can judge which are suitable candidates for auto-update.

Care to elaborate?

Indeed - that's why I've come back into this thread to draw your attention (and others reading this thread) to the fact that there is now a dedicated thread for 1.4.83

See this thread. Also, public direct download links will follow - please be patient!

Hi Folks, Sync 1.4.83 is now available for manual download from the main site (or via direct links here) Note: This build isn't yet available via auto-update Sync 1.4.83 Changelog: - Fix UI when https usage forced (Linux only) The changelog for the previous build (1.4.82) may be found here. Important Notes on Sync 1.4: Downgrade to 1.3 is not possible after installing Sync 1.4. (If you wish to downgrade - please uninstall Sync removing all settings, then install 1.3 and configure all folders from scratch)

Yes! But ONLY if you have IE<9 installed. The Web UI isn't currently available if you're running IE9+ (although the devs are working on this!) When installing Sync on a Windows machine with IE<9, you'll see the dialog I mentioned in the first post. Clicking "OK" will install sync and then immediately pop open your default browser showing the Web UI. Each time you then run Sync subsequently, again your default browser will be opened to the Web UI

To be fair though, BitTorrent Sync has yet to leave "beta", so whilst its great that others are coming up with all these ideas, it's worth bearing in mind that because Sync is currently in "beta" things can - and do - change during the course of development. If developers can't accept and/or keep up with that, then, yes, it's probably best that their projects are put onto the "back burner" until they either have the time/resources needed to maintain their own projects during the "beta" phase of Sync, or until Sync itself leaves "beta" and becomes "stable". In the meantime, a number of other developers are currently offering their own "cloud storage services for Sync" (not affiliated with/endorsed by BitTorrent Inc)

Downgrading from 1.4 to 1.3 is not possible - their databases are incompatible. If you wish to revert back to 1.3 you'd need to remove all settings, then install 1.3 and configure all folders again from scratch

Please see this thread. Also there's a dedicated forum for API/Developer related stuff here.

What's wrong with using the API?

Links are secure and do not contain your "secret" - Please see this post and this article. You can also paste links directly into Sync via the "Enter Key" dialog

...and just to update this thread; in the latest build (1.4.82) the version number is now also clearly displayed at the bottom of the "Preferences" dialog

I'm afraid so - or alternatively, run Sync with a config file and specify a fixed "listening_port" there