Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

OpenDrop: An open Apple AirDrop implementation written in Python

github.com

Post reply on HN
Print view View original

101–110 of 132 posts

Re: OpenDrop: An open Apple AirDrop implementation written in Python

#101

Post by quitit »

emsy wrote: post #29
mrtksn wrote: post #3

AirDrop is brilliant but it fails silently, no error messages - nothing. At best, it says that it was cancelled. Does anyone knows how to debug it? I also wonder, why this type of file transfer isn't the industry standart. It's so straightforward(when it works), why would anyone transfer files in any other way? Okay, maybe a transfer history can also be useful.

This is true for most Apple protocols in my experience. I’m supposed to be able to control my Homepod from my watch with a tap but it never works. Sometimes I can’t use the Homepod for minutes until it shows up. iMessage regularly fails to show the blue name for contacts, FaceTime is randomly unavailable for certain contacts, Airpods randomly disconnect, Airdrop rarely works. Tethering is also kind of spotty. The wat…

I find a lot of the grief with these protocols is driven by which wifi router is in use. When using the old Apple wifi routers I never had trouble with homekit, airdrop, handoff, airplay or any of the zeroconfig network stuff: as soon as I switched to other brands the issues would pop up (including ones that oddly seem to persist even after disconnecting from wifi - but then disappear when using a different user account on the same machine).

Because of this I feel Apple could do a hugely better job in all of their wireless protocols, as it stands the only truly stable networking appears to be between two iphones.

Re: OpenDrop: An open Apple AirDrop implementation written in Python

#102

Post by lelandbatey »

jkepler wrote: post #98

As a Debian and Android user, can anyone help me understand how AirDrop and this python implementation differ from or are similar to Syncthing and/or Firefox Send? Is it basicly the same idea?

Syncthing and Firefox send both incorporate a 3rd party publicly available server which both parties contact over the general internet.

Airdrop is done direct device to direct device, without intermediate, over wifi.

Re: OpenDrop: An open Apple AirDrop implementation written in Python

#103

Post by quitit »

samwillis wrote: post #20

I believe AirDrop is a a great example of how Apples vertical integration and full ownership of software and hardware really thrives. It may not offer interoperability with other platforms, but that’s because other platforms don’t have the control needed to implement the same level of integration of hardware and software needed. Without the direct low level control of the radio hardware they would not have been able…

They historically have opened source similar protocols, e.g. they open sourced rendezvous. But generally there would need to be an interoperability reason for them to do so. AirDrop seems like a good candidate for this.

Re: OpenDrop: An open Apple AirDrop implementation written in Python

#104

Post by KarlKemp »

mrtksn wrote: post #3

AirDrop is brilliant but it fails silently, no error messages - nothing. At best, it says that it was cancelled. Does anyone knows how to debug it? I also wonder, why this type of file transfer isn't the industry standart. It's so straightforward(when it works), why would anyone transfer files in any other way? Okay, maybe a transfer history can also be useful.

Console.app will give you all the error messages you ever wanted. And more.

Re: OpenDrop: An open Apple AirDrop implementation written in Python

#105

Post by jacob019 »

lelandbatey wrote: post #102
jkepler wrote: post #98

As a Debian and Android user, can anyone help me understand how AirDrop and this python implementation differ from or are similar to Syncthing and/or Firefox Send? Is it basicly the same idea?

Syncthing and Firefox send both incorporate a 3rd party publicly available server which both parties contact over the general internet. Airdrop is done direct device to direct device, without intermediate, over wifi.

Syncthing is p2p, a relay is supported for when both clients are behind NAT on different networks. It supports local network discovery, but the use case is different. It's for syncing files between your devices, not one off transfers.

Re: OpenDrop: An open Apple AirDrop implementation written in Python

#106

Post by lotsofpulp »

quitit wrote: post #101
emsy wrote: post #29

Earlier quoted context omitted.

This is true for most Apple protocols in my experience. I’m supposed to be able to control my Homepod from my watch with a tap but it never works. Sometimes I can’t use the Homepod for minutes until it shows up. iMessage regularly fails to show the blue name for contacts, FaceTime is randomly unavailable for certain contacts, Airpods randomly disconnect, Airdrop rarely works. Tethering is also kind of spotty. The wat…

I find a lot of the grief with these protocols is driven by which wifi router is in use. When using the old Apple wifi routers I never had trouble with homekit, airdrop, handoff, airplay or any of the zeroconfig network stuff: as soon as I switched to other brands the issues would pop up (including ones that oddly seem to persist even after disconnecting from wifi - but then disappear when using a different user acco…

Specifically with Homekit, a wired Apple TV and good quality home networking equipment with wired access points makes a world of difference. I use Aruba Instant On, but I have had good experiences with Orbi at higher prices and Linksys Velop at the lower end from Costco. Also, if you have a lot of Homekit stuff, it is best to use devices that have their own Zwave or Zigbee or whatever hubs that are then connected via ethernet into your network, to cut down on how much chit chat is flying around on WiFi, especially from cheaper quality homekit devices.

I am overall unimpressed with the consistency of wireless technologies, especially since Apple no longer makes the equipment that provides the backbone (the router/access points). You usually have no idea what quality radios and programming various wireless devices are equipped with, so it is just a crapshoot when dealing with it.

Re: OpenDrop: An open Apple AirDrop implementation written in Python

#107

Post by geophertz »

samwillis wrote: post #20

I believe AirDrop is a a great example of how Apples vertical integration and full ownership of software and hardware really thrives. It may not offer interoperability with other platforms, but that’s because other platforms don’t have the control needed to implement the same level of integration of hardware and software needed. Without the direct low level control of the radio hardware they would not have been able…

There's Nearby Share on Android.

Re: OpenDrop: An open Apple AirDrop implementation written in Python

#108

Post by geophertz »

jkepler wrote: post #98

As a Debian and Android user, can anyone help me understand how AirDrop and this python implementation differ from or are similar to Syncthing and/or Firefox Send? Is it basicly the same idea?

Nearby Share is the Android equivalent.

Re: OpenDrop: An open Apple AirDrop implementation written in Python

#110

Post by sudhirkhanger »

I have been having a huge problem getting pics and videos out of my partner's iPhone. We don't have a Mac or Windows to run iTunes. The only way I have found is to upload pics to Google Drive but then I have to keep the app open on iPhone until all pics are uploaded and bringing Google in between doesn't feel well.

Is there a way to transfer pics from iOS to Android wirelessly and locally similar to Xender or Nearby Share on Android.

Post reply on HN