Well I will use solely DO. IMMessage objects are sent and routed among clients and the server. Everything else is going to be implemented using loadable modules (NSBundle's that is dynamically loaded).
在 2013-2-28，下午9:27，Bluna Ratimonkey <[email protected]> 写道： > I'd call it iMaxChat for now. Doesn't Etoile already have its own goal for IM > implementation? Would be confusing if you took such name? You should try to > use existing components like taking advantage of LK or CoreObject etc, and > make it fit with the project philosophy, a component based system rather > trying to think of one big application. > > > On Thu, Feb 28, 2013 at 8:18 PM, Maxthon Chan <[email protected]> wrote: > Is it actually allowed that I used the name ÉtoiléMessage as the "trademark > name" for IMClone? You know that if this is allowed, I will as well use the > logo of Étoilé project on this app, and it will go to App Store for iOS. And > what about licensing? I need a license that is both open-sourced and > compatible to Apple's App Store rules. Will BSDL+MIT License dual licensing > work? > > 在 2013-2-28，下午8:38，Luis Garcia Alanis <[email protected]> 写道： > >> IRC is needed to build a community... in my opinion... later it can be >> changed when IMClone is done. >> >> >> On Thu, Feb 28, 2013 at 3:20 AM, Maxthon Chan <[email protected]> wrote: >> If you want to help, the thing is here: http://github.com/xcvista/IMClone >> >> 在 2013-2-28，下午5:46，Maxthon Chan <[email protected]> 写道： >> >>> I am now implementing it using DO over SSL with application-layer hardening >>> (Message signature in Apple fashion). >>> >>> 在 2013-2-28，下午5:43，Slex Sangiuliano <[email protected]> 写道： >>> >>>> >>>> >>>> > From: [email protected] >>>> > Date: Wed, 27 Feb 2013 15:23:20 +0000 >>>> > To: [email protected] >>>> > Subject: Re: [Etoile-discuss] Maybee switch to IRC? >>>> > >>>> > On 27 Feb 2013, at 15:14, Maxthon Chan <[email protected]> wrote: >>>> > >>>> > > Security. This firewalled gmcd will only push notifications to the >>>> > > clients that connected to it. All requests have to go through HTTP >>>> > > interface built on ohttpd and bundles, and routed to the firewalled >>>> > > gmcd. >>>> > >>>> > I meant the high-level problem. The problem we have is that SILC has >>>> > poor client support, which is discouraging people from using it. You >>>> > proposing that we address this problem by switching to a protocol that >>>> > has NO client support. >>>> > >>>> > I don't know where to begin with your 'security' comments, other than to >>>> > suggest that you find a book that gives a beginners' guide to computer >>>> > security. >>>> > >>>> > David >>>> > >>>> > -- Sent from my brain >>>> >>>> >>>> If can be usefull, this is the one I used at University for the security >>>> exam. I think it is a good starting point. It also talks of "Network >>>> security" and "Trusted Operating System Design". >>>> _______________________________________________ >>>> Etoile-discuss mailing list >>>> [email protected] >>>> https://mail.gna.org/listinfo/etoile-discuss >>> >>> _______________________________________________ >>> Etoile-discuss mailing list >>> [email protected] >>> https://mail.gna.org/listinfo/etoile-discuss >> >> >> _______________________________________________ >> Etoile-discuss mailing list >> [email protected] >> https://mail.gna.org/listinfo/etoile-discuss >> >> >> _______________________________________________ >> Etoile-discuss mailing list >> [email protected] >> https://mail.gna.org/listinfo/etoile-discuss > > > _______________________________________________ > Etoile-discuss mailing list > [email protected] > https://mail.gna.org/listinfo/etoile-discuss > > > > > -- > I used to be a GNUstep developer like them, then I took an arrow in the > knee... > _______________________________________________ > Etoile-discuss mailing list > [email protected] > https://mail.gna.org/listinfo/etoile-discuss
_______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
