From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/notes
Date: Thursday March 1, 19101 @ 14:30
Author: fen
CVSWEB Options: -------------------
Main CVSWeb: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi
View this module: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes
-----------------------------------
Update of /usr/local/cvs/public/openprivacy/htdocs/notes
In directory giga:/home/fen/projects/openprivacy/htdocs/notes
Modified Files:
whitepaper.shtml
Log Message:
pointer to new location
*****************************************************************
File: openprivacy/htdocs/notes/whitepaper.shtml
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/whitepaper.shtml?annotate=1.46
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/whitepaper.shtml?rev=1.46&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/whitepaper.shtml.diff?r1=1.46&r2=1.45
-----------------------------------
Index: openprivacy/htdocs/notes/whitepaper.shtml
This archive was generated by hypermail 2b30
: Thu Mar 01 2001 - 14:30:53 PST
diff -u openprivacy/htdocs/notes/whitepaper.shtml:1.45 openprivacy/htdocs/notes/whitepaper.shtml:1.46
--- openprivacy/htdocs/notes/whitepaper.shtml:1.45 Wed Feb 28 19:50:34 2001
+++ openprivacy/htdocs/notes/whitepaper.shtml Thu Mar 1 14:30:51 2001
@@ -9,580 +9,16 @@
</head>
<body bgcolor="#ffffff">
- <!-- $Id: whitepaper.shtml,v 1.45 2001/03/01 03:50:34 fen Exp $ -->
+ <!-- $Id: whitepaper.shtml,v 1.46 2001/03/01 22:30:51 fen Exp $ -->
<h1>OpenPrivacy - Enhancing the Internet with Reputations</h1>
- <h2>Abstract</h2>
- <blockquote>
- <p>
- OpenPrivacy.org is building an Internet platform to take us into the
- next age - the age of personalized information. Basic to this goal
- is a platform that will provide people with complete control over
- their personal information and aid them in protecting their privacy
- while simultaneously enabling more efficient data mining by
- marketers and the access to highly desirable market segments by
- advertisers.
- </p>
- <p>
- OpenPrivacy creates a secure marketplace for anonymous demographic
- and profile information, and a distributed, attack-resistant,
- reputation-based rating system that can be used for everything from
- item selection and ordering to search result filtering. Further,
- this system is completely open, allowing multiple communication
- mechanisms, languages and ontological meanings to coexist. This
- platform thrives on diversity.
- </p>
- <p>
- To accomplish our goals, we introduce three new concepts:
- <i>Opinions</i>, <i>Bias</i> and <i>Reputations</i>. These are all
- first class, signed objects that are created at will under a
- multitude of pseudonymous entities maintained by the user. A fourth
- concept, that of a <i>personal profile</i>, is created virtually
- from a collection of the first three objects in such a way that only
- the owner of the information can validate the connections between
- them. However, if granted access, others (marketers, advertisers,
- online community builders and the like) may mine the profile for
- potentially profitable or otherwise valuable correlations while the
- owner of the profile maintains her anonymity.
- </p>
- </blockquote>
- <h2><a name="platform">The OpenPrivacy Platform</a></h2>
- <blockquote>
- <h3>Philosophy</h3>
- <p>
- While we provide a system that securely protects one's privacy, we
- are focusing our efforts on creating an <i>open</i> system. By
- "open" we mean much more than merely being Open Source with open,
- published APIs. We are creating a mechanism for communication and
- interaction that provides free and open access to all.
- </p>
- <p>
- In order to be able to freely search for and collect, read, write,
- publish and distribute information in a highly networked society
- without fear of reprisal, there must be a mechanism that can
- dissociate a user from her actions. It is our intention and firm
- belief that pseudonymous entities, combined with our concepts of
- reputation and their intrinsic value, will form the cornerstone of
- a powerful and unlimited communications mechanism that allows us to
- make better informed, useful and profitable decisions.
- </p>
- <h3>Overview</h3>
- <p>
- What you do tells a lot about who you are. For example, where you
- live, for whom you work (and how much money you make), where you
- went to school, when and what your grades were, what kind of car you
- drive, where you eat and what movies and plays you see, the
- magazines to which you subscribe and the organizations to which you
- belong, where you go on vacation and how much (and on what) you
- spend -- all of this data is collected by government agencies,
- corporations and direct marketers for the express purpose of
- providing you with enhanced services and the improved lifestyle that
- comes with them.
- </p>
- <p>
- Of course, the problem herein lies in the fact that you have little
- control over who collects this information and far less control over
- how it is used, to whom it is sold, etc. While strong laws (such as
- those that exist in the European Union) can attempt to stem the
- abuse and misuse of personal information, in actuality it comes down
- to the fact that the consumer simply has to trust those who hold the
- power to do the right thing.
- </p>
- <p>
- Systems like the Anonymizer[<a href="#anon">anon</a>] and Freedom[<a
- href="#zero">zero</a>] provide the essential anonymity needed to
- protect oneself from being watched while online, but they lack a way
- to create and profit from a long-lived pseudonymous identity. In
- today's world, people want enhanced services such as personalized
- home pages, recommended reading lists and respect within their
- communities. Many systems have been created to address these
- desires, such as my.Yahoo.com, Amazon.com's book recommendations and
- Slashdot.org, but these have problems, too. A very basic issue here
- is that a person who develops a good reputation on one site cannot
- carry that reputation with them to another. A deeper issue is that
- all of your information is known by the creators of these sites and
- can be used by them at will.
- </p>
- <p>
- OpenPrivacy provides a framework for building intercommunicating
- systems that support the concept of <i>reputation</i>. Reputations,
- which can be attached to any object such as pseudonyms, purchase
- histories, physical objects (using an expanded URI namespace),
- reputation servers, and even reputations themselves, are pervasive
- and directly affect every aspect of OpenPrivacy-enabled systems.
- One example of how this framework can be used is as a customizable
- privacy-enhanced personal portal with reputation-assisted search and
- publishing features [<a href="#jets">jets</a>]. We are also
- creating reputation calculation engines that will provide work-alike
- similarity for the communities created by the likes of Slashdot and
- Advogato. Because projects such as these are built on the
- OpenPrivacy platform, not only with their users enjoy enhanced
- privacy and security from spoof attacks, but they will also be able
- to publish selected portions of their profiles for access by the
- members of these and other communities. Likewise, advertisers can
- avail themselves of targeted, high-quality profile information with
- the full cooperation and confidence of a pseudonymous user.
- </p>
- <h3><a name="rms">Reputation Services</a></h3>
- <p>
- We introduce a set of <i>Reputation Services</i> that form the
- cornerstone of the OpenPrivacy framework. These services provide a
- standard reputation framework that can be used by any community,
- supporting an unlimited numbers of mechanisms to create, use and
- calculate results from accumulated reputation. The implementor of
- these services can nest or reuse existing reputation calculation
- engines or roll their own. They gain the ability to query remote
- RCEs, to perform ontological forwarding, and share all or part of
- their users profile database with other communities without
- violating user privacy.
- </p>
- <p>
- A reputation management system, which implements the reputation
- services, acts as a peer in a distributed network supplying the
- capability to create, store and forward opinions (either
- autonomously or under user control), manage bias structures
- (including creation and validation) and calculate reputations. More
- specifically, a reputation management system implements the
- following interfaces:
- </p>
- <blockquote>
- <h4>Nym Service</h4>
- <p>
- OpenPrivacy uses a <i>nym service</i> to to create and manage a
- set of pseudonymous virtual users - generally represented by
- public-key pairs - that inhabit OpenPrivacy space. A primary, or
- "parent" nym can be created by the nym service, and then use the
- service to beget any number of child nyms which can then
- recursively employ a nym service to beget grandchildren. This
- creates a hierarchical nym-space in which child nyms cannot be
- linked by a third party as originating from the same parent, but a
- parent can execute a validation mechanism to create an anonymous
- certificate proving that a set of child nyms were created from the
- same parent. (And of course, the parent can do so non-anonymously
- if it so chose.)
- </p>
- <p>
- This is a key facility (pun intended) of the OpenPrivacy platform,
- as anonymity can too easily be pierced by what is known as "data
- triangulation." For example, knowing only the age, zip code, and
- the make and model of a heretofore anonymous person's car can
- narrow the population quite a bit. But if each of these data
- points were stored under a different nym, then the same data
- exists, but it is unconnected. Others can make opinions as to
- what data is connected - and gain or lose reputation according to
- the value and usefulness of their opinions - but only the owner
- can prove it. Mechanisms exist that allow for such proof to be
- tied to a single receiving party, such that further dissemination
- of the proof without permission would directly - and adversely -
- affect the reputation of the receiver.
- </p>
- <h4>Bias Management</h4>
- <p>
- A reputation management system may assemble a set of related
- opinions into a <i>bias</i>. Bias is maintained via additional
- RCEs (possibly object clones) with different opinion sets. When a
- nym Ji creates new Opinions and adds these to an RCE, a smart
- implementation may choose to append these to Ji's bias for later
- use by getReputation requests so that results are better tailored
- for the nym.
- </p>
- <p>
- Often, a bias may consist of Opinions from multiple nyms,
- particularly since a parent nym may use multiple child nyms to
- make successive requests. Further, a nym may want to use the bias
- from someone else altogether, for it may want to benefit from the
- bias of someone it holds in high regard. Finally, a RCE itself
- may be created with and/or develop a bias through its standard
- activities. For example, it may use sophisticated collaborative
- filtering techniques to develop its own opinions and associated
- bias.
- </p>
- <h4>Reputation Calculation Engine (RCE)</h4>
- <p>
- The <i>reputation calculation engine</i> is the brains of a
- reputation service, as it determines opinions on the information
- it has available. In its simplest incarnation, an RCE might do
- little more than mechanical collaborative filtering to create its
- opinions. But a sophisticated RCE has additional information at
- its disposal, such as the reputations of the various local
- opinions (and their, recursive, reputations), access to the
- opinions of other, remote RCEs, the calculated or gifted bias of
- the requester, and even hand-tweaking by its human maintainer.
- Ultimately, what form its opinions take, their quality and other
- factors are judged by its peers who may then assign it a
- reputation, and seek its advice -- or not.
- </p>
- <h4>Opinion Store</h4>
- <p>
- A reputation server's <i>opinion store</i> supports the
- putReputation() and getReputation() methods which access some form
- of persistent data store. The store may be anything from simple
- in-memory hash tables to a full-blown Oracle database. We include
- the mention of the interface here only for completeness.
- </p>
- </blockquote>
- <h3>Communications</h3>
- <blockquote>
- <p>
- We outline a course-grained capability-based framework in which
- each nexus of reputation services - generally located one to a
- hardware machine - is considered to be a secure computation
- environment (or "vat" [<a href="#dist">dist</a>]) with respect to
- itself. <font color=red>[present a simple proof that supports
- this claim]</font> Communications between vats are signed and
- encrypted, but also asynchronous and may be unreliable. Secure
- streams can be built, analogous to the way in which SSL is
- implemented on top of TCP, which is in turn implemented on top of
- UDP, but are not required for operation. Note that communication
- channels and communicating objects themselves can gain or lose
- reputation capital according to their reliability and speed.
- While we define the implementation of the communications mechanism
- to be outside the scope of OpenPrivacy per se, we expect that a
- secure, anonymous and uncensorable mechanism such as those that
- Freenet, Free Haven or Publius [<a href="#free">free</a>] provide
- would be best suited to the need for robust, distributed and
- private communications.
- </p>
- </blockquote>
- <h3>Reference Applications</h3>
- <blockquote>
+ This file has moved; see
+ <a href="http://www.openprivacy.org/papers/200103-white.html">
+ http://www.openprivacy.org/papers/200103-white.html>
- <h4><a href="http://sierra.openprivacy.org/">Sierra</a>
- - The Reference Reputation Management System</h4>
- <p>
- Sierra is the reference implementation of our Reputation
- Management System. It is based on the Talon component framework
- and defines our RCE plugin mechanism.
- </p>
- <p>
- Sierra incorporates various subsystems which should be used by
- most RCE implementations. It defines our Nym management system,
- Store interface, Query interface and the Reputation objects which
- we use as Payload holders. Developers which wish to build RCEs or
- incorporate a Reputation Management System with their application
- should evaluate Sierra.
- </p>
- <h4><a href="http://talon.openprivacy.org/">Talon</a>
- - Reputation based Component Management System</h4>
- <p>
- Talon is a flexible component system which we expect to become the
- cornerstone of all OpenPrivacy applications. Talon is simple yet
- powerful, sharing many of the characteristics of XPCOM and
- Microsoft COM [<a href="#comp">comp</a>]. However, Talon solves a
- number of problems with these existing systems and also
- incorporates Reputations (Sierra) as part of its Component factory
- mechanism. Since Talon uses RCEs to determine what components to
- return, natural selection can take hold and a Talon-based system
- can "evolve" over time to become more efficient and powerful.
- This mechanism is similar to advanced profiler technologies [<a
- href="#prof">prof</a>] but works with distributed systems.
- </p>
- <h4><a
- href="http://www.openprivacy.org/projects/jetspeek.shtml">JetsPeek</a>
- - A Privacy and Reputation-enhanced Internet Portal</h4>
- <p>
- JetsPeek is an OpenPrivacy-enhanced personal portal builder that
- keeps a user's profile anonymous. Further, it allows for the
- attachment of Opinions to news stories (and to Opinion makers),
- which enables using reputation mechanisms to more accurately
- find and filter information.
- </p>
- <p>
- JetsPeek taps XML (RSS) channels that are published via the Open
- Content Syndication (OCS) mechanism. JetsPeek also supports the
- pseudonymous publishing of preferences as well as the creation of
- nym-based RSS channels that may be subscribed to (and earn
- reputation from) other peers on the network.
- </p>
- <h4>OpenPrivacy-enabled Communities, or<br>
- Slashdot Moderation for Advogato and Trust Metrics for Slashdot</h4>
- <p>
-
- </p>
- </blockquote>
- <h3>Security, Trust, Validation and Verifiability</h3>
- <p>
- The OpenPrivacy security model is based on the user's capability to
- have control over and optionally publish their profile in chunks
- under a multitude of apparently unrelated pseudonyms. This prevents
- "data triangulation" methods used by numerous agencies and
- corporations to accurately identify a person from their activities,
- even when their name is not known. Users can create Bias objects
- that contain references to a collection of Opinions that may or may
- not all belong to themselves, and in fact the Bias itself can be
- formed under yet another pseudonym. The Sierra Reputation
- Management System transparently handles user-level nym management,
- and a well designed RMS will flag any potential data leaks as
- dangerous.
- </p>
- <p>
- We do not attempt to defeat traffic analysis mechanisms nor locality
- of reference or storage attacks. Rather, our communications are
- transport agnostic, and we expect that many users will avail
- themselves of a growing number of anonymous and censorship-resistant
- publishing mechanisms such as Freenet and Free Haven.
- </p>
- <p>
- Despite all these easily manufactured pseudonyms, the OpenPrivacy
- system encourages the use of long-lived pseudonyms for purposes of
- publishing
- </p>
- <p>
- </p>
- <h3>Attack Resistance</h3>
- <p>
- <ul>
- <li><b>Denial of service (DOS):</b>
- </li>
- <li><b>Spoofing:</b>
- </li>
- <li><b>Replay:</b>
- </li>
- <li><b>Flooding:</b>
- </li>
- <li><b>Shills/Slander/False claims:</b>
- </li>
- </ul>
- </p>
- </blockquote>
- <h2><a name="economy">OpenPrivacy Enhances The New Internet Economy</a></h2>
- <blockquote>
- <h3>Anonymity</h3>
- <p>
- Within any society, anonymity has decided usefulness. Freedom from
- observation and monitoring of one's physical location, purchases,
- reading and movie viewing preferences and history are, by and large,
- no one else's business. There is a reasonable expectation of
- privacy through confidentiality contracts made between a person and
- their school, employer, financial institutions and health providers.
- As well, in a less common but no less important role, the cloak of
- anonymity can be used by the oppressed to bring the sins of
- their oppressors to light without fear of retribution.
- </p>
- <p>
- That said, law enforcement has traditionally been concerned about
- people being able to act anonymously, as they perceive a need to be
- able to track the actions of an unknowing public via electronic
- wiretaps, online data collection and physical surveillance. The
- aggregated information is often linked to ostensibly confidential
- databases gathered by employers, retailers and health care
- providers. If law abiding citizens have their privacy violated in
- the process, we are told not to worry, for we can "trust the
- government."
- </p>
- <p>
- Within the business world, the concept of profile data being
- anonymous - that is, unconnected to a person's name, address and
- other identifying means - strikes fear into the hearts of marketers,
- for while they could mine the data for concordances of interest,
- their present belief is that they would not be able to contact the
- market segments so identified.
- </p>
- <p>
- The OpenPrivacy platform enables a user to wear a cloak of anonymity
- while divulging information useful to others - and by extension to
- oneself - without losing their anonymity. She can participate in
- communities, browse personalized retail catalogs, and be marketed to
- more accurately by advertisers safely.
- </p>
- <h3>Trust</h3>
- <p>
- Anonymity has very real limitations, both in the social and business
- worlds. We find <i>trust</i> is built on the security of knowing
- and building relationships with our acquaintances and places of
- business over time. On the flip side, companies want to be able to
- provide personalized services that enhance their customer's
- experience and further, to understand their wants and capabilities
- so that they can be marketed to effectively.
- </p>
- <p>
- Trust is a key point, and when many people trust some entity it
- gains a positive reputation. (Note: negative reputations are
- possible, too.) Trust is in fact the bridge between anonymity and
- useful pseudonymity. The OpenPrivacy platform - through long-lived
- pseudonymous entities and the reputations they accrue - enables
- various trust metrics to be employed that support this bridge.
- </p>
- <h3>Pseudonymity and Reputations</h3>
- <p>
- <font color=red>[we will provide
- consumers with the privacy they desire while increasing the amount
- and quality of information available for data mining and direct
- marketing purposes. - address all three issues above...]</font>
-
- </p>
- <h3>The Value of Information [Quality]</h3>
- <p>
-
- </p>
- <h3>An Agoric, Reputation-based Marketplace [Capitalism]</h3>
- <p>
-
- </p>
- <h3>Efficiency Via Chaos and Bias</h3>
- <p>
- Chaos is an essential element for systems to evolve, for without
- it the unexpected changes and mutations that lead to new, often
- revolutionary processes will not have a chance to occur. The very
- fact that people are all different - not only from each other but
- even with one's self from moment to moment - has a valuable
- ramification: that we all have different opinions and bias. This
- points to a major failing of search engines: that each person who
- enters the same search X probably has a slightly different mind
- set of what they would like to see as results.
- </p>
- <p>
- OpenPrivacy thrives in this multitude of opinion, this diversity
- of thought, for though we are all different, there are certain
- areas that two very different people may align with. For example,
- suppose person A reads the New York Times every day and finds an
- average of four articles that A considers tops - well worth the
- cost of the paper and her time to find them. Now consider that
- there probably exists a person B who finds the same four articles
- to be indispensable. The safe, secure, pseudonymous publishing
- environment of OpenPrivacy, along with the agoric marketplace of a
- million infomediaries looking for valuable concordances, make it
- possible for these two people to virtually meet. Further, A may
- strike a deal with B to provide her with the editorial filtering
- process, saving A time and aiding B at least in reputation if not
- also financially.
- </p>
- </blockquote>
- <h2><a name="references">References</a></h2>
- <blockquote>
- <h3>Definitions</h3>
- <ul>
- <li><b>Reference:</b> A pointer to an entity (generally a URI, often
- a URL). Examples include a physical or virtual object, place,
- person, pseudonym, web page or site, opinion, reputation, bias,
- profile, and reputation calculation engine.
- </li>
- <p>
- <li><b>Nym:</b> Short for "pseudonym," a nym is a fictitious name
- that can refer to an entity without using any of its directly
- identifiable characteristics, such as name, location, etc.
- OpenPrivacy uses public-key pairs to represent a nym, with the
- owner having sole access to the private part and the public part
- being published to at least one external party. A long-lived nym
- is useful in that it allows for trust (or "reputation") to
- accumulate over time and usage. Often, we refer to the public key
- as the "nym," as it is how the entity is know in the outside
- world.
- </li>
- </p>
- <p>
- <li><b>Principal:</b> An identifiable, pseudonymous, or anonymous
- entity. A principal can be uniquely referenced by its public key.
- Any static entity that can be referenced can in theory be a
- principal, the only requirement being that it can store a private
- key and perform signature operations.
- </li>
- </p>
- <p>
- <li><b>Opinion:</b> A unique description of something (pointed to by
- a reference). Uniqueness is satisfied by attaching a hash,
- generally created from the pricipal's signature, to the opinion
- such that no two opinions are exactly the same. An opinion may be
- clearly subjective (as in "openssl is a good cryptography
- package") or appear as a statement (as in "I live in San
- Francisco," where the reference is "San Francisco" and the
- description is "where I live").
- </li>
- </p>
- <p>
- <li><b>Reputation:</b> A value that represents the collective
- opinion of some reference. A reputation is really just another
- name for an Opinion, as it is the calculated opinion of a
- Reference by the issuing Reputation Calculation Engine.
- Reputations are ephemeral, and the weight applied to an Opinion
- representing the reputation of some Reference is subjectively
- applied by the end user (person or program) that requests it. As
- Principals add their Opinion to a Reference, it accrues (positive
- or negative) <i>reputation capital</i> [<a href="#tmay">tmay</a>].
- </li>
- </p>
- <p>
- <li><b>Bias:</b> While reputations generally reflect the sum of many
- opinions of a single reference, a bias is an accumulation of
- opinions that represent the views of a single principal. Biases
- may be divided by area or type of reference (such as groups of
- political or demographically descriptive opinions). A RCE uses
- one or more Bias collections in the couse of its calculations.
- </li>
- </p>
- <p>
- <li><b>Offer Template:</b> A set of seemingly disparate opinions can
- be grouped together (in a bias-like structure) for the purpose of
- finding best matches in a universe of unconnected data. A
- reputation service that receives an offer template may advertise
- prizes for parent nyms that can validate ownership of a subset of
- the template.
- </li>
- </p>
- <p>
- <li><b>Profile:</b> A collection of pseudonymous opinions (also in a
- bias-like structure) that an entity claims that it can prove
- belong to a single (parent) entity. (The proof itself is called
- <i>validation</i>.)
- </li>
- </p>
- </ul>
- <h3>Bibliography</h3>
- <blockquote>
- <dl>
- <dt><a name="anon">[<b>anon</b>]</a> The Anonymizer
- <<a href="http://www.anonymizer.com/"
- target="_new">http://www.anonymizer.com>>
- <dt><a name="comp">[<b>comp</b>]</a> Component systems; see e.g.:
- <dd><li>XPCOM
- <<a href="http://www.mozilla.org/projects/xpcom/"
- target="_new">http://www.mozilla.org/projects/xpcom/>>
- </dd>
- <dd><li>Microsoft COM
- <<a href="http://www.microsoft.com/com/"
- target="_new">http://www.microsoft.com/com/>>
- </dd>
- <dt><a name="dist">[<b>dist</b>]</a> OpenPrivacy uses
- capability-based security; see e.g.:
- <dd><li><i>Distributed Computing in E</i>, <<a
- href="http://www.skyhunter.com/marcs/ewalnut.html#SEC36"
- target="_new">http://www.skyhunter.com/marcs/ewalnut.html#SEC36>>
- </dd>
- <dt><a name="free">[<b>free</b>]</a> Distributed,
- censorship-resistant publishing; see e.g.:
- <dd><li>Freenet
- <<a href="http://freenet.sourceforge.net/"
- target="_new">http://freenet.sourceforge.net>>
- <dd><li>Free Haven
- <<a href="http://www.freehaven.net/"
- target="_new">http://www.freehaven.net/>>
- <dd><li>Publius
- <<a href="http://www.cs.nyu.edu/~waldman/publius/publius.html"
- target="_new">http://www.cs.nyu.edu/~waldman/publius/publius.html>>
- <dt><a name="jets">[<b>jets</b>]</a> JetsPeek
- <<a href="http://www.openprivacy.org/projects/jetspeek.shtml"
- target="_new">http://www.openprivacy.org/projects/jetspeek.shtml>>
- <dt><a name="prof">[<b>prof</b>]</a> Advanced profiler
- technologies; see e.g.:
- <dd><li>Java HotSpot Technology
- <<a href="http://java.sun.com/products/hotspot/"
- target="_new">http://java.sun.com/products/hotspot>>
- </dd>
- <dt><a name="tmay">[<b>tmay</b>]</a> Tim May used the term
- "reputation capital" in a 1994 cypherpunk paper
- <dd><i>Crypto Anarchy and Virtual Communities</i>
- <<a href="http://www.idiom.com/~arkuat/consent/Anarchy.html"
- target="_new">http://www.idiom.com/~arkuat/consent/Anarchy.html>>
- </dd>
- <dt><a name="zero">[<b>zero</b>]</a> Freedom (by Zeroknowledge)
- <<a href="http://www.freedom.net/"
- target="_new">http://www.freedom.net>>
- </dd>
- </dl>
- </blockquote>
- <br>
- <hr width=200>
+ <br><br><br>
+ <hr width=300 align=left>
<font size=1><i>Copyright © 2001 Fen Labalme and
OpenPrivacy.org.</i></font>
</body>