background preloader

Freenet

Freenet
History[edit] The origin of Freenet can be traced to Ian Clarke's student project at the University of Edinburgh, which he completed as a graduation requirement in the Summer of 1999.[9][10][11] Ian Clarke's resulting unpublished report "A distributed decentralized information storage and retrieval system" (1999) provided foundation for the seminal paper written in collaboration with other researchers, "Freenet: A Distributed Anonymous Information Storage and Retrieval System" (2001).[12][13] According to CiteSeer, it became one of the most frequently cited computer science articles in 2002.[14] The distributed data store of Freenet is used by many third-party programs and plugins to provide microblogging and media sharing,[16] anonymous, decentralised version tracking,[17] blogging,[18] a generic web of trust for decentralized spam resistance,[19] Shoeshop for using Freenet over Sneakernet,[20] and many more. Features and user interface of the Freenet[edit] Content[edit] Network[edit] Frost

UUCP UUCP is an abbreviation of Unix-to-Unix Copy.[1] The term generally refers to a suite of computer programs and protocols allowing remote execution of commands and transfer of files, email and netnews between computers. Specifically, a command named uucp is one of the programs in the suite; it provides a user interface for requesting file copy operations. The UUCP suite also includes uux (user interface for remote command execution), uucico (the communication program that performs the file transfers), uustat (reports statistics on recent activity), uuxqt (execute commands sent from remote machines), and uuname (reports the UUCP name of the local system). Some versions of the suite include uuencode/uudecode (convert 8-bit binary files to 7-bit text format and vice versa). Technology[edit] UUCP can use several different types of physical connections and link layer protocols, but was most commonly used over dial-up connections. History[edit] Mail routing[edit] User barbox! Bang path[edit]

The Freenet Project - /index Alternative DNS root The Internet uses the Domain Name System (DNS) to associate numeric computer IP addresses with human readable names. The top level of the domain name hierarchy, the DNS root, contains the top-level domains that appear as the suffixes of all Internet domain names. The official DNS root is administered by the Internet Corporation for Assigned Names and Numbers (ICANN). In addition, several organizations operate alternative DNS roots, often referred to as alt roots. The Internet Architecture Board (IAB) has spoken out strongly against alternate roots in RFC 2826.[1] Description[edit] The DNS root zone consists of pointers to the authoritative domain name servers for all TLDs (top-level domains). Alternative DNS roots may be characterized broadly as those run for idealistic or ideological reasons, run as profit-making enterprises, and those run internally by an organization for its own use. List of alternative roots[edit] This section lists the known alternate DNS roots. NameCoin P2P DNS[edit]

Freenet Da Wikipedia, l'enciclopedia libera. Freenet è una rete decentralizzata, creata per resistere alla censura, che sfrutta le risorse (banda passante, spazio su disco) dei suoi utenti per permettere la pubblicazione e la fruizione di qualsiasi tipo di informazione. Freenet è stata costruita pensando ad anonimato e sicurezza, non alla velocità di trasmissione. Questa caratteristica la rende poco indicata per lo scambio di file di grosse dimensioni (come filmati e file audio). Freenet è software libero distribuito con GNU General Public License; essendo scritto in Java può funzionare su Microsoft Windows, GNU/Linux, Mac OS X e su tutti i sistemi operativi dotati di Java Virtual Machine. Sebbene molte nazioni censurino le comunicazioni per motivi diversi, hanno tutte una caratteristica comune: qualcuno deve decidere cosa tagliare e cosa mantenere, cosa considerare offensivo e cosa no. All'interno di Freenet è possibile utilizzare servizi simili al Web e alle BBS. Ian Clarke et al.

ScreenPlay The MediaWiki ScreenPlay Extension (ScreenPlay) is a text-formatting add-on which allows screenwriters and hobbyists the ability to use MediaWiki as a screenwriting tool. Synopsis[edit | edit source] <screenplay>An example is described</screenplay><scene int day>A '''Darkened''' Room</scene> [[Bob Ross|BOB]] sits in front of a computer screen. Will produce the following type of formatting: Note how word case has been adjusted in certain cases. Description[edit | edit source] ScreenPlay supports three new editing hooks to add style codes that visually re-format certain wiki syntax (specifically, those used for definition lists, or "dl's") into proper screenplay format. Though ScreenPlay is not a replacement for a full-featured ScreenWriting software package, it offers a number of advantages for screenwriters: Usage[edit | edit source] Installing ScreenPlay is as easy as installing any other MediaWiki extension. Once installed, it is a simple matter to use ScreenPlay. Hooks[edit | edit source]

Usenet A diagram of Usenet servers and clients. The blue, green, and red dots on the servers represent the groups they carry. Arrows between servers indicate newsgroup group exchanges (feeds). Arrows between clients and servers indicate that a user is subscribed to a certain group and reads or submits articles. One notable difference between a BBS or web forum and Usenet is the absence of a central server and dedicated administrator. Introduction[edit] The articles that users post to Usenet are organized into topical categories called newsgroups, which are themselves logically organized into hierarchies of subjects. In most newsgroups, the majority of the articles are responses to some other article. When a user posts an article, it is initially only available on that user's news server. The format and transmission of Usenet articles is similar to that of Internet e-mail messages. Today, Usenet has diminished in importance with respect to Internet forums, blogs and mailing lists. History[edit]

Simple Authentication and Security Layer Simple Authentication and Security Layer (SASL) is a framework for authentication and data security in Internet protocols. It decouples authentication mechanisms from application protocols, in theory allowing any authentication mechanism supported by SASL to be used in any application protocol that uses SASL. Authentication mechanisms can also support proxy authorization, a facility allowing one user to assume the identity of another. They can also provide a data security layer offering data integrity and data confidentiality services. SASL is an IETF Standard Track protocol and is, as of 2010[update], a Proposed Standard. SASL mechanisms[edit] A SASL mechanism implements a series of challenges and responses. "EXTERNAL", where authentication is implicit in the context (e.g., for protocols already using IPsec or TLS)"ANONYMOUS", for unauthenticated guest access"PLAIN", a simple cleartext password mechanism." SASL-aware application protocols[edit] See also[edit] Transport Layer Security (TLS)

Hyperlink Open standard An open standard is a standard that is publicly available and has various rights to use associated with it, and may also have various properties of how it was designed (e.g. open process). There is no single definition and interpretations vary with usage. The terms "open" and "standard" have a wide range of meanings associated with their usage. The definitions of the term "open standard" used by academics, the European Union and some of its member governments or parliaments such as Denmark, France, and Spain preclude open standards requiring fees for use, as do the New Zealand, South African and the Venezuelan governments. Many definitions of the term "standard" permit patent holders to impose "reasonable and non-discriminatory licensing" royalty fees and other licensing terms on implementers and/or users of the standard. Open standards which specify formats are sometimes referred to as open formats. Specific definitions of an open standard[edit] ITU-T definition[edit]

HTML5 and the ArcGIS Platform - Thinking about HTML5? With the steady growth in smart mobile devices and with increasing support of the HTML5 standard by modern web browsers, interest in HTML5 is clearly on the rise. Webinar Recording Recorded: July 4, 2013 (32 minutes) HTML5-based web and mobile mapping technology has evolved to a point that organizations are leveraging the HTML5 standard and associated technology to provide ready access to spatial data like never before. As well as delivering straightforward, easy-to-use public access to maps via smartphones, tablets, and desktop web browsers without plug-ins, web mapping development platforms like Geocortex are now being deployed in parallel with Esri's ArcGIS platform to help organizations collect and edit data in the field—including in remote and offline environments. Using examples and principles associated with the spatial application infrastructure developed by Latitude Geographics, this webinar will explore how organizations are starting to leverage new development possibilities introduced by the ongoing evolution of web standards.

Related: