DistOS 2014W Lecture 6 - Revision history

Josh brach: Fleshed out point form lists into paragraph form discussions. Warning: Some paraphrasing was required! Original authors may wish to verify the integrity of their ideas! Added Reference section to get rid of cite error, but it isn't proper.

2014-04-24T17:43:42Z

Fleshed out point form lists into paragraph form discussions. Warning: Some paraphrasing was required! Original authors may wish to verify the integrity of their ideas! Added Reference section to get rid of cite error, but it isn't proper.

Show changes

Eapache at 17:23, 23 April 2014

2014-04-23T17:23:42Z

← Older revision		Revision as of 17:23, 23 April 2014
Line 71:		Line 71:
	== Group design exercise — The web that could be ==		== Group design exercise — The web that could be ==

	* “The web ~~that wasn't” mentioned~~ the ~~moans~~ of librarians.		The web as it currently stands (and to the distress of librarians everywhere) is a vast soup of unstructured information. Many ideas for "the web that could be" focus on a web for structured information, but this hits several difficulties:
	* A universal classification system ~~is needed~~.
			* Nobody has ever been able to agree on a universal classification system for all potential information.
	* The training overhead of classifiers (e.g., librarians) is high. See the master's that a librarian would need.		* The training overhead of classifiers (e.g., librarians) is high. See the master's that a librarian would need.
	* More structured content, both classification, and ~~organization~~
	* Current indexing by crude brute-force ~~searching for words~~, ~~etc.~~, ~~rather than searching metadata~~		Our current solution is a combination of various technologies including search engines and brute-force indexing, natural language processing, and tagging via the "semantic web". Unfortunately this system has its own problems:
	* Information doesn't have the ~~same persistence, see bitrot and Vint Cerf's talk~~.
	* Too concerned with presentation now.		* The semantic web has effectively died because nobody bothered tagging anything.
	* ~~Tim Berner-Lees bemoaning the death of the~~ semantic web.
	* The problem of information duplication when information gets redistributed across the web. However, we do want redundancy.		* The problem of information duplication when information gets redistributed across the web. However, we do want redundancy.
	* Too much developed by software developers		* Too much developed by software developers
Line 87:		Line 87:
	** See Reddit		** See Reddit
	* How do you programmatically distinguish satire from fact		* How do you programmatically distinguish satire from fact

			Other problems discussed include:

			* Information doesn't have the same persistence, see bitrot and Vint Cerf's talk.
			* Too concerned with presentation now.
	* The web's structure is also “shaped by inbound links but would be nice a bit more”		* The web's structure is also “shaped by inbound links but would be nice a bit more”
	* Infrastructure doesn't need to change per se.		* Infrastructure doesn't need to change per se.

36chambers: /* Class discussion */

2014-04-21T10:04:03Z

Class discussion

← Older revision		Revision as of 10:04, 21 April 2014
Line 119:		Line 119:
	* There is a semantic gap between how we express and query information, and how AI understands it.		* There is a semantic gap between how we express and query information, and how AI understands it.
	* Can think of Facebook as a distributed human search infrastructure.		* Can think of Facebook as a distributed human search infrastructure.
	* A core service of an operating system is ~~locating~~ information. '''Search is infrastructure.'''		* The core service/function of an operating system is to locate information. '''Search is infrastructure.'''
	* The problem is not purely technical. There are political and social aspects.		* The problem is not purely technical. There are political and social aspects.
	** Searching for a file on a local filesystem should have a unambiguous answer.		** Searching for a file on a local filesystem should have a unambiguous answer.

36chambers: /* Group 3 */

2014-04-21T10:02:44Z

Group 3

← Older revision		Revision as of 10:02, 21 April 2014
Line 57:		Line 57:
	** More availability for user - what happens when system fails?		** More availability for user - what happens when system fails?
	** Key management to be considered - Is it good to have centralized or distributed mechanism?		** Key management to be considered - Is it good to have centralized or distributed mechanism?
	** Make information centric as opposed to host centric.		** Make information centric as opposed to host centric

	=== Group 4 ===		=== Group 4 ===

36chambers: /* Group 3 */

2014-04-21T10:02:32Z

Group 3

← Older revision		Revision as of 10:02, 21 April 2014
Line 54:		Line 54:
	* Proposal		* Proposal
	** Peer-peer to distributed mechanisms for documenting		** Peer-peer to distributed mechanisms for documenting
	** Reverse links with caching - distributed cache		** Reverse links with caching (distributed cache) that doesn't compromise anything
	** More availability for user - what happens when system fails?		** More availability for user - what happens when system fails?
	** Key management to be considered - Is it good to have centralized or distributed mechanism?		** Key management to be considered - Is it good to have centralized or distributed mechanism?
			** Make information centric as opposed to host centric.

	=== Group 4 ===		=== Group 4 ===

36chambers: /* Class discussion */

2014-04-21T09:58:31Z

Class discussion

← Older revision		Revision as of 09:58, 21 April 2014
Line 111:		Line 111:
	* The document was TBL's idea of the atom of content, whereas nowaday we really need something more granular.		* The document was TBL's idea of the atom of content, whereas nowaday we really need something more granular.
	* We want to extract higher-level semantics.		* We want to extract higher-level semantics.
	* Google may not be pure keyword search anymore. It is essentially AI ~~now~~, but we still struggle with expressing what we want to Google.		* Google may not be pure keyword search anymore. It essentially now uses AI to determine relevancy, but we still struggle with expressing what we want to Google.
	* What about the adversarial aspect of content hosters, vying for attention?		* What about the adversarial aspect of content hosters, vying for attention?
	* People do actively try to fool you.		* People do actively try to fool you.

Matthewguzzo: /* Valuation and deduplication of information */

2014-02-26T22:15:45Z

Valuation and deduplication of information

← Older revision		Revision as of 22:15, 26 February 2014
Line 36:		Line 36:

	==== Valuation and deduplication of information ====		==== Valuation and deduplication of information ====
	Another problem common with the current ~~wwww~~ is the duplication of information. Redundancy is not in itself harmful to increase the availability of information, but is ad-hoc duplication of the information itself?		Another problem common with the current web is the duplication of information. Redundancy is not in itself harmful to increase the availability of information, but is ad-hoc duplication of the information itself?

	One then comes to the problem of assigning a value to the information found therein. How does one rate information, and according to what criteria? How does one authenticate the information? Often, popularity is used as an indicator of veracity, almost in a sophistic manner. See excessive reliance on Google page ranking or Reddit score for various types of information consumption for research or news consumption respectively.		One then comes to the problem of assigning a value to the information found therein. How does one rate information, and according to what criteria? How does one authenticate the information? Often, popularity is used as an indicator of veracity, almost in a sophistic manner. See excessive reliance on Google page ranking or Reddit score for various types of information consumption for research or news consumption respectively.

Matthewguzzo: /* On the current infrastructure */

2014-02-26T22:10:06Z

On the current infrastructure

← Older revision		Revision as of 22:10, 26 February 2014
Line 41:		Line 41:

	=== On the current infrastructure ===		=== On the current infrastructure ===
	The current <em>internet</em> infrastructure should remain as is, at least in countries with not just a modicum of freedom of access to information. Centralization of of control of access to information is a terrible power. See China and parts of the Middle-East. On that note, what can be said of popular sites, such as Google or Wikipedia that serve as the main entry point for many access patterns?		The current <em>internet</em> infrastructure should remain as is, at least in countries with not just a modicum of freedom of access to information. Centralization of control of access to information is a terrible power. See China and parts of the Middle-East. On that note, what can be said of popular sites, such as Google or Wikipedia that serve as the main entry point for many access patterns?

	The problem, if any, in the current web infrastructure is of the web itself, not the internet.		The problem, if any, in the current web infrastructure is of the web itself, not the internet.

Cdelahou: /* The Early Web (Jan. 23) */

2014-02-21T21:52:15Z

The Early Web (Jan. 23)

← Older revision		Revision as of 21:52, 21 February 2014
Line 2:		Line 2:


	===The Early Web (Jan. 23)===		==The Early Web (Jan. 23)==

	* [https://archive.org/details/02Kahle000673 Berners-Lee et al., "World-Wide Web: The Information Universe" (1992)], pp. 52-58		* [https://archive.org/details/02Kahle000673 Berners-Lee et al., "World-Wide Web: The Information Universe" (1992)], pp. 52-58

Cdelahou: Replaced previous change. added link to paper and title.

2014-02-21T21:51:51Z

Replaced previous change. added link to paper and title.

← Older revision		Revision as of 21:51, 21 February 2014
Line 1:		Line 1:
	'''the point form notes for this lecture could be turned into full sentences/paragraphs'''		'''the point form notes for this lecture could be turned into full sentences/paragraphs'''

	~~==UNIX and Plan 9 (Jan. 28)==~~

	* [http://homeostasis.scs.carleton.ca/~soma/distos/fall2008/unix.pdf Dennis M. Ritchie and Ken Thompson, "The ~~UNIX Time-Sharing System"~~ (~~1974~~)]		===The Early Web (Jan. 23)===
	* [~~http~~://~~homeostasis.scs~~.~~carleton.ca/~soma/distos~~/~~2014w~~/~~presotto~~-~~plan9.pdf Presotto~~ et. al, ~~Plan 9, A Distributed System~~ (~~1991~~)]
	* [http://~~homeostasis.scs~~.~~carleton~~.~~ca/~soma/distos~~/~~2014w/pike-plan9.pdf Pike et al.~~, ~~Plan 9 from Bell Labs~~ (~~1995~~)]		* [https://archive.org/details/02Kahle000673 Berners-Lee et al., "World-Wide Web: The Information Universe" (1992)], pp. 52-58
			* [http://www.youtube.com/watch?v=72nfrhXroo8 Alex Wright, "The Web That Wasn't" (2007)], Google Tech Talk

	== Group Discussion on "The Early Web" ==		== Group Discussion on "The Early Web" ==