nicercover v2: a serverless webapp for social networking on top of scientific portals

.

NiceCover v1 (failed)

• LOIS presentation 01

• too complicated◦ a tree/mesh of context nodes◦ unclear pull/push design

01 myself+0 "NiceCover: A Serverless Webapp for ...on Top of Scientific Portals" LOIS研 (2013)

M.Zhanikeev -- [email protected] -- NicerCover v2... Social Networking on Top of Scientific Portals -- http://bit.do/150115lois -- 2/24...

2/24

.

NiceCover v2: Still Wanted?

• SNS Today: content distribution network◦ the target is to get more people visit the product page

• NiceCover: context sharing network◦ content is converted into context (content is not essential)◦ context is shared, discussed, rated, etc.

• merit: any format/protocol can be applied to context and its handling◦ most SNSs today have a fixed framework

• example: one cannot use Twitter hashtags for scientific context/discussion02

02 myself+0 "A New Practical Design for Browsable Over-the-Network Indexing" ISEEE (2014)


3/24

.

Tradition (left) vs Nicecover (right)

Content

Context


4/24

.

Example Usecase: A Research Team

• team leader PUSHes all its context to team members

• team members TRUST all PUSHes from team leader, but also PUSHtheir own context to him/her

• team leader aggregates all PUSHes from one team members anddistributes them to others


5/24

.

Definitions


6/24

.

Serverless WebApp

.Serverless Webapp..

.... runs from a static HTML and uses cloud APIs for storage

• indexing (database) in cloud drives 02

• large-scale crowdsourcing: the Maps2Graphs project 04

• various browser-based apps like crawlers 03, etc.

02 myself+0 "A New Practical Design for Browsable Over-the-Network Indexing" ISEEE (2014)

04 myself+0 "Maps2Graphs: A Socially Scalable Method for Generating High-Quality GIS Datasets.." ITS研 (2013)

03 myself+0 "Reverse Engineering Twitter Hashtag Algorithm" NLC研 (2014)


7/24

.

Serverless WebApp: 2 Designs

• Standalone: static HTML put in a cloud drive and shared◦ JS/jQuery is inside the HTML file◦ merit: any browser, any device◦ demerit: no autoparse

• Browser Extension◦ Chrome is the easiest to write, has floating (panel), inpage (autoparse) andbackground JS scripts

◦ merits: autoparse, flexibility, ...◦ demerit: local to your Chrome browser


8/24

.

Social Networks : Push vs Pull

• PUSH: A can post in B's space (facebook)◦ participation cost: B has to accept A as a friend

• PULL: A can listen to B's broadcasts (twitter)◦ participation cost: A has to find B

• ... there are PUSH and PULL hybrids (facebook wall)


9/24

.

Useful Features

1. autoparse: parse context automatically from pages on certain portals

◦ example: Mendeley

2. autosync: sync context between A and B, automatically

3. .. both features have direct effect on participation cost


10/24

.

Private, Public, Readonly

• PRIVATE: read-write access, normally A's own context

• PUBLIC: A's space made public, can be accessed (written) by B• READONLY: A's space made public which cannot be written to or replaced

• ... plus the TRUST parameter which can create multiple modes for each of theabove


11/24

.

NiceCover: Basic Usage

• content travels as context from left to right

FIRST SECOND

Private Public Readonly

… … …

Content

Parse Store

Make public Register

Sync


12/24

.

NiceCover: More Modes

Private Public Readonly

………

ParseStore

MakepublicTrust

AutoSync

………

ParseStore

Check

ConfirmSync

• autotrust: autosyncsB's public into yourown private

• manual trust: checkand confirm

• zero trust: personaluse


13/24

.

Participation Cost


14/24

.

Participation Cost

PULL PUSH

Public (autosync )

Private

Trust

Sync

No push

Public

Sync

Trust


15/24

.

Participation Cost Optimization• action is both the qualitative and, when in |action| form, the quantitative unit

• C is unit cost of action(s), E is overall cost estimation

• C|action| is the cost of a given action times (not the power) the count

• Epull,first the total cost for a given interaction

• A = FIRST, B = SECOND

Epull,first = Cpublic (1)

Epull,second = Cprivate + C|sync−trust|sync (2)

Epush,first = Cpublic + C|sync−trust|sync (3)

Epush,second = C|nopush|nopush (4)


16/24

.

Cloud APIs


17/24

.

Cloud APIs and Automation

• Dropbox is the best Storage API◦ full automation possible -- see the process below◦ also full isolation -- permanent set of keys

• Google Drive API is more restraining, but can be worked out

• all the others are even worse than Google Drive API


18/24

.

Dropbox API Keys (1/4)

Create a Dropbox API app and get your keys. 1 private

Your own library. Only writable by your NiceCover . DO NOT share these keys!

public A copy of your information for others to get. Readable/writable both ways, by design.


19/24

.

Dropbox API Keys (2/4)

Drag -n-Drop dboxkeys.html into Firefox 2


20/24

.

Dropbox API Keys (3/4) Copy -paste your Dropbox keys , authorize, and get keys. 3


21/24

.

Dropbox API Keys (4/4) Register your full key with NiceCover Chrome Extension 4


22/24

.

DEMO...

1. Chrome Extension

2. autoparse

3. ...


23/24

.

That’s all, thank you ...


24/24

nicercover v2: a serverless webapp for social networking on top of scientific portals

Social Media

social networking

nicercover v2

nicecover v2

scientific portals lois

context content

team members team members

social networks

research team team leader