Imagine Transport

This transport started with the aim of being able to import anything into wiki. Now we look to be able to integrate a set of author customisable tools into the wiki experience.

We imagine the experience of clicking on the page-flag and providing the author with a set of affordances that they might like to apply to that page.

# Transporter

POST https://rest.livecode.world/imagine

This transport: - imports mediawiki wiki articles (such as wikipedia) - imports one-tab lists - imports asana tasks and projects - imports dropbox paper documents - imports images such as Goole image search results, wikipedia images, Flickr images, Pinterest pins, and web images, and media (audio and video). Drag and drop an image onto the transport.

This is an ever expanding list. Our aim is to be able to expand the range of drop-urls that this transporter can respond through the creation of an integrated set of json-rpc microservices that the author can customise.

# Use

You can drop the following types of image onto this transport: - First web image - cern.ch - Flickr image sample - flickr - Dropbox image sample - dropbox - A sample tweet - twitter

VIMEO 228098079 A quick intro to the Imagine Transport.

Strangely you can also drop a tweet here even though there are no images - the idea being that eventually you will be able to extract any picture in the tweet.

# To Do This transport is work-in-progress, we use it every day but It should be enhanced to: - [ ] Wiki Customisation - [ ] Fix geo and map importing - [ ] Flag Click

Tests

You can test this transporter with the HTML Form below:

Test: https://rest.livecode.world/imagine

url: 

You can test this out on the following: - Image discordapp.com - pinterest

# Code

The code for this transporter is written in Livecode. You can view the source here - gist

The code uses regular expressions and a case switch to route rest calls to other transporters. See Imagine Routing.

The transport should have few dependencies as using:

command fedwiki_ForwardAndReturn

delegates dependencies to the forwarded transporters.

# Not working

Some things won't work, as the web sites in question do not have the url structure needed to figure out which image is being presented on the page. It depends on how logical a url structure the sites use.

- Google Photos for instance uses obscured url's and Dropbox uses temporary links to images. With sites like Dropbox a solution would be to import the image into an open hosting media commons from where we can link to the image freely.

- Public Dropbox images - dropbox

# See also - Fedwiki Tools