You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reacted by Hugo, Julien Deswaef, Travis Plunk, Alex Lemann, Kevin Brubeck Unhammer, skicean, Anton Kaliaev, Max O'Cull, Ken Schnall, Chris [scuba.tech] and 58 more
Reacted by Kalcifer, Pihrra, Akash and Simon Deziel
I don't think it's possible to get an app approved that contains foreign binaries (such as a standalone syncthing written in Go). Go currently doesn't support being linked as a library to other C (or Objective-C) code, due to the runtime. So as it is, I think the only way forward that is guaranteed to succeed on that front is a pure Objective-C implementation.
it would be AWESOME(!!! repeat forever) if you guys included an example of implementing the protocol in another language.
aside yes i guess implementing the protocol in pure obj-c is the way however it seems i have nowhere to start (since lack of third-language implementation).
i am willing to make a big effort on the ios side but the objective would be to keep inside the frames of non-jailbreaked phones and free of course :-)
again "third party" implementation of protocol/functionality is highly needed
is there similar docs (have searched but not reaaaaly found any) for the network/transport layers.
i mean documentation on the establishment of lan/internet wide connections.
Yeah... Beware that while I always intended the block exchange protocol to be a stable standard, I haven't put nearly as much thought into the discovery protocol. That was always more of a half baked lets-do-something-and-see-what-happens thing that might lead into a DHT or mDNS or something in the long run.
Also a note on the BEP protocol is that the specs kinda vaguely say something about it typically being used with TLS over TCP. I'm considering mandating that or interoperability will be tricky in the future. From the beginning I was considering running it over UDP etc but I'm not sure there is a legitimate use case for anything not TLS/TCP.
yeah i guess an iphone app with "just" the ability to show an index of files using a predefined ip is a starter.
however if the discovery is not soon ot be set in stone then i guess it really disturbes development of third party stuff :-)
About the discovery specifically, I really feel that is an area where a single app like syncthing should not have to make up it's own thing. There should be a standard ready to use. I think that standard is mDNS w. DNS-SD and that is where I'd like to go. I just haven't had the time / energy / prioritization to go there when a custom thing was easier to get off the gorund.
I don't think any of the usual suspects are in any way interested in doing this, and be assured that doing it properly is a major piece of work. So I don't think there's anything to revisit, really.
Doesn't this fit the expressed goal of the project to be universally
available? iOS is still a major platform. I really wish I knew how to code.
I would love to help in some way.
Yes, I've done this - Syncthing can run just fine on iOS when compiled to a C library and started by a thin wrapper application that provides a web view for the GUI. But it's not a very useful thing.
@calmh Could you document how to compile into a C library? I'm a capable enough Swift developer to add the module map myself and export this as a proper Swift package, but I'm no good at understanding the build system of Go :)
It's 2022 now. Seems it still not not come out. I just wonder resilio also has a ios version. Is there any particular reason that syncthing still not support ios?
If it didn't fit our goals the issue would be rejected. Still needs someone willing and able to do it.
I think it's pretty clear why. People are expecting an iOS port to materialise out of thin air. It's an immense amount of work and no one is willing to volunteer the time needed to do it.
The $515 bounty obviously isn't sufficient. Perhaps the issue needs to be broken down into smaller pieces people might be more able to help fund in the near term?
What about creating a mobile web client and then making it an iOS app by embedding it in a frame? It wouldn’t interact with your file system obviously so no syncing but it would allow you to view the file system, down files, and maybe even add a built in file viewer like google drive. That way you get some interaction with syncthing and could be a good start to a full iOS client. It would also give users the option of a google drive style way to access their files without needing a client app installed.
I locked the issue as the intent here is clear. More comments that it's needed or how it might be done don't help. Someone "just" needs to do work. For any discussions or even better, if you'd like to work on it, reach out on https://forum.syncthing.net.
Activity
calmh commentedon Mar 24, 2014
That's an awesome initiative!
I don't think it's possible to get an app approved that contains foreign binaries (such as a standalone syncthing written in Go). Go currently doesn't support being linked as a library to other C (or Objective-C) code, due to the runtime. So as it is, I think the only way forward that is guaranteed to succeed on that front is a pure Objective-C implementation.
sloev commentedon Mar 24, 2014
it would be AWESOME(!!! repeat forever) if you guys included an example of implementing the protocol in another language.
aside yes i guess implementing the protocol in pure obj-c is the way however it seems i have nowhere to start (since lack of third-language implementation).
i am willing to make a big effort on the ios side but the objective would be to keep inside the frames of non-jailbreaked phones and free of course :-)
again "third party" implementation of protocol/functionality is highly needed
calmh commentedon Mar 24, 2014
Someone has to be the first third party, and it obviously can't be me since I'm the first party. :)
I would start with reading https://github.com/calmh/syncthing/blob/master/protocol/PROTOCOL.md and filing bugs on any ambiguities or other strange stuff.
sloev commentedon Mar 24, 2014
is there similar docs (have searched but not reaaaaly found any) for the network/transport layers.
i mean documentation on the establishment of lan/internet wide connections.
filoozom commentedon Mar 24, 2014
Are you talking about the discovery?
https://github.com/calmh/syncthing/blob/master/discover/PROTOCOL.md
sloev commentedon Mar 24, 2014
yes thanx.
i know its not good githubing to mention issues in issues in .... but that site is not listed from the wiki. :-)
calmh commentedon Mar 24, 2014
Yeah... Beware that while I always intended the block exchange protocol to be a stable standard, I haven't put nearly as much thought into the discovery protocol. That was always more of a half baked lets-do-something-and-see-what-happens thing that might lead into a DHT or mDNS or something in the long run.
calmh commentedon Mar 24, 2014
Also a note on the BEP protocol is that the specs kinda vaguely say something about it typically being used with TLS over TCP. I'm considering mandating that or interoperability will be tricky in the future. From the beginning I was considering running it over UDP etc but I'm not sure there is a legitimate use case for anything not TLS/TCP.
sloev commentedon Mar 24, 2014
yeah i guess an iphone app with "just" the ability to show an index of files using a predefined ip is a starter.
however if the discovery is not soon ot be set in stone then i guess it really disturbes development of third party stuff :-)
calmh commentedon Mar 24, 2014
Agreed. Lets have a discussion about that when the first third party project is at the point where it's relevant. :)
calmh commentedon Mar 24, 2014
About the discovery specifically, I really feel that is an area where a single app like syncthing should not have to make up it's own thing. There should be a standard ready to use. I think that standard is mDNS w. DNS-SD and that is where I'd like to go. I just haven't had the time / energy / prioritization to go there when a custom thing was easier to get off the gorund.
sloev commentedon Mar 24, 2014
mDNS / dns-sd is sweet and extremely transparent in that it delivers knowledge on its services and optionally hints on how to use them.
but it only works locally. you still need a standards solution globally.
sloev commentedon Mar 24, 2014
by reading:
https://github.com/calmh/syncthing/wiki/Case-Study
i got a better understanding of the global lookup in this case using your announce server. is the announce server sourcecode available?
filoozom commentedon Mar 24, 2014
It is: https://github.com/calmh/syncthing/blob/master/discover/cmd/discosrv/main.go
60 remaining items
calmh commentedon Dec 26, 2021
I don't think any of the usual suspects are in any way interested in doing this, and be assured that doing it properly is a major piece of work. So I don't think there's anything to revisit, really.
zjDrummond commentedon Dec 27, 2021
calmh commentedon Dec 27, 2021
If it didn't fit our goals the issue would be rejected. Still needs someone willing and able to do it.
DivineDominion commentedon Sep 13, 2022
@calmh Could you document how to compile into a C library? I'm a capable enough Swift developer to add the module map myself and export this as a proper Swift package, but I'm no good at understanding the build system of Go :)
calmh commentedon Sep 13, 2022
It's been many years, I don't remember. I'm sure the info is out there, though.
fuzihaofzh commentedon Sep 28, 2022
It's 2022 now. Seems it still not not come out. I just wonder resilio also has a ios version. Is there any particular reason that syncthing still not support ios?
bezmi commentedon Sep 28, 2022
I think it's pretty clear why. People are expecting an iOS port to materialise out of thin air. It's an immense amount of work and no one is willing to volunteer the time needed to do it.
OliverCole commentedon Sep 28, 2022
The $515 bounty obviously isn't sufficient. Perhaps the issue needs to be broken down into smaller pieces people might be more able to help fund in the near term?
pySec710 commentedon Oct 1, 2022
What about creating a mobile web client and then making it an iOS app by embedding it in a frame? It wouldn’t interact with your file system obviously so no syncing but it would allow you to view the file system, down files, and maybe even add a built in file viewer like google drive. That way you get some interaction with syncthing and could be a good start to a full iOS client. It would also give users the option of a google drive style way to access their files without needing a client app installed.
ivankovnatsky commentedon Oct 3, 2022
I think this is what: https://github.com/MobiusSync/MobiusSync closely to what you suggest does, I guess.
imsodin commentedon Oct 3, 2022
I locked the issue as the intent here is clear. More comments that it's needed or how it might be done don't help. Someone "just" needs to do work. For any discussions or even better, if you'd like to work on it, reach out on https://forum.syncthing.net.
calmh commentedon May 30, 2025
This now exists in the form of Synctrain 🎉