Accomplished thus far ~ ornia

This page exists to document the evolution of the ornia project up until the present date, describing all of the things that have been accomplished and created since ornia's inception. For a list of things yet to be accomplished on ornia's to-do list, see the To be continued.... ~ ornia article. The first general phase, or ornia 1.0 began about a month into the Fall 2006 semester, when Hampshire granted Niko Kern's server it's own publicly valid IP address and domain name after he crafted an academic justification for such resources. During this phase, ornia existed first and foremost as Niko's playground for exploring GNU+Linux server administration, and not many people knew about ornia or used its services. Even so, ornia was constantly changing during this period of some 14-15 months until Niko secured funding to breathe new life into the project.

In December of 2007, ornia 2.0 began. Niko rebuilt ornia from the ground up, purchasing separate hardware pieces and built an entirely new server from scratch, with the hardware listed on the ornia page. Because ornia 2.0 began with entirely new hardware, the software portion of ornia also had to be re-created to match the new machine. In this new era of ornia, more services were added which raises awareness and use of ornia to levels which are orders of magnitude greater than any such use during ornia 1.0. ornia 2.0 is currently being developed and improved to make ornia accessible, easy to use, and useful for Hampshire students in particular, but also the rest of the Internet as well.

= ornia 1.0 =

The timeline of accomplishments for the ornia 1.0 phase is largely irrelevant to the current composition and use of ornia as it exists today. Effectively speaking, ornia 1.0 was an experimental, exploratory phase for Niko, who cared for ornia for over a year with no one else really caring or even knowing of ornia's existence. This phase of exploration and development was most useful so that Niko could learn how to best install, set up, configure, and run various services on the Internet. Many of the services that currently run in ornia 2.0 where available and initially explored back in this phase. As such, ornia 1.0 played an important, albeit indirect role in the formation of ornia as a project which has grown to effect many people.

Hardware build
ornia during the 1.0 phase was constructed of spare x86 PC parts collected by Niko during his mid-teenage years, and assembled as a secondary computer. While it was never intended to be a particularly fast computer, it was certainly comprised of second-hand, relatively outdated components. Even so, none of the components ever failed, and ornia 1.0 remains assembled in Niko's room to this day, waiting for some greater use or purpose. The hardware components are as follows:


 * Mainboard: 1 x
 * CPU: 1 x AMD Athlon XP 1900+
 * RAM: 2 x
 * Parallel ATA Hard Disk Drive: 1 x 60GB Maxtor -- Parallel ATA (IDE) Hard Drive
 * Power Supply Unit: 1 x
 * Heatsink/Fan: 1 x
 * Chassis: 1 x generic beige box metal/plastic chassis

Operating System
The operating system chosen for ornia was of course GNU+Linux, specifically the Slackware distribution. Slackware was chosen for it's smooth simplicity, power, and elegance. It was Niko's first GNU+Linux distribution, which also perhaps aided his bias towards using it for ornia. Slackware takes a minimalistic approach at software installation and removal, also known as package management. During the ornia 1.0 phase, hardly any package management was in use at all, and all software was compiled from source using the GNU Compiler Collection. The version of Slackware used initially still had the 2.4.x branch of the Linux kernel enabled by default.

Networking Setup
After bringing this machine to Hampshire with him in the beginning of the Fall 2006 semester, Niko quickly got it set up in the server room at Hampshire. First and foremost, ornia needed its own, globally valid IP, or Internet Protocol address. This means that anyone can access ornia directly from anywhere on the Internet, as opposed to the vast majority of the computers on Hampshire campus which are "hidden" from the rest of the Internet by a technique known as Network Address Translation. ornia was granted the IP address 192.101.188.51, and was configured to use this address for all communications on its sole Ethernet port.

Because the IP address is not exactly easy to remember and type in every time anyone wants to use the services of ornia, Niko and Dan Parker assigned a domain name entry in Hampshire's primary DNS server which would automatically resolve any requests for "ornia.hampshire.edu" to the IP address "192.101.188.51" anywhere in the world. This makes ornia extremely easy to access and make use of. During ornia 1.0, there were no other domain names assigned to ornia's IP address.

Even though ornia has its own IP address and domain name which is valid for the entire world to access, there is still a firewall between Hampshire College and the rest of the Internet which ornia rests behind. This firewall by default denies all incoming traffic from the Internet which is not a response to an earlier outbound request from a computer at Hampshire. This means that as a server, no one on the Internet would be able to access ornia's services unless ornia specifically knew beforehand that they wanted to connect to a specific daemon. ornia is not psychic, so the best solution is to poke holes in the firewall specifically to ornia for whatever services happen to be appropriate to be open to the Internet at large. Only services which have been specifically allowed in the firewall at Hampshire can be accessed by others on the Internet off campus. Because the firewall only affects traffic to and from the external Internet from Hampshire, anyone located on the Hampshire College campus can access every service on ornia possible at much faster speeds. Physically speaking, ornia only had a single 10/100 Megabit per second Ethernet RJ-45 port, which was connected to a switch in the server room on the ground floor of the Library.

Services
For a server, there typically is no GUI, or Graphical User Interface. This is because there is no need to have menus and windows in the direct interaction with the computer. ornia normally has no monitor, keyboard, or mouse plugged into the motherboard, because there is no need. The only two chords plugged into ornia during the 1.0 phase were the network cord going into the Ethernet RJ-45 jack on the motherboard, and the power cord plugging into the Power Supply Unit supplying the machine with DC power. Therefore, all administration of ornia was always done remotely, from other computers connecting in to it using the Secure Shell (SSH) protocol.

It is through the CLI, or Command Line Interface, that ornia is manipulated and instructed to run certain programs. Which programs are chosen to run defines ornia as a server more than anything else. Through these text-based terminal sessions over SSH, Niko would continuously log in and download, unpack, compile, install, and configure a variety of server programs. Each server program, or daemon, runs in the background 24/7 with ideally zero interruptions or downtime. What primarily distinguishes a daemon from applications one generally runs on a desktop or laptop computer is the fact that it exists to receive incoming communications and requests from those desktops/laptops, so that they may serve these so-called "clients" with information. This relationship is known as the client-server model. ornia is the server running daemons, and your computer is the client, running network applications which request services from ornia, as well as millions of other servers.

Each service Niko wished to experiment with and offer to the world requires another program, or daemon to be installed, configured, and running in the background. What follows is a list of services Niko set up during ornia 1.0 and the daemons he chose to run those services.

Web sites (HTTP)
The websites on ornia 1.0 were run by the 1.x branch of the Apache web server, a powerful Free Software web server which powers the vast majority of websites on the Internet.

E-mail (SMTP and IMAP)
E-mail on ornia is powered by Citadel, a groupware server designed to have complete e-mail, calendering, and collaboration features in one package. Simple Mail Transfer Protocol (SMTP) is used for sending outbound e-mails to other mail servers on the default port of TCP 25, and Internet Message Access Protocol (IMAP) using SSL encryption is used for retrieving e-mails from the server to read on the client's Mail User Agent. This service is available on the default IMAP/SSL port, TCP 993. The protocol POP3 was deliberately disabled for mail because of it's antiquated nature, and IMAP without SSL encryption was also disabled to ensure a secure connection between ornia's Citadel server and the client's e-mail software.

Webmail (HTTPS)
The Webmail service on ornia is provided by Webcit, an add-on to Citadel. It is functionally the same e-mail server as Citadel, but merely accessible via the HTTP protocol encrypted with SSL. ornia's webmail is hosted on the default HTTPS port, TCP 443.

File Transfer Protocol (FTP)
There are many different FTP daemons in existence, but after much research and tinkering, Niko chose wzdftpd as the optimum balance of features, power, and ease of use. For any FTP user account and accompanying password that is created, Niko ensures that the use of explicit TLS encryption on both the data and control channels is mandatory. FTP over explicit TLS is being hosted on the default FTP ports of TCP 21 for the control channel and TCP 20 for the data channel.

Synchronous Conferencing (PSYC, IRC, and XMPP)
During a search for a proper Internet Relay Chat (IRC) server daemon, Niko stumbled upon a far superior synchronous conferencing (chat) protocol: PSYC, or Protocol for SYnchronous Conferencing. There are many benefits of PSYC over IRC, but Niko soon found out that the reference implementation of PSYC (called psyced) actually implemented not only the PSYC protocol itself, but also IRC and Extensible Messaging and Presence Protocol (XMPP), the latter of which is also known as Jabber. With psyced, ornia is turned into a powerhouse of free/open synchronous conferencing protocols with a single daemon.

PSYC connections can be made on the default PSYC port of 4404 TCP and UDP. IRC connections are available on the default IRC port of TCP 6667, but SSL/TLS encryption is mandatory. XMPP is also available on the default port of TCP 5222, again with mandatory SSL/TLS encryption.

Radio Streaming (HTTP)
ornia uses Icecast to stream audio over the HTTP protocol in the patent-free Ogg Vorbis format. Niko can run an Icecast source client on any computer which sends the stream to be broadcast to ornia's Icecast server, and anyone can connect to the Icecast server to listen to what is being broadcast by the source client. The web interface for ornia's Icecast server as well as the radio stream itself are available on TCP port 3030.

Quake (Quakeworld)
Ahh, Quake. id Software's classic First Person Shooter which revolutionised the genre with fully 3-dimensional graphics and its artistic ambient environment, not to mention its insanely (for its time) popular multiplayer TCP/IP play. After a while, id Software released the Quake source code under the GNU GPL, making it Free Software, including the improved network efficient version of multiplayer Quake: Quakeworld. ornia runs a Quakeworld server daemon, called qwsv, on the default Quakeworld port of UDP 27500.

Nexuiz (Nexuiz)
Because Quake was GPL licensed, people were able to take the source code and dramatically improve and update it. There have been interesting results, including this game. Unlike Quake, not only the software but also all content (music, maps, textures, models, etc.) is GPL licensed and therefore Free Culture. Nexuiz is also cross-platform and can be accessed on UDP port 8767, or simply through the built-in server browser in the game (ornia should show up in the list of servers).

Secure Shell (SSH)
This is the service which is primarily used by Niko alone. SSH is the protocol used to remotely log in to an operating system over an encrypted channel. With SSH, Niko can log into ornia and manipulate anything he pleases, be it running or killing daemons, installing or upgrading software, altering configurations, moving and renaming files and directories, etc. To utilise SSH, one must have a valid username and password for logging in to the system. The SSH daemon, or sshd, is run on the default SSH port of TCP 22.

= ornia 2.0 =

ornia 2.0 began in November/December of 2007, during the end of Niko's third semester at Hampshire. After securing the funding for a rehaul of the project, Niko purchased entirely new components and created a new phase of ornia. There were dramatic changes in this new phase, which improved the stability, features, and flexibility of the project immensely. ornia is currently in the 2.0 phase, pending perhaps some future, unforeseen rehaul of the project from the ground up.

Hardware Synthesis
Much like ornia 1.0, the current phase of ornia is owned and controlled by Niko Kern alone. He owns all of the hardware in the server and is the only person who consistently alters its setup and operation to improve the accessibility and features of ornia's services. After a good 20+ hours of research on which make and model to purchase for each component of the new server, Niko proceeded to order all of the required components from Internet websites using a combination of the search engine Pricewatch and Google Product Search to find the best prices.

Each hardware component was chosen with Freedom in mind. There was a conscious decision to support the companies who have been friendly towards the Free Software world, such as a motherboard manufacturer who paid an employee to enable LinuxBIOS (now called coreboot) compatibility with their motherboard, or AMD for the CPUs and video card because they released graphics processing unit hardware documentation to enable the creation of Freely licensed drivers for all ATI-brand video cards. Current hardware specifications and pictures of the building process for ornia 2.0 are available on the ornia main page.

Operating System
For ornia 2.0, The Debian distribution of GNU+Linux was chosen for multiple reasons. Debian has a staunch commitment to having any data whatsoever included in the main distribution be Freely licensed, be it software, documentation, images, audio, or video data. It is a community run and maintained operating system which no individual or corporation owns or controls. It has thousands of software packages available for it, essentially built in to the operating system.

This package management system, called APT or Advanced Packaging Tool, was a large motivation for moving towards Debian as the operating system to use for ornia. Because of the packaging system, it is very easy to install new software and upgrade existing installations, and the integration with Xen was a large benefit as well.

RAID
Prior to ornia 2.0, Niko had never worked directly with RAID before. RAID (Redundant Array of Independent Disks) is a technique using multiple hard drives of the same capacity to boost performance or redundancy, and sometimes both. There are different types of RAID, known as levels, which provide varying levels of performance and redundancy, but most RAID configurations prove beneficial in case a hard drive dies. The redundancy aspect uses hard drive space to store essentially multiple copies of the data so that if a drive dies, the data on that drive can be restored.

ornia 2.0 uses RAID-1 and RAID-5. RAID-1 is also known as mirroring, which provides pure redundancy: two hard drives in RAID-1 have the exact same data on them, so if one dies there is another with the data still alive. RAID-1 is used on the two, small (137GB) Serial Attached SCSI hard drives which store the operating systems, applications, and web site data on them.

RAID-5 uses block-level striping with parity data distributed across all member disks. This means that you can have three or more hard drives striped together making one big storage pool while at the same time having them be redundant. The parity data necessary to restore a given drive is split across all other drives in the array, meaning of the six hard drives in ornia 2.0's RAID-5 array right now, one could die and the data could be restored from the parity information for that drive which is spread across the other five disks in the array.

ornia's RAID implementations are handled not by a hardware controller, but rather by the Linux kernel's software RAID features. While this is not as fast as a dedicated microcontroller for handling RAID operations, it is sufficiently swift given ornia's massive amounts of processing and memory resources.

Virtualisation
This is a technology which has practically speaking revolutionised the server room, and theoretically speaking revolutionised our entire paradigm of using computers: we can now run multiple operating systems on our microcomputers simultaneously. This is supremely practical for many uses, especially right now in the server room. We can use virtualisation to reduce the carbon footprint of server rooms dramatically: when a new server needs to be deployed, we can simply install a new operating system on a currently existing piece of hardware.

The idea of running multiple operating systems on computers is not exactly new, but Free Software solutions are reaching prime time in enterprise use and capabilities. The traditional proprietary, non-free vendor of virtualisation solutions, VMWare, is no longer necessary. The Central Processing Units in ornia 2.0 actually have a feature specifically designed to enable hardware virtualisation with Free Software solutions without modification of the guest operating system. Because ornia 2.0 runs only Free Software operating systems which can indeed be modified specifically to be paravirtualised, this is a non-essential but nice feature.

ornia has been set up from scratch on the software end with the GPL-licensed Xen virtualisation hypervisor. When ornia boots up, the first thing to load after the boot loader (GRUB) is the Xen hypervisor, which in turn loads the host operating system, or domain 0 in Xen-speak. This domain 0, or dom0 can then act as the host for a multitude of other guest operating systems, or domain U's (domU). The dom0 on ornia is used for hardly anything at all, with practically no network-accessible services being run on it. This is for security, mainly, but also practicality. Any services to run for people either on Hampshire's local network or on the Internet can be more easily and fluidly controlled as daemons running on the domU's.

Logical Volumes
Yet another technology deployed in ornia 2.0 is the use of the Linux kernel's Logical Volume Manager in lieu of hard drive partitions. Instead of the old limit of only four primary partitions in total, all of which are static in size, LVM brings in a new era of control and flexibility. With LVM, ornia's so-called logical volumes can be dynamically grown, shrunk, moved, backed up, or restored. Each domU operating system lives within its own logical volume, as well as special data directories such as the web site data for all of ornia.

Hard drive encryption
The RAID-5 array contains a filesystem never before used by Niko, the XFS filesystem. The special quality about this array isn't so much it's use of software RAID for parity and striping, nor the use of the XFS filesystem, but rather that it's entire contents are encrypted using dm-crypt in the Linux kernel to encrypt all data stored in the array with Advanced Encryption Standard aka Rijndael.

This adds a level of security to ornia, obscuring the contents of this array to any organisation who might happen to steal or confiscate ornia's hardware.

ornia as only one part of the server
During the ornia 2.0 phase, it should be noted that ornia itself is actually not the entire machine. With the new scheme of virtualisation, ornia is merely a single domU guest operating system running under both the domain 0 host operating system and the Xen hypervisor. This means that the physical hardware that ornia runs on can be used for more purposes than ornia itself currently runs. Entire operating systems can be used or rented to yield entirely new services on an entirely new machine. In this sense, ornia in this new phase takes an ambiguous definition: is ornia the whole machine and all software on it as it once was, or is ornia only certain bits on the hard drives? What defines a non-physical computer?

services in the ornia domU
All of the services from ornia 1.0 have since been recreated, most often with newer versions of the daemons. In addition, there have been quite a few new additions, including the DirectConnect hub which has served to thrust ornia as a project and a concept into the conscious minds of Niko's fellow Hampshire students.

Web sites (HTTP)
ornia 2.0 uses the Apache HTTP Server version 2.2.3 to serve up websites, and now wikis. All websites are accessible using the HTTP protocol on port 80 TCP, the default HTTP port.

E-mail (SMTP and IMAP)
E-mail for ornia 2.0 is again powered by Citadel, the groupware server designed to have complete e-mail, calendering, and collaboration features in one package. Simple Mail Transfer Protocol (SMTP) is used for sending outbound e-mails to other mail servers on the default port of TCP 25, and Internet Message Access Protocol (IMAP) using SSL encryption is used for retrieving e-mails from the server to read on the client's Mail User Agent. This service is available on the default IMAP/SSL port, TCP 993. The protocol POP3 is deliberately disabled for mail because of it's antiquated nature, and IMAP without SSL encryption is disabled to ensure a secure connection between ornia's Citadel server and the client's e-mail software.

Webmail (HTTPS)
The Webmail service on ornia is provided by Webcit, an add-on to Citadel. It is functionally the same e-mail server as Citadel, but merely accessible via the HTTP protocol encrypted with SSL. ornia's webmail is hosted on the default HTTPS port, TCP 443.

DirectConnect (DC)
Ahh, beauty, love, and sunshine. This is why Hampshire loves ornia so much. ornia's DirectConnect hub provides a service much needed and surprisingly absent on the Hampshire College campus: simple, free, cross-platform file sharing and synchronous communication. The DirectConnect hub is powered by Verlihub 0.9.8d RC2 and accepts connections on the default DC port of TCP 411. This service is closed to the external Internet, with TCP 411 being disabled in Hampshire's firewall to ornia. This provides anonymity and safety to students, faculty, and staff who choose to use this service.

DirectConnect is not only a powerful way to trade data between our computer's quickly, but it also serves as a Hampshire-specific social networking tool. With ornia's hub, we can communicate with any other student, faculty member, or staff person instantly from out computers without resorting to the Internet. Local communications are faster and safer, and it makes sense to keep all such file transfers and communications on campus when the source and destination are both at Hampshire College. ornia in this sense has revolutionised the way a large portion of the student body transfers data to one another, and to a lesser extent communicate with one another.

Database (MySQL)
ornia uses databases on the backend for multiple different daemons, including the DirectConnect hub and wikis. While it is disabled and discouraged to connect to ornia's databases from anywhere except ornia itself, it is an essential part of providing certain services on ornia. The database software used on ornia is the famous MySQL Database Server, licensed under the GPL and now owned by Sun Microsystems after a one billion dollar takeover. In running the MySQL database, Niko has had to learn the Structured Query Language in order to communicate with it effectively and efficiently on the command line.

Voice over IP (Mumble)
ornia's Voice over IP service is different than the usual peer-to-peer telephony connections which most people are used to from normal telephones, SIP phones such as Ekiga, or Skype. Mumble is a client-server architecture, hence running the Mumble service on ornia and having many people connect to it from their client machines. ornia's Mumble service can hold many, many people on at once. Once connected to Mumble, users can join different channels and speak with everyone in the given channel at once. This provides unlimited, free party line between as many users as desired.

A magnificent benefit of Mumble is that it is Freely licensed, cross-platform, and encrypted by default. Once connected to the server you can view the encryption (AES) properties in Server --&gt; Information. Mumble is a superior replacement for the proprietary technologies Ventrilo or Teamspeak. ornia's Mumble server runs on port 8767 TCP/UDP.

File Transfer Protocol (FTP)
As in ornia 1.0, wzdftpd was chosen to be ornia's FTP daemon. For any FTP user account and accompanying password that is created, Niko ensures that the use of explicit TLS encryption on both the data and control channels is mandatory. FTP over explicit TLS is being hosted on the default FTP ports of TCP 21 for the control channel and TCP 20 for the data channel.

Synchronous Conferencing (PSYC, IRC, and XMPP)
During a search for a proper Internet Relay Chat (IRC) server daemon, Niko stumbled upon a far superior synchronous conferencing (chat) protocol: PSYC, or Protocol for SYnchronous Conferencing. There are many benefits of PSYC over IRC, but Niko soon found out that the reference implementation of PSYC (called psyced) actually implemented not only the PSYC protocol itself, but also IRC and Extensible Messaging and Presence Protocol (XMPP), the latter of which is also known as Jabber. With psyced, ornia is turned into a powerhouse of free/open synchronous conferencing protocols with a single daemon.

PSYC connections can be made on the default PSYC port of 4404 TCP and UDP. IRC connections are available on the default IRC port of TCP 6667, but SSL/TLS encryption is mandatory. XMPP is also available on the default port of TCP 5222, again with mandatory SSL/TLS encryption.

Radio Streaming (HTTP)
ornia uses Icecast to stream audio over the HTTP protocol in the patent-free Ogg Vorbis format. Niko can run an Icecast source client on any computer which sends the stream to be broadcast to ornia's Icecast server, and anyone can connect to the Icecast server to listen to what is being broadcast by the source client. The web interface for ornia's Icecast server as well as the radio stream itself are available on TCP port 3030.

Video Streaming (HTTP)
With the newer versions of Icecast, ornia can now stream Theora encoded video to anyone on the Internet. The amount this streaming capability has been used is fairly low, but it is possible. The client of choice to watch such streaming videos is of course VLC.

Wikis (HTTP)
ornia runs a growing number of wikis after the explosive growth of Hampedia demonstrated the insatiable demand for wikis for various educational institutions, or even companies and governments. The Hampedia sister project, MoHopedia runs on ornia and is accessible at mohopedia.org, mohopedia.net, or mohopedia.com. Also running on ornia is an expirement of the Guatemalan Congress to use a wiki platform as a means to engage the citizenry of a country in participatory legislation drafting. The project is called Leviwiki and can be accessed at leviwiki.org or leviwiki.com. The Congress of Guatemala has chosen a single law to test first, a cybercrime law. They will post a draft of the law onto Leviwiki and invite others to come and edit it and comment on it. This is as of now an unprecented way of drafting legislation and will be an interesting thought experiment with regards to rethinking the very organisation of society in the new era of egalitarian access to technology. ornia is also running a brand new wiki for a university in Guatemala called Vallepedia, which can be accessed at vallepedia.com and vallepedia.org. While Niko handles all the technological work on the wikis, he continues to work with Jose Fuentes on developing them as platforms.

Quake (Quakeworld)
Ahh, Quake. id Software's classic First Person Shooter which revolutionised the genre with fully 3-dimensional graphics and its artistic ambient environment, not to mention its insanely (for its time) popular multiplayer TCP/IP play. After a while, id Software released the Quake source code under the GNU GPL, making it Free Software, including the improved network efficient version of multiplayer Quake: Quakeworld. ornia runs a Quakeworld server daemon, called qwsv, on the default Quakeworld port of UDP 27500.

Nexuiz (Nexuiz)
Because Quake was GPL licensed, people were able to take the source code and dramatically improve and update it. There have been interesting results, including this game. Unlike Quake, not only the software but also all content (music, maps, textures, models, etc.) is GPL licensed and therefore Free Culture. Nexuiz is also cross-platform and can be accessed on UDP port 8767, or simply through the built-in server browser in the game (ornia should show up in the list of servers).

Tremulous (Tremulous)
Tremulous is a first person shooter/real-time strategy combination based on the GPL-licensed id Tech 3 (Quake 3) engine. Not only is the software GPL-licensed, but the game content is CC-BY-SA 2.5 licensed, making the entire finished product free software and culture, much like Nexuiz. ornia's Tremulous server is available in the built-in server browser of the game, as well as external server browsers such as XQF.

Secure Shell (SSH)
This is the service which is primarily used by Niko alone. SSH is the protocol used to remotely log in to an operating system over an encrypted channel. With SSH, Niko can log into ornia and manipulate anything he pleases, be it running or killing daemons, installing or upgrading software, altering configurations, moving and renaming files and directories, etc. To utilise SSH, one must have a valid username and password for logging in to the system. The SSH daemon, or sshd, is run on the default SSH port of TCP 22.

= What is in ornia's future? =

While this page serves as documentation of what has already happened with ornia, there are many things yet to be accomplished in the ornia multiverse. A rough list describing what is on Niko's to-do list for improving ornia exists on the page To be continued.... ~ ornia. Items on that page will gradually be moving over to this one as they are completed. Anyone is welcome to edit the to-do list with suggestions of new services or improvements to existing services.

= See Also =

ornia

ornia Portal

Examining Anonymity Online (Birth of ornia)

To be continued.... ~ ornia