Bit | First insight line |
---|---|
1.1 | Some p2p technology is more about marketing than product. |
1.2 | There’s far more to p2p than popularized MP3 file swapping. |
1.3 | Metcalfe’s Law: Network value rises by the square of the number of terminals. |
1.4 | Fragmenting a network dramatically reduces the perceived value. |
1.5 | Gilder's Law: Bandwidth grows at least three times faster than computer power (both with regard to total network capacity). |
1.6 | The Black Box Law: Networks evolve towards high-bandwidth, dumb pipes, with intelligence spread to the machines at their peripheries. |
1.7 | People talk—with each other, directly. |
1.8 | Modern p2p connectivity is usually transient, not permanent. |
1.9 | P2P assumes some form of end-to-end connectivity. |
1.10 | People use technologies to achieve their own goals. |
1.11 | The Internet paradigm is addressing resources, not individuals. |
1.12 | Domain addressing assumes static IP and constant connectivity. |
1.13 | The p2p focus is mainly on individual or content identity. |
1.14 | Current p2p treats intermittent variable connectivity as the norm. |
1.15 | Internet p2p is a reaction to the server-centric structure. |
1.16 | P2P is about distributed ownership of resources. |
1.17 | P2P is about distributed control of resources. |
1.18 | P2P is often about persistent storage of content. |
2.1 | Sharing distributed resources doesn’t necessarily make it p2p. |
2.2 | P2P innately supports natural, bidirectional conversational modes. |
2.3 | A-A conversational modes are the next emergent technology. |
2.4 | Presence is a crucial issue in human-usable p2p applications. |
2.5 | Up-to-date nodelists are a valuable resource in AP2P. |
2.6 | Workgroup networking in Windows is an atomistic p2p architecture. |
3.1 | Strong encryption will be a ubiquitous feature of p2p systems. |
3.2 | Atomistic networks can be characterized as “search and discovery”. |
3.3 | Atomistic search returns arbitrary, source-determined relevancy. |
3.4 | Atomistic search entities only return responses to queries for which they can process and return a relevant “hit”. |
3.5 | Peer networks can provide innovative services to simple queries. |
3.6 | Storage model decisions can restrict innovative functionality. |
3.7 | Distributed search and storage promote content availability. |
3.8 | Transfer resume and multiple-host sourcing must be considered almost essential features in content sharing and distribution. |
4.1 | Popular IM systems “track personal identity” but don’t actually care about a user’s real identity or authentication proof-of-use. |
4.2 | Both agency and e-commerce require secure authentication. |
4.3 | Full-featured IM clients expose far more than the user assumes. |
4.4 | Common p2p file-sharing systems tend to ignore user identity. |
4.5 | P2P deployment can easily mean a breach of firewall security. |
4.6 | “Clever” clients can unwittingly subvert proxy/firewall protection. |
4.7 | When considering p2p, think of leveraging existing resources and storage more than migrating to an entirely new infrastructure. |
4.8 | Peer clients invariably open unconsidered security holes. |
4.9 | Even a “closed” p2p network might inadvertently become public. |
4.10 | Any p2p deployment must consider what the users are likely to use it for, especially when the focus is content sharing. |
4.11 | Digital items are critically different from physical items, yet the public perception of ownership remains relatively unchanged. |
5.1 | Peer computers respond independently to requests from other peers. |
5.2 | Peer computers normally act and respond without central control. |
5.3 | Offline, a peer user’s real network address is unknown. |
5.4 | Broadcast-route in p2p refers to request propagation. |
5.5 | Amdahl's Law: System speed is determined by the slowest component in the data path. |
5.6 | At any loading, there will always be some nodes in the network that drop or delay requests due to local bandwidth saturation. |
6.1 | E-mail is an open, uniform and extensible, albeit asynchronous and low-priority p2p (server) protocol. |
6.2 | That IM implements the notion of user presence is its greatest asset. |
6.3 | Registered identities invariably overstates the number of users. |
6.4 | Proprietary protocols tend to be haphazard constructions. |
6.5 | AIM peer messaging is entirely dependent on central server relay. |
6.6 | Jabber is an XML-based peer architecture, not any specific application. |
6.7 | Jabber serves as a conduit between peer applications. |
7.1 | Gnutella is a common peer protocol, not any specific application. |
7.2 | TTL value is the only mechanism to expire descriptors on the network. |
7.3 | Gnutella message headers have no special framing sequences. |
7.4 | Pong data can refer to an arbitrary node. |
7.5 | Constantly changing topology means discarded descriptors. |
7.6 | Gnutella transfer requires at least one servent with no firewall. |
7.7 | A user can leave the network to improve download performance. |
7.8 | The ability to resume transfer might be dependent on client state. |
7.9 | The Gnutella connectivity model is “allow” unless explicitly denied. |
7.10 | Gnutella clients are natural gateway servers between networks. |
8.1 | Micropayment systems are resistant to DoS attacks and other abuse. |
8.2 | Selling relay server services are a good 24/7 way to earn Mojo. |
8.3 | The MojoID is a human-readable URL designating a unique file. |
8.4 | The network values new users who can provide more resources. |
8.5 | Mojo Nation records all transactions in session logs. |
8.6 | Realistic micropayment systems must be highly automated. |
8.7 | More Mojo Nation content means more agents working together. |
8.8 | Private publication of content is possible in Mojo Nation. |
8.9 | No single agent in Mojo Nation has a monopoly on anything. |
8.10 | Swarmcast forms transient networks (meshes) based on demand. |
8.11 | Swarmcast is a plug-in solution. |
9.1 | Only the first contacted node knows the user’s identity and location. |
9.2 | Freenet’s routing choices and performance improve over time. |
9.3 | Freenet requests and hence users are in practical terms anonymous. |
9.4 | Nearness to a node is totally unrelated to geographical proximity. |
9.5 | Freenet connectivity rewards successful content supply nodes. |
9.6 | Browsing and accessing content on Freenet is slow. |
9.7 | Removal of expired documents is automatic, intrinsic node behavior. |
9.8 | Fulfilled requests ensure continued document storage. |
9.9 | Everything in Freenet is stored in terms of key-data pairs. |
9.10 | Freenet 0.3 and Freenet 0.4 are incompatible protocols. |
9.11 | In Freenet, “not found” is not the same as “not stored anywhere”. |
9.12 | Insertion occurs at locations where requests are likely to be routed. |
9.13 | All security and anonymity measures make some assumptions. |
9.14 | Go with the defaults and recommendations for node installation and configuration, unless you really, really know what you’re doing. |
9.15 | Freesite content updates at midnight UTC—and only then. |
10.1 | Groove is mostly about interactive collaboration efforts. |
10.2 | The relay server is a transparent facilitator for all p2p functionality. |
10.3 | Codats are the basic unit of information exchanged by JXTA peers. |
10.4 | JXTA security is essentially up to the implementations. |
11.1 | Standard Internet protocols are the universal level playing field. |
11.2 | Reed’s Law: The social value of the network is proportional to 2n. |
11.3 | The primary academic goal is to publish information openly. |
11.4 | The primary goal of business is to sell something exclusive. |
11.5 | The primary goal of government and law is to control and regulate. |
11.6 | Resistance is futile. Prepare to be assimilated. |
11.7 | Open source is firmly in the build-now, regulate-later camp. |
11.8 | Content subscriptions per site are not a viable e-revenue solution. |
11.9 | Viable network agency will presume a micropayment infrastructure. |
12.1 | Granting free access to large and powerful unused network resources, even as a quasi-regulated p2p resource, is not without its risks. |
12.2 | Viable network information content presumes a trust infrastructure. |
13.1 | Today’s optional, premium feature is tomorrow’s standard. |
13.2 | The race is on to design a next-generation Internet operating system. |
13.3 | A successful collaboration rests on well-defined transactions. |
13.4 | For every Internet access obstacle, there are several workarounds. |
13.5 | Internet information flow must be more bidirectional to be useful. |
13.6 | Pragmatics: Information is authoritative if many sources quote it. |
3.144.84.155