- From: Steven Roose <stevenroose@gmail.com>
- Date: Thu, 28 Jan 2016 14:48:28 +0100
- To: Adrian Hope-Bailie <adrian@hopebailie.com>
- Cc: Rafael Pereira <rafael@rippex.net>, Melvin Carvalho <melvincarvalho@gmail.com>, Stefan Thomas <stefan@ripple.com>, Evan Schwartz <evan@ripple.com>, Interledger Community Group <public-interledger@w3.org>
- Message-ID: <CAChG=YV-GOKTeamMvBTew_fhQQWdH0d3wjRhwYHcdo6AdZD3+g@mail.gmail.com>
I'm not a really big fan of Slack. I'd rather promote the IRC channel over at W3C. On Thu, Jan 28, 2016 at 12:36 PM, Adrian Hope-Bailie <adrian@hopebailie.com> wrote: > Thanks for the input Rafael and Xavier. > > I have already created the team interledger.slack.com so I thought we > should kick the tyres for a bit since this is the system that was suggested > on our last call. > > This sounds like something we should discuss next week > > On 28 January 2016 at 13:32, Rafael Pereira <rafael@rippex.net> wrote: > >> Adrian, I would be careful with slack, unless you will use the paid >> version (8+ USD/user) there is a limitation on accessing the group's >> message history (10,000 messages). Even if this project is eligible for >> a special condition >> <https://get.slack.help/hc/en-us/articles/204368833-Slack-for-Nonprofits>, >> I wouldn't go this way. If I would use a IM app, I would choose Fleep >> <https://fleep.io/pricing> over Slack because it has no limitations on >> history access and search, has integrations >> <https://fleep.io/blog/integrations/>, and is compatible >> <https://fleep.io/features> with email. I'm much more comfortable with >> that as my IM in general. >> The other possible option is a forum (hosted, or a google forum), IMO, >> the best way to keep discussions organized. >> >> Em qui, 28 de jan de 2016 às 07:52, Adrian Hope-Bailie < >> adrian@hopebailie.com> escreveu: >> >>> Have setup slack and will send out invites to the group. >>> >>> It has some great integrations so we can link to IRC for W3C archive >>> purposes and to Git. >>> >>> Happy to try gitter but Slack was pitched on the call so going with that >>> for now. >>> >>> On 28 January 2016 at 11:49, Melvin Carvalho <melvincarvalho@gmail.com> >>> wrote: >>> >>>> >>>> >>>> On 28 January 2016 at 10:35, Adrian Hope-Bailie <adrian@hopebailie.com> >>>> wrote: >>>> >>>>> We're using #interledger on the W3C IRC but it's not widely used. >>>>> In the last call we discussed setting up Slack which I am >>>>> investigating. >>>>> >>>> >>>> Thanks! I'll join. >>>> >>>> Have used slack a bit in the past. >>>> >>>> We've had good experiences with gitter. >>>> >>>> If you want to host your own, perhaps rocket.chat >>>> >>>> >>>>> >>>>> On 28 January 2016 at 10:46, Melvin Carvalho <melvincarvalho@gmail.com >>>>> > wrote: >>>>> >>>>>> >>>>>> >>>>>> On 27 January 2016 at 17:40, Stefan Thomas <stefan@ripple.com> wrote: >>>>>> >>>>>>> Very strange, the "Use of const in strict mode" error is exactly the >>>>>>> one you get when trying to run it with an older node version like 0..10.x. >>>>>>> But the log clearly shows you're using 5.5.0. >>>>>>> >>>>>>> The second error I believe is an issue with NPM. There is a >>>>>>> "--color" command line parameter that is being passed and somehow NPM has >>>>>>> decided to search for a module called "--color". >>>>>>> >>>>>>> I would make sure that you don't have any old versions of Node or >>>>>>> NPM installed somewhere. Especially check the ones in your path (run "node >>>>>>> -v" and "npm -v".) >>>>>>> >>>>>>> I've also created a possible fix: >>>>>>> https://github.com/interledger/five-bells-demo/pull/24 - This >>>>>>> forces all parts of the demo to use the same Node/NPM. I'll get it >>>>>>> reviewed/merged ASAP. >>>>>>> >>>>>> >>>>>> Thank you! >>>>>> >>>>>> It's working now ... >>>>>> >>>>>> Very cool visualization ... I'll be experimenting with this over the >>>>>> next days. >>>>>> >>>>>> Sorry if this has come up before: is there a canonical chat area for >>>>>> this project? >>>>>> >>>>>> >>>>>>> >>>>>>> On Wed, Jan 27, 2016 at 6:37 AM, Melvin Carvalho < >>>>>>> melvincarvalho@gmail.com> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 2 November 2015 at 17:47, Evan Schwartz <evan@ripple.com> wrote: >>>>>>>> >>>>>>>>> We've released our reference implementation of the Interledger >>>>>>>>> Protocol. Try out the demo at >>>>>>>>> https://github.com/interledger/five-bells-demo >>>>>>>>> >>>>>>>>> × >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> This is a basic implementation of the Universal mode of the >>>>>>>>> protocol. The demo runs a number of independent ledgers and connectors and >>>>>>>>> allows you to select any two ledgers and send an interledger payment >>>>>>>>> between them. This is meant to illustrate how easy it could (and arguably >>>>>>>>> should) be to send money between payment networks. >>>>>>>>> >>>>>>>>> More documentation, draft specs, and other use case demos to come >>>>>>>>> but we're looking forward to hearing your feedback on this in the meantime! >>>>>>>>> >>>>>>>> >>>>>>>> Having issues getting this running. >>>>>>>> >>>>>>>> npm start >>>>>>>> >>>>>>>> const demo = require('./src/services/demo') >>>>>>>> ^^^^^ >>>>>>>> >>>>>>>> I guess that's an npm thing, so i downloaded npm 5.5 >>>>>>>> >>>>>>>> But same issue. >>>>>>>> >>>>>>>> SyntaxError: Use of const in strict mode. >>>>>>>> at Module._compile (module.js:439:25) >>>>>>>> at Object.Module._extensions..js (module.js:474:10) >>>>>>>> at Module.load (module.js:356:32) >>>>>>>> at Function.Module._load (module.js:312:12) >>>>>>>> at Function.Module.runMain (module.js:497:10) >>>>>>>> at startup (node.js:119:16) >>>>>>>> at node.js:935:3 >>>>>>>> >>>>>>>> npm ERR! Linux 3.16.0-44-generic >>>>>>>> npm ERR! argv >>>>>>>> "/home/melvin/dev/node/node-v5.5.0-linux-x64/bin/node" >>>>>>>> "/home/melvin/dev/node/node-v5.5.0-linux-x64/bin/npm" "start" >>>>>>>> >>>>>>>> >>>>>>>> *npm ERR! node v5.5.0npm ERR! npm v3.3.12*npm ERR! code ELIFECYCLE >>>>>>>> >>>>>>>> >>>>>>>> So I tried >>>>>>>> >>>>>>>> node index.js >>>>>>>> >>>>>>>> npm ERR! Error: ENOENT, open >>>>>>>> '/home/melvin/dev/five-bells-demo/node_modules/five-bells-ledger/node_modules/--color/package.json' >>>>>>>> >>>>>>>> Sorry, Im probably making a simple mistake here. Any tips on a >>>>>>>> workaround would be great, thanks! >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Evan Schwartz | Software Architect | Ripple >>>>>>>>> [image: ripple.com] <http://ripple.com> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> -- >> >> Obrigado, >> Rafael >> >> *Rafael Olaio - CEO* >> tel +55 11 2337.2225 >> cel +55 11 99522.7572 >> rippex.net >> >> Esta mensagem pode conter informação confidencial e/ou privilegiada. Se >> você não for o destinatário ou a pessoa autorizada a receber esta mensagem, >> não poderá usar, copiar ou divulgar as informações nela contidas ou tomar >> qualquer ação baseada nessas informações. Se você recebeu esta mensagem por >> engano, por favor avise imediatamente o remetente, respondendo o e-mail >> e em seguida apague-o.This message may contain confidential and/or >> privileged information. If you are not the addressee or authorized to >> receive this for the addressee, you must not use, copy, disclose or take >> any action based on this message or any information here in. If you have >> received this message in error, please advise the sender immediately by >> reply e-mail and delete this message. >> > >
Attachments
- image/png attachment: Screen_Shot_2015-11-03_at_1.37.44_AM.png
Received on Thursday, 28 January 2016 13:53:42 UTC