They said this hack was impossible
venturebeat.com
venturebeat.com
You shouldn’t need to jailbreak your device to make PDQ work;
the app alone does the trick. (Whether Apple and other app
store operators will allow PDQ on their marketplaces is
separate matter.)
The author of this article, and more worryingly the developers running a Kickstarter campaign, seem to have an insufficient understanding of the technical criteria upon which Apple admits or rejects apps.I was expecting some arcane optical-modem procedure where you point the receiving phone's camera at the sender's screen, which flashes a series of glyphs or something like a high-bandwidth QR code. That would've been cool. Instead it turns out that "even when they're offline" just means "we were lying about that part." Oh well.
I mean, assuming they actually did manage this, it wouldn't be portable either. It sounds like they'd have to implement their own driver, which would mean hardware dependence.. and then theirs the fact that they are apparently breaking out of the sandbox and getting direct hardware access, a major exploit..
I call BS
edit: Note, I know that wifi is capable of P2P/ad-hoc connections, and it's what bluetooth uses exclusively... The article seems to say that this app doesn't use that though and has these things disabled
"So while PDQ doesn’t require existing connections, it uses the existing wireless chips to send data across short distances, which could be useful during power outages or natural disasters. That means you can’t have your iPhone in airplane mode while using PDQ, for example, because then it wouldn’t be able to tap into its wireless chips."
Transfers even without power, as in wireless network routers/towers don't have power, but phones still do.
Yes -- a whole new incompatible layer.
I cannot tell you how many times I've heard this exact pitch during my long career in this business. "Our method breaks through the morass of incompatible, adversarial protocols" ... by creating yet another incompatible, adversarial protocol that refuses to work with any existing ones.
The only difference between this and Microsoft's classic "Embrace, Extend and Engulf" strategy is that small companies can only create a new niche protocol, hopefully soon to be forgotten.
Zeroconf was more than good enough. UpNp was more than good enough. And so forth. But no one is willing to adopt anyone else's universal, flexible, foolproof communications protocol.
Because that's basically what radios (and the software that controls them) are designed to do.
Cool stuff though!
The only radio that's disabled in Airplane Mode is the cell radio. WiFi and Bluetooth still work if you turn them back on (Airplane Mode turns them off, but does not disable them).
Maybe they didn't actually mean that or understand what they were saying. But that's what I'm saying: BS article.
And it's not like it really matters. You can hardly talk directly to the WiFi or Bluetooth chips from an iOS app sandbox either.
You may as well invest in a Kickstarter for a free energy machine.
There's no way apple will let this through. A lightly secured connection protocol that can talk to your device disk sounds like a security nightmare. A nice 0-day exploit and a stroll through a downtown BART station sounds like a blast.
So this will be FOSS, right?
Errr...
Further, while it disappoints me that you can't easily do point to point wifi between, for instance, iDevice and winphone, I'm not really surprised.
But I do not understand the bluetooth part. Granted, I have a very, very dumb phone so I'm not doing things like this at all, but I assumed that simple file transfer via bluetooth would work just fine between, say, iDevice and Android ... it's really troubling to learn that's crippleware.
I mean, that's the whole point of bluetooth.
At first it sounds like he's claiming that they created their own drivers for the wireless chips of seemingly every phone. Which is pretty much impossible (for them).
What's probably happening is they're enabling ad-hoc mode on the wifi chips, and enable bluetooth transport between any two devices nearby each other. Then their app deals with the addressing and routing of messages using some proprietary tunneling, with probably some kind of virtual network interface that talks to their app so they can communicate on multiple networks at once.
It's a neat idea that makes it easier to do networking between devices. But the title ("They said this hack was impossible") is incorrect. Ad-hoc wifi networks and bluetooth network transport works just fine with existing devices and no other software.
As usual, the idea with this piece and their website is to exaggerate as much as possible to drum up funding. If people figured out how boring this really is they might not get enough press.
I highly advise anyone interested in this to instead read the information on the Kickstarter page: http://www.kickstarter.com/projects/fasetto/fasetto-sharing-...
It seems that it just tries whatever the device offers. From the kickstarter:
"If Bluetooth isn’t available it can use near field, if near field isn’t available it can use WiFi Direct, if WiFi Direct isn’t available it can use hotspot, and if that isn’t available it can use root sockets (TCP, UDP or any other supported protocol, using any port)."
I'm not sure what "root sockets" means, or how UDP is going to allow you to transmit without WiFi, NFC, or Bluetoth.
Along the lines of "I don't have network and I want to share with someone else on a different platform and don't (or can't) use bluetooth/wifi".
Narrow population, but it would be a fun project to learn about sending data over an audio medium.
Get it working well and you might even be able to send data over a set of headphones/mic, although your data throughput would likely be slow as molasses.
[1] https://play.google.com/store/apps/details?id=com.hubski.com...
[2] http://sixteenmillimeter.github.io/Javascript-FSK-Serial-Gen...
I thought the app sandbox was designed to specifically prevent app makers from accessing the hardware in unauthorized ways. (I am guessing Android and Windows phones have similar ways of controlling access to the hardware). This seems like the exact use case that should be stopped.
There is simply no way what they're doing is kosher with Apple, nor should it be. For a sandboxed application to run custom drivers on my hardware defies any notion of security.
Jailbroken phones where people have acknowledged the risk of running things outside the sandbox? Sure. Great.
I find it interesting that their website announces that they're gonna be launching all of thei apps by January 2014, considering that their kickstarter hasn't ended, and that it's almost sure that Apple won't play along.
That said, I'm all up for a quicker way to share things with my friend's Android, so while the article is far from making me want to support this, I might give it a try once it's out.
I'm curious about the security layer. It sounds like a one-time pad kind of setup. If true, does that mean the devices involved have to be synched up in a different secured environment to share the encryption codes and the protocols on how they should be used?
Eventually it will offer phone calls and text messaging? So you can call people in the immediate vicinity?
Also, AirDrop doesn't share with Android and Windows Phones.
No, AirDrop does not require wifi or cellular. It uses Bluetooth LTE to scan for nearby phones and then establishes an ad-hoc wifi connection.
You can't use it if you have wifi turned off (or airport mode turned on), but it works whether you're connected to a network or not.
> Also, AirDrop doesn't share with Android and Windows Phones.
And as of November 19 2013, this does not either.
But it is not cross platform, obviously.