Make a route to share based on a configuration file

[gabrielstuff]

Sharing should be easy as using one route.
Based on the configuration the route will handle the automatic sharing principle

[4quet]

Performing a POST request on the share route should call all concerned routes.
Example:

POST /api/v1/actions/share
{
  "twitter": { "message": "hello world !" },
  "mandrill": { "email": "my@email.com" }
}

The request above will perform:

POST /api/v1/actions/twitter
{
  "message": "hello world!"
}

and

POST /api/v1/actions/mandrill
{
  "email": "my@email.com"
}

[4quet]

Different proposition: the share route will receive an object with all kind of data:

{
  "media": "/path/to/media",
  "filename": "media.jpg",
  "thumbnail": "/path/to/thumbnail",
  "email": {
    "from": "my@email.com",
    "to": "your@email.com"
  },
  "meta": "..."
}

Then each action is configured to pick whatever it needs inside this object to share content.
Example (in settings.json):

"twitter": {
  "mediaKey": "media",
  "filenameKey": "filename"
}

[4quet]

Different proposition: All actions use the same standard set of data and use only what they need.
The share route will only dispatch this set of data among all different actions.
Example: all actions should be able to handle this object:

{
    "media": {
        "name": "...",
        "content": "..."
    },
    "thumbnail": {
        "name": "",
        "content": ""
    },
    "email": {
        "from": "",
        "to": "",
        "firstname": "",
        "lastname": "",
        "subject": "",
        "text": "",
        "html": "",
        "template": "",
        "attachments": [{
            "name": "",
            "content": ""
        }],
        "vars": ""
    },
    "title": "",
    "description": "",
    "message": "...",
    "source": "",
    "destination": "",
    "user": "",
    "password": "",
    "hostname": "",
    "target": "",
    "privacyStatus": "",
    "uploadDirectoryPath": "",
    "uploadDirectoryID": "",
    "printer": "",
    "format": "",
    "copies": "",
    "options": "",
    "bucket": "",
    "token": ""
}

[4quet]

Final JSON:

  {
    "path": "path to a file / url",
    "file": "myFile.jpg",
    "type": "image/jpg",
    "details": {
      "width": 1024,
      "height": 1024,
      "thumbnail": {
        "file": "myThumb.jpg",
        "width": 128,
        "height": 128,
        "type": "image/jpg",
        "source": "path to a file / url"
      }
    },
    "meta": {
        "email": {
            "from": "",
            "to": "",
            "firstname": "",
            "lastname": "",
            "subject": "",
            "text": "",
            "html": "",
            "template": "",
            "attachments": [{
                "name": "",
                "content": ""
            }],
            "vars": ""
        },
        "title": "",
        "description": "",
        "message": "...",
        "source": "",
        "destination": "",
        "user": "",
        "password": "",
        "hostname": "",
        "target": "",
        "privacyStatus": "",
        "uploadDirectoryPath": "",
        "uploadDirectoryID": "",
        "printer": "",
        "format": "",
        "copies": "",
        "options": "",
        "bucket": "",
        "token": ""
    }
  }

The meta field can adapt according to the called actions.

[gabrielstuff]

In the V2 of altruist, this option seems mandatory. Recently I've been posting using : base64 and formData for sharing on:

• mandrill
• print
• socialite

It is completely useless to repost the Data. This should be optional and not mandatory. It also appears to be a great option to be able to post a link to the media (image, video or sound) that we want to share.