Top Banner
Social networking [email protected] http://www.irccyn.ec-nantes.fr/~magnin/ http://www.twitter.com/morgan_it/ Office E214
71

Social networks: technical issues

Nov 01, 2014

Download

Education

Morgan Magnin

This material comes from the course I give to 2nd year-students at Centrale Nantes who follow the "Webstrategies and development" program. During this semester long program, students have the opportunity to develop a sound understanding of current web marketing techniques and to put these techniques into practice through real professional missions undertaken with our partners. All courses are given in English. More information on our blog: https://pedagogie.ec-nantes.fr/web-sd/

This courses aims to give an overview of technical outcomes behind social networks (syndication, semantic web, ...) and to help students get familiar with their on-line identity.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 2: Social networks: technical issues

Be aware of what goes public

Page 3: Social networks: technical issues

Be aware of what goes public

Page 4: Social networks: technical issues

Be aware of what goes public

Page 5: Social networks: technical issues

Different networks, different usages

Page 6: Social networks: technical issues

Different networks, different usages

Page 7: Social networks: technical issues

Different networks, different usages

Page 8: Social networks: technical issues

Different networks, different usages

Page 9: Social networks: technical issues

Different networks, different usages

Page 10: Social networks: technical issues

Different networks, different usages

Page 11: Social networks: technical issues

Different networks, different usages

Page 12: Social networks: technical issues

Different networks, different usages

From: http://www.fabernovel.com/news/research-paper-social-network-websites

Page 13: Social networks: technical issues

Online identity

Page 14: Social networks: technical issues

Online identity

Page 15: Social networks: technical issues

Online identity

Page 16: Social networks: technical issues

Online identity

Page 17: Social networks: technical issues

Technical issues of social Internet

Page 18: Social networks: technical issues

Web 2.0

• Web applications that facilitate interactive information sharing, interoperability, user-centered design and collaboration

• Websites mimic desktop applications: word processing, spreadsheet, slide-show presentations

• Asynchronous communications: To permit the user to continue to interact with the page, communications such as data requests going to the server are separated from data coming back to the page

Page 19: Social networks: technical issues

Web 2.0

• Takes profit from the capabilities of:

• Client- and server-side software

• Content syndication

• Use of network protocols

• Client and server side technologies: Asynchronous JavaScript and XML (Ajax)

• Server side technologie: PHP, Ruby, ColdFusion, Perl, Python, and ASP

Page 20: Social networks: technical issues

Some Web 2.0 applications

• http://www.netvibes.com

• http://www.meebo.com/

• http://docs.google.com

• http://www.zimbra.com/

• http://www.facebook.com

Page 21: Social networks: technical issues

Web 1.0 vs Web 2.0

• publishing --> participation

• directories (taxonomy) --> tagging ("folksonomy")

• personal websites --> blogging

• domain name speculation --> search engine optimization

• page views --> cost per click

• content management systems --> wikis

• Britannica Online --> Wikipedia

• Source : http://oreilly.com/web2/archive/what-is-web-20.html

Page 22: Social networks: technical issues

Web 2.0

• Pros:

• Interactive web applications

• Recommendations between users

• Collaborative spaces

• Cons:

• Is it really a technical revolution?

• Creating a Web 2.0 company just to sell it to Yahoo, Google or Microsoft?

• Accessibility

Page 23: Social networks: technical issues

Semantic web

• Evolving development of the Internet supported by W3C

• Emphasizes on the meaning (semantics) of information and services on the web is defined, making it possible for the web to "understand" and satisfy the requests of people and machines to use the web content

• Help computers categorise the content of web pages so that machines process similar to human deductive reasoning and inference

• Aim: make the information be understandable by computers, so that they can find, combine, and act upon information on the web

Page 24: Social networks: technical issues

Semantic web

• Involves publishing in languages specifically designed for data: Resource Description Framework (RDF), Web Ontology Language (OWL), and Extensible Markup Language (XML).

• Very simple examples for turning the web into semantics:

• <item>cat</item> --> <item rdf:about="http://dbpedia.org/resource/Cat">Cat</item>

• César said: <i>Alea jacta est.</i> --> <cite>César</cite> said : <q>Alea jacta est</q>

Page 25: Social networks: technical issues

Semantic web

From: http://en.wikipedia.org/wiki/Semantic_Web

Page 26: Social networks: technical issues

Syndication

Page 27: Social networks: technical issues

Syndication

Page 28: Social networks: technical issues

Syndication

Page 29: Social networks: technical issues

Syndication

Page 30: Social networks: technical issues

Syndication

Page 31: Social networks: technical issues

Syndication

• Website material is made available to multiple other sites or individual subscribers

• Benefits both the websites providing information and the websites displaying it

• Very useful for frequently updated content

• First version of RSS created by Guha at Netscape in March 1999 for use on the My.Netscape.Com portal

Page 32: Social networks: technical issues

Applications of syndication

• News websites

• Weblogs

• Podcasting

• Personal aggregators or feed readers

Page 33: Social networks: technical issues

Feed readers

• Display the contents of multiple web feeds on a single screen or series of screens

• Web-based: Google Reader, Netvibes, ...

• Desktop-based: NetNewsWire, Firefox, Mail, ..

• Mobile-device-based: Newsstand, Pro RSS, ...

• Websites aggregating content

Page 34: Social networks: technical issues

Web feeds

• Standardized XML file format

• Supported by every major web browser

• Main web syndication formats: RSS and Atom

Page 35: Social networks: technical issues

RSS

• Really Simple Syndication

• Two majors branches:

• RDF (or RSS 1.*) branch: RSS 0.90, 1.0, 1.1

• RSS 2.* branch: RSS 0.91-0.94, 2.0

Page 36: Social networks: technical issues

RSS

Page 37: Social networks: technical issues

Atom

• Developed as an alternative to RSS

• Because some people thought RSS had limitations and flaws (lack of on-going innovation, necessity to remain backward compatible)

Page 38: Social networks: technical issues

Atom

Page 39: Social networks: technical issues

Differences between RSS and Atom• RSS tags:

• title, link, date, language, creator, subject, description, content

• Atom tags:

• title, link, issued, modified, id, author, subject, summary, content

• Different paradigms regarding:

• Content model

• Date formats

• Internationalization

Page 40: Social networks: technical issues

Online identity

• Being anonymous is just an illusion

• Some issues:

• Identity exposure

• Reliability of online identities

• Reputation management

Page 41: Social networks: technical issues

OpenID

Page 42: Social networks: technical issues

OpenID

Page 43: Social networks: technical issues

OpenID

Page 44: Social networks: technical issues

OpenID

Page 45: Social networks: technical issues

OpenID

Page 46: Social networks: technical issues

OpenID

• Method of using a single login at a trusted provider to automatically allow you trusted access to other websites

• Open, decentralized standard for authenticating users

• Can be used for access control, allowing users to log on to different services with the same digital identity where these services trust the authentication body (e.g. banking or e-commerce)

• Used and provided by several large websites, e.g. Facebook, Typepad, PayPal, LiveJournal

• Developped since 2005

Page 47: Social networks: technical issues

OpenID principles• 1/ The user visits a relying party web site which displays an OpenID login

form (connected to an implementation of an OpenID client library)

• 2/ The user types his OpenID identifier into the aforementioned OpenID login form.

• 3/ The relying party then requests the identity provider to authenticate the user

• 4/ The identity provider requests the user whether he trusts the relying party web site

• 5/ After the OpenID identifier has been verified, OpenID authentication is considered successful

• 6/ The user is now considered logged in to the relying party web site.

Page 48: Social networks: technical issues

OpenID providers

• OpenID Foundation: http://openid.net/

• OpenID Europe Foundation: http://www.openideurope.eu/

• OpenID France: http://www.openidfrance.fr/

Page 49: Social networks: technical issues

XFN

• XHTML Friends Network (XFN)

• HTML microformat (i.e. approach that re-uses existing XHTML and HTML tags to convey metadata)

• Provides a way to represent human relationships using links.

• Enables web authors to indicate relationships to the people in their blogrolls by adding one or more keywords as the rel attribute to their links

<a href="http://moreaug44.free.fr/blog/" rel="colleague met">Guillaume Moreau</a>

<a href="http://jimmy.example.com/" rel="friend">Jimmy Example</a>

Page 50: Social networks: technical issues

FOAF

Page 51: Social networks: technical issues

FOAF

Page 52: Social networks: technical issues

FOAF

With FOAF, it becomes possible to answer questions like:

“Who are the people living in Nantes and aged less than 30 with their own personal website and who enjoy playing go?”

Page 53: Social networks: technical issues

FOAF

• FOAF

• Social Semantic Web application

• Machine-readable ontology describing persons, their activities and their relations to other people and objects

• Descriptive vocabulary expressed using the Resource Description Framework (RDF) and the Web Ontology Language (OWL)

• Natively supported by some web applications (e.g. LiveJournal.com and identi.ca)

Page 54: Social networks: technical issues

FOAF ressources

• FOAF Project homepage: http://rdfweb.org/foaf/

• FOAF vocabulary specification: http://xmlns.com/foaf/spec/

Page 55: Social networks: technical issues

Social aspects of Internet

Page 56: Social networks: technical issues

• New services emerge from:

• Existing information

• Data

• Services

• Information and services may be used a way that has not been targeted by the initial creators

• Facebook moved from an alumni network to an online community

• Social dimension

Page 57: Social networks: technical issues

Blogs

• Type of website, usually maintained by an individual with regular entries of commentary, descriptions of events, or other material

• 133,000,000: (June'09) number of blogs indexed by Technorati since 2002

• Classification attempts:

• Personal blogs

• Corporate and organizational blogs

• By genre (political blogs, travel blogs, dreamlogs, ...)

• By media type (vlog, linklog, sketchblog, ...)

Page 58: Social networks: technical issues

Technical tools for blogging

• Developer-hosted platforms (blog farms):

• Typepad : http://www.typepad.com/fr/

• Viabloga : http://www.viabloga.com/

• Skyrock : http://www.skyblog.com/

Page 59: Social networks: technical issues

Technical tools for blogging

• User hosted platforms:

• Wordpress : http://www.wordpress.org

• Dotclear : http://www.dotclear.net

• Movable Type : http://www.movabletype.org

• Most common technologies:

• PHP or Perl to manage dynamic pages

• MySQL or XML to manage data

Page 60: Social networks: technical issues

Twitter

• Microblogging service

• Changes blogging habits

• 9,680,000,000 tweets up to date (http://popacular.com/gigatweet/)

• RSS file for each Twitter account

• Free social networking and microblogging service,...

• But what could happen to your data (and to your URL)?

• Open-source alternative: identi.ca

Page 61: Social networks: technical issues

Wikis

• Collaborative work

• Continuous improvement of documents

• Useful for collaborative websites, personal note taking, in corporate intranets, and in knowledge management systems

• Examples:

• http://pedagogie.ec-nantes.fr

• http://romeo.rts-software.org/trac

• http://easybindings.net

Page 62: Social networks: technical issues

Social networks

• The famoux “six degrees of separation” theory

• Small world experiment by psychologist Stanley Milgram (in the U.S., 1967)

• Social structure

• Individuals (or organizations) called "nodes"

• Connections by one or more specific types of interdependency: friendship, kinship, financial exchange, dislike, sexual relationships, or relationships of beliefs, knowledge or prestige

Page 63: Social networks: technical issues

Why social networks for companies? (and people)

• Social networks are a tool to promote yourself or/and your company

• Control what is said about you implies you control what you say

• Editorial policy

• Community manager

Page 64: Social networks: technical issues
Page 65: Social networks: technical issues
Page 66: Social networks: technical issues
Page 67: Social networks: technical issues
Page 68: Social networks: technical issues

Various tools for various audiences

Page 69: Social networks: technical issues

Forthcoming features

• Growing interconnections between web services

• Social features natively integrated in new web applications

• Social search engines

• 3G Services

• Geolocation

• Management of geocoded photos by Flickr or Moblog

• Local trends in Twitter

• Use of geolocation information in Google Buzz

Page 70: Social networks: technical issues

Conclusion

Page 71: Social networks: technical issues

Think “collaborative”

• Share your information...

• But be aware of who you share with... and what you share

• Collaborative applications

• Ensure interconnection between your web applications