aaronliao

Hey willjasen, Cool project! You're right about the cloud "shyness" - the entire premise of Sync is that your data moves from device to device without a required stop in the cloud, thereby eliminating a third location where an attacker could potentially compromise your data (while also eliminating the bandwidth hit as well as cost). With cloud storage, the security of Sync wouldn't really be the issue - the introduction of 3rd party storage would now be the weakest link. I'm not saying that AWS is weak or easy to compromise by any stroke of imagination, just that now your data sits somewhere else - a place with traditional login credentials...Some food for thought That said, I'm thrilled to see the work you've done on rainstash - this looks like a great tool for folks looking to use Sync with AWS - looking forward to seeing your progress on rainstash! aaron

send me a PM or email with your requesting email address thejae. thanks! aaron

Yup!

Thanks RomanZ - pinning this one

adam1v - thanks for bringing this to my attention. Can you post some details about your configuration (ver of Sync, which Synology devices, etc?) Thanks! aaron

This is an interesting and somewhat unfortunate development. Although it appears that it's already too late (syncmade.com 404's for me now), I would like to invite Syncmade to discuss the bugs that are prohibitive to them or let me know who they attempted to contact at BitTorrent in an effort to get questions answered or to partner with us for marketing purposes. In my time working on Sync, I haven't seen a single inquiry from the Syncmade team - and as Sync's Developer Evangelist, any concerns Syncmade had would have been a top priority for me! The same goes for any and all other Sync API developers out there - got a question or concern? I'm here to help. I have posted numerous calls for projects/papers so that projects like Syncmade can be featured on the BitTorrent blog/elsewhere (like Wired!) and have gotten great responses. Here are a couple examples: Forum Post - Call for Blog Topics Blog Post - Sync Dev: Q&A with the Creator of Sync's Linux Desktop GUI Package - check out paragraph 1: And last but certainly not least, Jack Minardi and Jon Seymour - developers buliding on the Sync API - got some great coverage in Wired just by having a chat or five with me about what they were building and providing their time to answer questions for Ryan Tate @ Wired: BitTorrent Sync Apps Offer Escape From Big Brother So, I'll say it again - are you working on something awesome that's built on the Sync API? Is there something about the API that's creating a blocker for your project? I want to hear about it and I want to get you sorted out and drive traffic/attention towards your project! Find me here on the forum, on Twitter @aaronliao, or via good old email - aaron [at] bittorrent [dot] com. Lets talk! aaron

Yes, the title is supposed to be slightly comedic, but believe it or not, I've gotten at least a few emails that read just like the title and this question also comes up fairly often on this forum, so I'm going to sticky this one for future reference. I personally read, approve and process every API key request that comes in via the Sync Developer website. I like to tell folks that it may take ~72 hours for their key to arrive, but please allow +/- 72 hours if you request a key on a US holiday, on a weekend, etc. "But it has been 72 hours + 73 hours and I STILL haven't received my key!!! What gives?! Are you ignoring me?" Absolutely not Here are a few things that might help. First, your API key email will come from "no-reply@bittorrent.com" - I feel almost patronising saying this, but please check your junk folder for the API key. Next, we use Mailchimp to send out the automated API Key Welcome emails. Mailchimp does not allow role-based emails. More info on that here: http://kb.mailchimp.com/lists/growth/limits-on-role-based-addresses "OK, I've checked my junk folder and I'm not using a role-based email and I still have received my key - it has been 245838975398745 hours since I requested it. What now?" At this point, it makes perfect sense to shoot me an email to ask what's going on I'm aaron [at] bittorrent [dot] com. Hope this helps! aaron

Glad you got your key - I approve and process all of the keys manually and it's just me doing it - so ~72 hours is usually a safe amount of time for me to tell folks to wait. I really need to sticky this at the top of this forum - this topic seems very popular aaron

Looking into this. Thanks for the heads up folks!

No changes in 1.4

Still working on this =]

Yes! The idea we are kicking around is having a blog entry on the BitTorrent blog that would be a living document that I update with new implementations. How does this sound? aaron

Hey folks, I don't know if you guys follow the Sync Dev Blog, but this week I've got a Q&A with another cool decentralised project - MeshedSites.com Previous featured guests have included our own "tuxpoldo" =] Head on over and take a look http://blog.bittorrent.com/2014/07/31/sync-dev-qa-with-the-creator-of-meshedsites/ I'm always looking for more awesome projects to highlight and talk about - if there's something you'd like to see covered or are working on something yourself, let me know! aaron

Give me a day to ask around =]

This is a great idea and I'd really like to see it happen - happy to lend a hand where I can and would be really excited if the community got this going! aaron

Hi Callum, Got your email and sent your key over! Thanks! aaron

Hi Mattia, Interesting idea - are you going to be using the encrypted sync feature from the API to sync the data? This would be something really cool to talk about on the blog once you get it going! aaron

Hi Callum, Shoot me a PM or an email (aaron at bittorrent dot com) with the email address you signed up for the API key with and I'll get you taken care of. Thanks for your patience. Hi j2b, Bummed to hear you haven't received your key yet! Lets get this taken care of - I'm PMing you your new key (it was sent out some time ago via our automated system) and will send you an email with it as well. Please let me know if you still don't get it =] aaron

Hey folks, My first few developer blog entries are up and live with the today's entry being a Q&A with our very own tuxpoldo here on the forums! http://blog.bittorrent.com/2014/07/10/sync-dev-qa-with-the-creator-of-syncs-linux-desktop-gui-package/ Previous entries here: http://blog.bittorrent.com/2014/05/01/hello-world/ http://blog.bittorrent.com/2014/07/03/sync-dev-a-look-into-how-keys-formerly-known-as-secrets-work/ What topics would you guys like to see covered next? aaron

1. There isn't a queue length - turnaround is usually ~72 hours. Your key was requested right before a holiday weekend in the US, which might explain the delay =] 2. Yes, one key should be fine! 3. Not really, no. Easiest way is to PM/email me if you don't receive the automated email. 4. no-reply@bittorrent.com Thanks for your patience! aaron

No apology necessary! I'm stoked that you are anxious to get your key and I'm excited to get it out to you so you can start building awesome things. Thanks again for your patience and hang tight - key coming your way soon =] aaron

Hi BeryJu, Your key was requested <72 hours ago on Saturday 6/21/14 at 2am in the morning my time - I wasn't at work then =] Your key will be processed and sent out today. Thank you for your excitement and patience! aaron

Cool project built on our API!

Thanks for bringing this to my attention - looping in a few other folks to get to the bottom of this =]

Could you tell me a bit more about your configuration? OS, version of Sync on host/peers, etc? aaron