aaronliao

Members
  • Posts

    34
  • Joined

  • Last visited

Posts posted by aaronliao

  1. 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

  2. Have you emailed Aaron to chase it up, as outlined in his first post?

     :)

     

     

    I requested an API key 1 month ago and I haven't received it. zOMG!

     

    Has my request been denied?

     

    I even described the amazing things we are doing with Btsync here http://forum.bittorrent.com/topic/32216-geo-load-balancing-data-replication-alternative/

     

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

     

    aaron

  3. 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: 

     

    I’m constantly impressed by the variety and depth of Sync API projects out in the wild and aim to highlight some of these projects going forward.  If you are working on or have built something awesome using the Sync API – tell me about it!  Do you know a a great Sync API developer that you’d like to see interviewed here?  Let me know!

     

     

    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

  4. 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

  5. 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

  6. It would be nice if http://www.bittorrent.com/sync/developers/api would link to

    a page with a list of API implementations per programming language/platform.

     

    Since I assume the BTSync team has their hands full at this moment,

    it would be best if the community could manage this page.

     

    A forum post would be one option, but I'm pretty sure it'd get messy real soon.

     

    The API is great, but it's not for every developer and I don't think everybody

    should try to implement the API from scratch in their favorite language.

    Showing potential developers a list of available implementations might

    push them across the threshold as far as getting started with the BTSync API is concerned,

    thus expanding the user base of BTSync in general.

     

    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

  7. hi aaronliao, 

    I m looking for stories about sharing hd space between unknown, any suggestions?

    because I would like to try this kind of social experiment. 

     

    now trying to create the community here, in the "Sync Hacks" section  :)

     

    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

  8. Hey I too need to recover my API key. Can I request this to be resent?

     

    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, Callum!

     

    As aaronliao allready suggested, try to PM him after official request from your filled form (http://www.bittorrent.com/sync/developers). I still have not received new key in my e-mail, but I managed to find the old one (Email search helps in my case :) ). And as reply to my 2.question was confirmative, I still use formerly sent key.

     

    It seems, that something has changed @btsync, and even putting in Q4 e-mail into whitelist, still does not deliver one.

     

    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

  9. 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

  10. Please pardon me, if I rise this question again (I've noticed forum posts regarding a queue for API key distribution, so I'm patient, but still would like to get some expectations).

     

    1. What's current queue length (expected wait time), to get new API key (registered afternoon 03.07.2014 GMT+2)?

     

    2. Can a Dev use the same API key for several projects, or each project is advised to register separate API keys? (even if dev E-mail address is the same for all projects)

     

    3. Is there any other place, to get/recover or copy API keys, besides e-mail messages?

     

    4. What's the e-mail address, API key is sent from, to enter in Whitelist (for case of SPAM filters)?

     

    Appreciate your info...

     

    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

  11. Dear arronliao,

     

    I'm sorry, I didn't even think about time zones and I also forgot that it was a weekend

     

    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

  12. Dear arronliao,

     

    I too have benn waiting for my keys longer than 72 hours. The Email address I used is jenslanghammer[at]gmail.com

     

    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

  13. After switching my secrets over to the encryption secret for my server, I cannot get a complete sync. 600+ files are stuck in the queue. If I remove the file that sync is stuck on, then it gets stuck on the next file in the queue. Is anyone else having issues with the encryption secrets?

     

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

     

    aaron