Twilio Chat is one of the latest products from twilio. And would be a great addition to this repo.
https://www.twilio.com/chat

We use it extensively in my company. Though the legacy systems still run on python for it, we're planning a migration to NodeJS in some time.

I'd be happy to contribute to this repo. Though I feel the current dependencies are quite outdated, and I will have to use the latest twilio-node client for it. Issue is I don't have any experience of working with SMS or calls on twilio, so maybe someone else will have to do the migration for them as I upgrade to the latest client for twilio chat.

There are few other things in my mind to discuss.

@daffl @ekryski Let me know if there is any interest for this.

Add documentation or just write how to create Service of twillio to send SMS .

This service is using an outdated version of the Twilio API library. I've looked a little bit into the new API, but I'm really not sure how to update this service to be compatible with the Feathers Common API, so I'm collecting some perhaps useful information here in hopes someone else might take a look.

Twilio API docs

• New Twilio API
• Old API vs New API

Twilio Paging Information docs

• Link to "Paging Information"

Twilio messages stream docs

• Link to "Read: List messages matching filter criteria"

Twilio's API library repository docs showing how to use this.list:

• List messages using callbacks or promises

this.list uses this.each internally:

• this.list source code
• this.each source code

Pseudo code for sms.js

Here I'm trying to handle pagination based off the mongoose service and what Twilio supports:

• Mongoose service code
• Twilio messaging service code

class Service {
  constructor (options = {}) {
    if (!options.accountSid) {
      throw new Error('Twilio `accountSid` needs to be provided');
    }

    if (!options.authToken) {
      throw new Error('Twilio `authToken` needs to be provided');
    }

    this.from = options.from || null;
    this.paginate = options.paginate || {};
    
    const twilio = new Twilio(options.accountSid, options.authToken);
    this.client = twilio.messages;
  }

  find (params) {
    const paginate = (params && typeof params.paginate !== 'undefined') ? params.paginate : this.paginate;
    const result = this._find(params, !!paginate.default,
      query => filterQuery(query, paginate)
    );

    return result;
  }

  _find (params, count, getFilter = filterQuery) {
    const { filters, query } = getFilter(params.query || {});

    let opts = {};

    if (count) {
      // Handle $limit
      if (typeof filters.$limit !== 'undefined') {
        opts = {
          limit: filters.$limit,
          pageSize: this.paginate.max
        }; 
      } else {
        opts = {
          limit: this.paginate.default,
          pageSize: this.paginate.max
        };
      }
    }

    return new Promise((resolve, reject) => {
      return this.client.list(opts).then(resolve).catch(reject);
    });
  }

// Note: I'm really not sure about this code or how to connect Twilio to Feathers.

Feathers pagination:

I'm not sure to what extent this idea of pagination can be supported?

• Feathers pagination docs
• Feathers querying docs

Seeing as the new Twilio API is "streaming" I don't know how that changes things.

statusCallback

Users might want to be able to pass extra options like a statusCallback URL:

• Monitor the status of your message

EDIT:

• https://www.twilio.com/engineering/2015/04/16/replacing-absolute-paging-with-relative-paging

The devDependency @feathersjs/express was updated from 4.3.10 to 4.3.11.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@feathersjs/express is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @feathersjs/feathers was updated from 4.3.10 to 4.3.11.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@feathersjs/feathers is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency @feathersjs/errors was updated from 4.3.10 to 4.3.11.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@feathersjs/errors is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

The devDependency @feathersjs/socketio was updated from 4.3.10 to 4.3.11.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@feathersjs/socketio is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴