What are you doing to prevent government tampering, MITM attacks, or other dangers? You seem to have put a lot of thought into the security of the implementation, though it might help you spread it to the do-it-yourself-er culture if you explained what you were doing a bit to keep things secure.<p>Is the cipher completely encrypted all the way from the phone to the desktop, whilst being tunneled through your server?<p>And if it's as secure as you say it is, what stops people from proxying their own arbitrary payloads through your tunnel? (-- that is to suggest that you're being as honest as you are about not decrypting anything the entire way from the phone through your cloud to the desktop...)<p>If it's that secure, what would stop a botnet from theoretically leveraging this as misdirection?<p>And what is the purpose of the cloud server here? If someone had their own hosting, would they still need to rely on your server to route the commands?<p>All questions and criticisms aside, I've always wanted something that could do this for my house without having to rely on an external entity... I think paranoia has taken a rather large toll in our culture today, because anything with the word 'cloud' in it starts to give all programmers the chills unless it comes with some assurances of trust, longevity, and ultimately devotion.<p>I'd almost suggest selling a piece of hardware that people could install in their houses, simply because it's extensible for your purposes, users can maintain control over it, and it's far more difficult to isolate as a target, and ultimately it allows people to decide whether to "connect indefinitely to any company" for continued operation.<p>I mean, if you pick up any cloud-based mobile control software from any major manufacturer today, they all create this massive problem of a surrogate dependency on the cloud in their implementation.<p>These days you can't even set up an IR mobile control product without sending out your wifi password through a web-based silverlight UI hosted in the cloud just to get it to the product that's meant to use it! That's so far backwards security-wise that it's teaching people to send their login credentials the wrong damned way!<p>Hopefully everyone sees what's going on here?
Works on my Nexus 4. Neat idea but it's already been done many times, unless I'm missing something?<p>I can pair the Youtube app on my phone with my TV the same way and search/play items from my phone.
This looks very cool. I had the same ideas, but for the slideshow control for remote control speakerdeck.com and slideshare.net [1]<p>The technology stack that I used is quite simple: Go Lang, Firebase and a bookmarklet. I plan to replace Firebase with CouchDb and TouchDB later.<p>If you can explain how you send the data between client and server, that will be a big help.<p>----------<p>[1] <a href="https://axcoto.com/qslider" rel="nofollow">https://axcoto.com/qslider</a>
Minor nit: On my phone, the placeholder text for the verification code input box reads "five digits". My code was "9tlni". Only one of those is a digit.
There's something funky with your QR code. My reader doesn't recognize it as a URL (it seems to be just the plain text type). There was also a space in the URL that I had to delete before my browser would recognize it as a valid URL. (fyi I'm running Cyanogenmod with their stock browser and the Obsqr QR scanner).
well this is the same hoby project that i am working on. The thing is this is not remote control for "browser". This is remote control for the api integrated web page. Mine project called "peegle" works with a chrome extension. So I can call it remote controller for browser. Just check it maybe we can do something together.
Nice idea but does not work on my fully up-to-date iPhone 5s. After putting in the code and tapping "Pair" the pair button just flickers slightly and nothing else happens. Tried with two different codes, rescanning the QR code each time.