This will cause gityll to search in the wrong directory for html files.

Post, Contents, HTML generation logic, templating should all be split into seperate files.

Split express into a separate file.

Travlr

Elevator

Live. Local. Global.
Tailored travel for everyone.

Feature overview

Day trip suggestions

'Hot spots' with group travlr discounts

'Travlr codes' - same idea as snapcodes

'travlr discount codes' - companies can display their travlr business code to give travlr discounts

'surge pricing' - companies offer reduced prices when there are lots of travlrs in the same area

machine learning to learn the kinds of places and trips you enjoy most

tag locations that you find interesting, give brief descriptions to...

earn 'travlr points', redeemable against trips

record travlrs gps location to geneerate new suggested day trip routes

use gps location to find travlr hotspots, suggesting interesting places

'detours' - suggestions during your adventure

Flow

First run

Select 5 places you love the look of

Add your 'travlr' friends by phone number

'Choose your adventure' - choice between 5 day trips.

'detours' - why not try a river sightseeing tour.

travel plan day out, ml, like google maps routes
tap and tag event

when you leave an event or cool place, route out of 5 stars, then use ml to suggest things to do
clustering for travellers locations, ml to discover cool places

geolytics

local knowledge tips and tricks

record someones entire day of travelling, use this to suggest routes

traffic data

travlr code like a snapcode

companies can sponsor / subsidise routes

'hot locations' companies offer discounts to people using the app

take a picture of our travlr code, to get a permanent 5% discount

travlrs get a free dessert with a meal

recording gps location

interactive travel guide

crowdsourced interactive travel guide

travlr meetups (like pokemon go gyms)
create a meetup
travlr group discounts

move. live. play.

live. move. play.

this is living.vibrant.

see the world through everyones eyes.

suggest a trip based on my history.

suggest a random trip.

suggest a trip I might not like.

groupon, tripadvisor, tinder social,

earn travlr points, redeem for discounts / days out.

live. local. global.

have a drink on us.

learn what kind of places you like, find people like you.

user preferences -> tailored travel

suggested meetups.

Join the hangover club?

Company can make a 'deal', 'hangover club' with a short elevator desc, then a

Hey get off your phone, your already here.

There's a surge or travlrs in your area, 10% discount off all events.

travlures?

Seriously running rm -f *.html is getting boring.

Write an express backend to serve blog posts and to automatically recompile these posts when a new issue is posted.

i.e. remove the '.html' extension, potentially support for custom shortlinks

Intro

The Cisco University Challenge is an amalgamation of a hackathon and a businessathon(?). Take Computer Science and Business students, place them in a room with UK business leaders and a worrying amount of caffeing, see what happens.

The Brief

Starting the competition, we were presented with a series of four briefs, our team choosing Barclays' brief of "Controlling access to a users private data in the internet of things".

The Idea

Borrowing from the Bitcoin architecture we formed 'PermissionCloud', a user centric IOT permissions management system. The premise is based around the following key components:

Device Administrators

These are the manufacturers and developers of the IOT device in question, for example: Nest and their 'smart' thermostat system.

Data Providers

This is a source of a users personal data, for example: Android or IOS could provide a users GPS location.

Permission Cloud

This is a de-centralised server that stores tokens for specific endpoints provided by the device administrators and data providers.

BlockChain

This is a distributed backup of the state of the Permission Cloud at specific times. This means if anyone was to somehow gain unauthorised access to the Permission Cloud and change any users settings, this could be detected due to a discontinuity between the permissions and those stored in the BlockChain.

User

This is the person actually using the system, be it through a mobile application, web app or any other implementation. Users have the ability to create new rules, think IFTTT, and at any time can invalidate the tokens used by these rules, hence revoking access to their data.

What makes Permission Cloud special?

We are essentially making all IOT devices slaves to their respective owners and device administrators. Far removed from the idea of a smart fridge botnet, devices using our system could not actually access any data directly. This would actually be acheived by the device administrators requesting permission from the user, the user granting permission and authenticating with the device administrator and data provider, OAuth tokens from both providers being stored in a 'rule entry' in the Permission Cloud and then the device administrator being able to request data directly from the data provider using their OAuth token.

In summary, IOT devices need not apply (for a users data) and are in the hands of the user rather than the other way around.

{{post-published-time}}
{{post-modified-time}}
{{author-profile-icon}}
{{author-profile-link}}
{{post-tags}}
{{similar-posts}}
{{post-github-link}}

Creating the webhook:

POST /repos/:owner/:repo/hooks

{
  "name": "web",
  "active": false,
  "events": [
    "issues"
  ],
  "config": {
    "url": server_address,
    "content_type": "json"
  }
}