Hi Amr! The twister-core has been ported to iOS already, as you may see in this changelog here (merged):
https://github.com/miguelfreitas/twister-core/pull/339/files There you may also find complete build instructions. I'm not aware of any iOS client frontend, so please yes: feel free to start a new repo! regards, Miguel On Fri, Jan 19, 2018 at 5:16 PM, Amr <[email protected]> wrote: > Hi > I am an iOS developer and would like to help building the iOS client for > Twister. Did anybody already started that effort, or should I start a new > repo in github? > > > On Monday, August 8, 2016 at 4:16:48 PM UTC-7, 1776 wrote: >> >> Following up on this, the Android and iOS clients are critical. Native >> gui, packaged up, open-sourced. Easy for non-techies to install and use. >> What do you all think about crowd funding development of a lightweight >> client for iOS and Android? I would gladly contribute to that, I suspect >> others would to. Raising thousands of dollars/euros wouldn't be >> difficult. What about BountySource? (vs GoFundMe or one of the others). >> >> Thanks! >> >> >> On Monday, November 16, 2015 at 7:57:57 AM UTC-5, Miguel Freitas wrote: >>> >>> Hi Erkan, >>> >>> On Sat, Nov 14, 2015 at 3:00 PM, Erkan Yilmaz <[email protected]> wrote: >>> >>>> Happy birthday! >>>> >>>> RT @myleneb To celebrate 2 years of #twister @mfreitas will you take a >>>> little time to tell us how you consider Twister's future ? >>>> RT @kseistrup the zeroth block was mined 2013-11-14T01:57:35Z >>>> >>> >>> I believe most important landmarks for twister's roadmap have already >>> been put... >>> >>> I mean, to start, we obviously need to increase userbase. That won't >>> happen if we stay mostly linux-based. >>> >>> *A good windows installer, that also manages running twister as a >>> service when computer boots, is a first and easy candidate.* >>> >>> *Then, a mobile client. We already cross-compile twisterd for android >>> and ios, but packing it nicely with a good (native) UI is still missing.* >>> >>> The last nice client to foster usage would be the web-only client. We >>> have already most of support implemented in twisterd (commands exposing raw >>> data without crypto/authentication), a nodejs proxy prototype (to handle >>> limiting traffic for some commands etc) and working javascript crypto. >>> Still to decide: policy to allow torrent joining requests (to prevent >>> server DoS) and packing client as a browser extension (to ensure code >>> authenticity). >>> >>> Ideas on improving user registration in general (fighting massive >>> registrations) are important as well, but i don't currently see these as >>> the most impeding factor. >>> >>> These as just a few thoughts anyway, of course i might be overlooking a >>> lot of cool ideas! >>> >>> regards, >>> >>> Miguel >>> >>> -- > You received this message because you are subscribed to the Google Groups > "twister-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "twister-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
