initial commit
This commit is contained in:
commit
7a01455c61
|
|
@ -0,0 +1,57 @@
|
|||
<!DOCTYPE html>
|
||||
|
||||
<head>
|
||||
<title>Dataforge UUCP</title>
|
||||
<link rel="stylesheet" href="css/main.css" type="text/css">
|
||||
</head>
|
||||
<body>
|
||||
<div id="container">
|
||||
<div id="header">
|
||||
<h1>Dataforge UUCP</h1>
|
||||
</div>
|
||||
<div id="nav">
|
||||
<ul class="menu">
|
||||
<li><div style="color: green"><a href="about.html">About Dataforge</a></div></li>
|
||||
<li><a href="manifesto.html">UUCP Manifesto</a></li>
|
||||
<li><a href="sites.html">Network Sites</a></li>
|
||||
<li><a href="http://uucp.dataforge.tk/~uucp/wiki/">Wiki</a><li>
|
||||
<li><a href="faq.html">FAQ</a></li>
|
||||
</ul>
|
||||
<center>
|
||||
<hr class="join">
|
||||
<h3><a href="join.html">Join Us!</a></h3>
|
||||
</center>
|
||||
</div>
|
||||
<div id="content">
|
||||
<h1>About Dataforge</h1>
|
||||
<p>
|
||||
Dataforge is an fledgling independent, hybrid shell provider/tilde server operated by Wesley Banderia (aka; praetor) of Fort Worth, Texas.
|
||||
While it's core mission is to provide services to retrocomputing enthusiasts, it serves as a home for anyone.
|
||||
</p>
|
||||
<p>
|
||||
Dataforge is hosted on a fleet of Silicon Graphics machines, its primary tilde host is running on an SGI Challenge S.
|
||||
Dataforge UUCP, however, is running on a Google Cloud VPS for purposes of reliability and fault tolerance.
|
||||
</p>
|
||||
<p>
|
||||
While being the youngest of the pubnix/tilde projects, its administrator has over 20 years of Systems Engineering experience
|
||||
and has provided services for a variety of organizations including the United States Air Force, Argonne National Labs, Boeing
|
||||
and others during his time of service with Linux Networx/Silicon Graphics. He also served as Chief Technology Officer for a federal
|
||||
contractor servicing the US Nuclear Regulatory Comission and the Department of Energy. As such, Wesley is a previous holder of a DoD
|
||||
"SECRET" clearance and is familiar wtih FIPS and OPSEC security best-practices. He strives to make Dataforge not only fun, but secure
|
||||
for all its users.
|
||||
</p>
|
||||
<p>
|
||||
<a href="http://www.dataforge.tk">Main Website</a><br>
|
||||
<a href="mailto:wfisher@dataforge.tk">Contact</a>
|
||||
</p>
|
||||
<br>
|
||||
<p>
|
||||
<center>
|
||||
<img src="img/lab.jpg">
|
||||
<img src="img/me.jpg">
|
||||
</center>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</body>
|
||||
|
|
@ -0,0 +1,22 @@
|
|||
#!/usr/local/bin/perl -w
|
||||
#
|
||||
use strict;
|
||||
use warnings;
|
||||
|
||||
my $html = qq{Content-Type: text/html
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<title>Dataforge UUCP</title>
|
||||
</head>
|
||||
<body>
|
||||
<center>
|
||||
<h1>
|
||||
Stay tuned...
|
||||
</h1>
|
||||
</center>
|
||||
</body>
|
||||
</html>
|
||||
};
|
||||
|
||||
print $html;;
|
||||
|
|
@ -0,0 +1,93 @@
|
|||
@import url('https://fonts.googleapis.com/css?family=Open+Sans+Condensed:300');
|
||||
@import url('https://fonts.googleapis.com/css?family=Raleway');
|
||||
|
||||
body {
|
||||
background-color: black;
|
||||
color: white;
|
||||
font-family: "Raleway", sans-serif;
|
||||
}
|
||||
|
||||
#container {
|
||||
width: 100%;
|
||||
margin-left: 18%;
|
||||
margin-right: -20%;
|
||||
position: absolute;
|
||||
}
|
||||
|
||||
h1 {
|
||||
font-family: 'Open Sans Condensed', sans-serif;
|
||||
}
|
||||
|
||||
a:active {
|
||||
color: white;
|
||||
}
|
||||
|
||||
a:visited {
|
||||
color: white;
|
||||
}
|
||||
|
||||
a:link {
|
||||
color:white;
|
||||
}
|
||||
|
||||
a:hover {
|
||||
color: green;
|
||||
}
|
||||
|
||||
table {
|
||||
width: 100%;
|
||||
}
|
||||
th, td {
|
||||
border: 1px solid white;
|
||||
border-collapse: collapse;
|
||||
}
|
||||
|
||||
#content {
|
||||
border-color: green;
|
||||
border-style: solid;
|
||||
border-width: 1px 1px 1px 1px;
|
||||
padding: 10px 10px 10px 10px;
|
||||
position: absolute;
|
||||
left: 208px;
|
||||
top: 103px;
|
||||
width: 806px;
|
||||
}
|
||||
|
||||
h3.creedo {
|
||||
font-family: "Raleway", sans-serif;
|
||||
padding-left: 20px;
|
||||
}
|
||||
|
||||
p.intro {
|
||||
padding-left: 10px;
|
||||
}
|
||||
|
||||
#header {
|
||||
border-color: green;
|
||||
border-style: solid;
|
||||
width: 1024px;
|
||||
border-width: 1px 1px 1px 1px;
|
||||
padding: 5px 5px 5px 5px;
|
||||
}
|
||||
|
||||
#nav {
|
||||
border-color: green;
|
||||
border-style: solid;
|
||||
border-width: 1px 1px 1px 1px;
|
||||
width: 200px;
|
||||
height: 400px;
|
||||
position: relative;
|
||||
top: 5px;
|
||||
|
||||
}
|
||||
|
||||
ul.menu {
|
||||
font-family: 'Open Sans Condensed','sans-serif';
|
||||
font-size: 28px;
|
||||
list-style-type: none;
|
||||
}
|
||||
|
||||
hr.join{
|
||||
width: 100px;
|
||||
color: green;
|
||||
}
|
||||
|
|
@ -0,0 +1,83 @@
|
|||
<!DOCTYPE html>
|
||||
|
||||
<head>
|
||||
<title>Dataforge UUCP</title>
|
||||
<link rel="stylesheet" href="css/main.css" type="text/css">
|
||||
</head>
|
||||
<body>
|
||||
<div id="container">
|
||||
<div id="header">
|
||||
<h1>Dataforge UUCP</h1>
|
||||
</div>
|
||||
<div id="nav">
|
||||
<ul class="menu">
|
||||
<li><a href="about.html">About Dataforge</a></li>
|
||||
<li><a href="manifesto.html">UUCP Manifesto</a></li>
|
||||
<li><a href="sites.html">Network Sites</a></li>
|
||||
<li><a href="http://uucp.dataforge.tk/~uucp/wiki/">Wiki</a><li>
|
||||
<li><div style="color: green"><a href="faq.html">FAQ</a></div></li>
|
||||
</ul>
|
||||
<center>
|
||||
<hr class="join">
|
||||
<h3><a href="join.html">Join Us!</a></h3>
|
||||
</center>
|
||||
</div>
|
||||
<div id="content">
|
||||
<h3>Frequently Asked Questions</h3>
|
||||
<b><i><u>Why UUCP?</u></i></b>
|
||||
<br>
|
||||
UUCP has a great many virtues not found in other technologies such as rsync or scp. Transmission is asynchronous due to the
|
||||
bidirectional nature of links between UUCP sites. If changes are made on one site, those changes are replicated to participating
|
||||
sites with no intervention by an administrator. Additionally, sending data to remote systems does not require the sending system
|
||||
to know anything about the receiving end or network topology. Only a bang path is needed for transmission. Transmissions are done in batches, which makes
|
||||
the protocol very efficient over unreliable or slow links (ie; dial-up, satellite, 3G, etc). UUCP also merges diffs between files with
|
||||
no intervention, which makes it useful for distributing items such as news where others may frequently modify items. Unlike rsync or
|
||||
scp, there is no need for a central authority. Which makes UUCP truly distributed and decentralized.
|
||||
<br>
|
||||
<br>
|
||||
<b><i><u>Is UUCP secure?</u></i></b>
|
||||
<br>
|
||||
Modern implementations of UUCP, such as Taylor UUCP, are very secure. On this UUCP network, transmissions are delivered over SSH,
|
||||
however, given the link agnosticism of UUCP, it could easily be sent over SSL or TLS. Authentication to the network occurs twice.
|
||||
First by SSH key exchange, and second by UUCP authentication. Additionally, each piece of data sent across the wire is GPG signed
|
||||
for integrity and proof of ownership. Since there is only one point of entry into the network, that greatly decreases its risk spread.
|
||||
Users can do whatever they please and the rest of the network won't be compromised. Additionally, UUCP is very verbose with its logging,
|
||||
which makes the protocol easily auditable.
|
||||
<br>
|
||||
<br>
|
||||
<b><i><u>Why doesn't this have a proper name?</u></i></b>
|
||||
<br>
|
||||
Following past traditions of UUCP networks, the network at large has no real name. A name implies ownership, and nobody <i>owns</i> the network. Individual site
|
||||
networks are free to have a proper name, but the larger network doesn't. Just as the Internet doesn't have a real name.
|
||||
<br>
|
||||
<br>
|
||||
<b><i><u>Is this just a Linux thing?</u></i></b>
|
||||
<br>
|
||||
NO! WHile the named Unix-to-Unix Copy suggests being a *nix only techology, implementations exists for non-unix systems, such as VMS,
|
||||
OS/2, z/OS, Windows and others. The UUCP code base is very portable and can be ran on a variety of operating systems and architectures.
|
||||
Everything from a PDP-11 to a giant mainframe.
|
||||
<br>
|
||||
<br>
|
||||
<b><i><u>Can anyone join?</u></i></b>
|
||||
<br>
|
||||
YES! :D While having your own UUCP presense is not required, if you are an end-user, you can peer with any number of Tier 1 hosts.
|
||||
Tier 1 status is reserved for dedicated points-of-presents (see <a href="tier1.html">Tier 1</a> article)
|
||||
<br>
|
||||
<br>
|
||||
<b><i><u>It's link agnostic? Can I run it over tin cans and string?</u></i></b>
|
||||
<br>
|
||||
You can peer with another UUCP site using any means of communication you wish. Whether that is a ham link, 3G, satellite, or
|
||||
even dialup. UUCP does not care about the medium in which it uses.
|
||||
<br>
|
||||
<br>
|
||||
<b><i><u>What happens if I try to lick it?</u></i></b>
|
||||
<br>
|
||||
You'll feel a beautiful euphoria not previously known to man
|
||||
<br>
|
||||
<br>
|
||||
<b><i><u>How do I join?</u></i></b>
|
||||
<br>
|
||||
Simply go to the join page and follow it's instructions. Select whether you wish to be a Tier 1 server, or a leaf node.
|
||||
</div>
|
||||
</div>
|
||||
</body>
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
|
After Width: | Height: | Size: 39 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 22 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 263 KiB |
|
|
@ -0,0 +1,64 @@
|
|||
<!DOCTYPE html>
|
||||
|
||||
<head>
|
||||
<title>Dataforge UUCP</title>
|
||||
<link rel="stylesheet" href="css/main.css" type="text/css">
|
||||
</head>
|
||||
<body>
|
||||
<div id="container">
|
||||
<div id="header">
|
||||
<h1>Dataforge UUCP</h1>
|
||||
</div>
|
||||
<div id="nav">
|
||||
<ul class="menu">
|
||||
<li><a href="about.html">About Dataforge</a></li>
|
||||
<li><a href="manifesto.html">UUCP Manifesto</a></li>
|
||||
<li><a href="sites.html">Network Sites</a></li>
|
||||
<li><a href="http://uucp.dataforge.tk/~uucp/wiki/">Wiki</a><li>
|
||||
<li><a href="faq.html">FAQ</a></li>
|
||||
</ul>
|
||||
<center>
|
||||
<hr class="join">
|
||||
<h3><a href="join.html">Join Us!</a></h3>
|
||||
</center>
|
||||
</div>
|
||||
<div id="content">
|
||||
<p>
|
||||
<h3 class="creedo">
|
||||
<i>
|
||||
"Bringing back the distributed Internet for artists, hackers, nerds, retro geeks, and justice warriors. A time before
|
||||
the existence of a few powerful 'cloud' providers and encroaching government entities"
|
||||
</i>
|
||||
</h3>
|
||||
</p>
|
||||
<p class="intro">
|
||||
Who is the network for?
|
||||
<ul>
|
||||
<li>Shell providers</li>
|
||||
<li>Tilde networks</li>
|
||||
<li>Retro groups</li>
|
||||
<li>Makerspaces</li>
|
||||
<li>BBS operators</li>
|
||||
<li>Freedom fighters</li>
|
||||
</ul>
|
||||
<br>
|
||||
<br>
|
||||
What can you use it for?
|
||||
<ul>
|
||||
<li>Send encrypted e-mail on the fly</li>
|
||||
<li>User-to-user data, even if they're not on the same system</li>
|
||||
<li>Distribute files across disparate sites transparently</li>
|
||||
<li>Execute commands remotely</li>
|
||||
<li>Distribute news using NNTP or flat files, or SQLite database. Network don't care...</li>
|
||||
</ul>
|
||||
<br>
|
||||
<br>
|
||||
<center>Data links provided via SSH or dialup. Secure from the start.</center>
|
||||
<br>
|
||||
<br>
|
||||
As seen on <a href="https://boingboing.net/2019/03/25/tilde-servers-r-us.html">Boing Boing</a> and <a href="https://news.ycombinator.com/item?id=19476323">
|
||||
Hacker News</a>. WELCOME :D
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</body>
|
||||
|
|
@ -0,0 +1,75 @@
|
|||
<!DOCTYPE html>
|
||||
|
||||
<head>
|
||||
<title>Dataforge UUCP</title>
|
||||
<link rel="stylesheet" href="css/main.css" type="text/css">
|
||||
</head>
|
||||
<body>
|
||||
<div id="container">
|
||||
<div id="header">
|
||||
<h1>Dataforge UUCP</h1>
|
||||
</div>
|
||||
<div id="nav">
|
||||
<ul class="menu">
|
||||
<li><a href="about.html">About Dataforge</a></li>
|
||||
<li><a href="manifesto.html">UUCP Manifesto</a></li>
|
||||
<li><a href="sites.html">Network Sites</a></li>
|
||||
<li><a href="http://uucp.dataforge.tk/~uucp/wiki/">Wiki</a><li>
|
||||
<li><a href="faq.html">FAQ</a></li>
|
||||
</ul>
|
||||
<center>
|
||||
<hr class="join">
|
||||
<div style="color: green"><h3>Join Us!</h3></div>
|
||||
</center>
|
||||
</div>
|
||||
<div id="content">
|
||||
So we have you convinced and you want to join in the fun!? YAY!! :D
|
||||
<br>
|
||||
Here is a happy dancing panda to celebrate!
|
||||
<br>
|
||||
<br>
|
||||
<center>
|
||||
<img src="img/panda.gif" width=250 height=250>
|
||||
</center>
|
||||
<br>
|
||||
<br>
|
||||
<center>First...a <marquee><div style="color: red">WARNING!</div></marquee></center>
|
||||
<br>
|
||||
While praetor has spent a while designing the network adequately, spent weeks testing, and tested all this internally, it is not without
|
||||
it's experimentation (which is good! We want that). While setup is easy, and maintaining a site is virtually adminless. It is not without
|
||||
it's quirks. If you want to be apart of something cool, different, and ripe for tinkering....read on.
|
||||
<br>
|
||||
<br>
|
||||
<ol>
|
||||
<li>
|
||||
Decide if you want to be a Tier 1 system or a leaf node.
|
||||
Reading the <a href="http://uucp.dataforge.tk/~uucp/wiki/index.php?n=Main.NetworkTopology">Network Topology</a>
|
||||
wiki article can help you choose. Please be aware being a Tier 1 site requires some dedication.
|
||||
</li>
|
||||
<br>
|
||||
<li>
|
||||
If you wish to be a leaf node, you will need to e-mail a Tier 1 site admin of your choosing, and provide them with a name
|
||||
for your site, location, end-point address, and ssh public key. Please note, you can only be peered to ONE Tier 1 host, however,
|
||||
you may have as many hosts peered with YOU as you wish. Peering with more than one Tier 1 host will result in a slap of the wrist. It's
|
||||
currently is not supported, and we will find out. However, if you have an exotic use case and require that, please petition an admin.
|
||||
</li>
|
||||
<br>
|
||||
<li>
|
||||
Please be patient for your credentials to be processed. Currently this process is not automated, but eventually will be. You will
|
||||
receive an e-mail with your UUCP credentials as well as the public key of the Tier 1 server, which you will need to put in your
|
||||
UUCP user's ~/.ssh/authorized_keys file.
|
||||
</li>
|
||||
<br>
|
||||
<li>
|
||||
Read the <a href="http://uucp.dataforge.tk/~uucp/wiki/index.php?n=Main.LeafNode">Leaf Node Setup Guide</a> to set up your site.
|
||||
If you've been approved to be a Tier 1 system, you will need to follow the
|
||||
<a href="http://uucp.dataforge.tk/~uucp/wiki/index.php?n=Main.Tier1">Tier 1 Setup Guide</a>
|
||||
</li>
|
||||
<br>
|
||||
<li>
|
||||
Enjoy and also join us on tilde.chat in the #UUCP room!
|
||||
</li>
|
||||
</ol>
|
||||
</div>
|
||||
</div>
|
||||
</body>
|
||||
|
|
@ -0,0 +1,65 @@
|
|||
<!DOCTYPE html>
|
||||
|
||||
<head>
|
||||
<title>Dataforge UUCP</title>
|
||||
<link rel="stylesheet" href="css/main.css" type="text/css">
|
||||
</head>
|
||||
<body>
|
||||
<div id="container">
|
||||
<div id="header">
|
||||
<h1>Dataforge UUCP</h1>
|
||||
</div>
|
||||
<div id="nav">
|
||||
<ul class="menu">
|
||||
<li><a href="about.html">About Dataforge</a></li>
|
||||
<div style="color: green"><li>UUCP Manifesto</li></div>
|
||||
<li><a href="sites.html">Network Sites</a></li>
|
||||
<li><a href="http://uucp.dataforge.tk/~uucp/wiki/">Wiki</a><li>
|
||||
<li><a href="faq.html">FAQ</a></li>
|
||||
</ul>
|
||||
<center>
|
||||
<hr class="join">
|
||||
<h3><a href="join.html">Join Us!</a></h3>
|
||||
</center>
|
||||
</div>
|
||||
<div id="content">
|
||||
<h3>UUCP Manifesto</h3>
|
||||
<p>
|
||||
We live in an age of increasing centralization and regulation of the Internet. Major swatches of the global's IP infrastructure
|
||||
now rests in the hands of major Internet properties such as Amazon, Google, Facebook and Apple. In addition, intrusive government
|
||||
policing is becoming prevalent, lack of privacy and increasing mis-use of data by marketing firms runs rampant. This runs contrary
|
||||
to the original idea and ethos of the internet, that ironically, was designed by the Department of Defense. Resilience,
|
||||
decentraliation and freedom are slowly becoming echoes of nostalgia.
|
||||
</p>
|
||||
<p>
|
||||
In response to this growing bastardization of IP infrastructure; groups, nerds and hackers have created independent communities
|
||||
based on privacy, decentralization of authority, and mututal respect for all people. Services such as shell providers, BBSes, and
|
||||
Tilde networks have become a new rennasaice of technical thought. A forum on the forum that is no more.
|
||||
</p>
|
||||
<p>
|
||||
In the formative days of the Internet, systems and sites were loosely linked over a protocol called UUCP (Unix-to-Unix Copy).
|
||||
Dedicated connections, such that have become common place now, were prohibitvely expensive. In response to this, universities and
|
||||
government research institutions formulated the UUCP network - a loosely coupled network of dial-up systems which relayed information
|
||||
across the network. Similar to Olympic torch relays. News, mail, files and a mulitude of services were provided by the UUCP network.
|
||||
In the early days of the Internet, a service known as Usenet was also carried across UUCP links and was in active service into the 2000s.
|
||||
As dedicated links have become more pervasive and affordable, the UUCP network slowly went away and faded to obscurity. While the UUCP
|
||||
protocol was designed from the ground up as a robust protocol ideal for communication over slow and unreliable data links with a great many
|
||||
virtues, it has been relegated to only the most obscure of legacy systems.
|
||||
</p>
|
||||
<p>
|
||||
Until now.
|
||||
</p>
|
||||
<p>
|
||||
We are a dedicated group of artists, system operators, nerds, geeks, nostalgics of every walk of life who desire a fully decentralized
|
||||
internet in the vein of the UUCP networks of yore. In this way, we have revived the network protocol adding modern essentials such
|
||||
encryption, permissions, better integration with dedicated links. While also keeping it's virtues of transparency, ease of implementation
|
||||
and resiliency. We also return to a place of mutual respect and understanding, freedom for all people who utilize it. Nobody "owns" it.
|
||||
It's everybody's to use, tinker with, contribte to and have equal say and access to its content and resources without fear of reprisal,
|
||||
condemnation or censorship.
|
||||
</p>
|
||||
<p>
|
||||
It is a return to a network for everybody, everywhere.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</body>
|
||||
|
|
@ -0,0 +1,117 @@
|
|||
<!DOCTYPE html>
|
||||
|
||||
<head>
|
||||
<title>Dataforge UUCP</title>
|
||||
<link rel="stylesheet" href="css/main.css" type="text/css">
|
||||
</head>
|
||||
<body>
|
||||
<div id="container">
|
||||
<div id="header">
|
||||
<h1>Dataforge UUCP</h1>
|
||||
</div>
|
||||
<div id="nav">
|
||||
<ul class="menu">
|
||||
<li><a href="about.html">About Dataforge</a></li>
|
||||
<li><a href="manifesto.html">UUCP Manifesto</a></li>
|
||||
<div style="color: green"><li>Network Sites</li></div>
|
||||
<li><a href="http://uucp.dataforge.tk/~uucp/wiki/">Wiki</a><li>
|
||||
<li><a href="faq.html">FAQ</a></li>
|
||||
</ul>
|
||||
<center>
|
||||
<hr class="join">
|
||||
<h3><a href="join.html">Join Us!</a></h3>
|
||||
</center>
|
||||
</div>
|
||||
<div id="content">
|
||||
<a href="tier1.html"><h3>Tier 1</h3></a>
|
||||
<table>
|
||||
<tr>
|
||||
<th>Organization</th>
|
||||
<th>Location</th>
|
||||
<th>Endpoint</th>
|
||||
<th>Bang Path</th>
|
||||
<th>Accepting Peers</th>
|
||||
<th>IPv6</th>
|
||||
<th>Dialup</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Dataforge</td>
|
||||
<td>Fort Worth, TX (US)</td>
|
||||
<td>uucp.dataforge.tk</td>
|
||||
<td>dataforge!</td>
|
||||
<td>Yes</td>
|
||||
<td>Yes</td>
|
||||
<td>Not yet</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Tilde Team</td>
|
||||
<td>Michigan, US</td>
|
||||
<td>tilde.team</td>
|
||||
<td>team!</td>
|
||||
<td>Yes</td>
|
||||
<td>Yes</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="http://cosmic.voyage">Cosmic Voyage</a></td>
|
||||
<td>Somewhere</td>
|
||||
<td>cosmic.voyage</td>
|
||||
<td>voyage!</td>
|
||||
<td>Space ships!</td>
|
||||
<td>No</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Tilde Center</td>
|
||||
<td>Dallas, TX</td>
|
||||
<td>tilde.center</td>
|
||||
<td>center!</td>
|
||||
<td>Yes</td>
|
||||
<td>Yes</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="http://frostbyte.cc">Frostbyte</a></td>
|
||||
<<td>Chicago, IL </td>
|
||||
<td>uucp.frostbyte.cc</td>
|
||||
<td>frostbyte!</td>
|
||||
<td>Yes</td>
|
||||
<td>Np</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="https://aussies.space">aussies.space</a></td>
|
||||
<td>Australia</td>
|
||||
<td>aussies.space</td>
|
||||
<td>aussies!</td>
|
||||
<td>Yes</td>
|
||||
<td>Np</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
<br>
|
||||
<h3>Leaf Sites Serviced By Dataforge</h3>
|
||||
<table>
|
||||
<tr>
|
||||
<th>Name</th>
|
||||
<th>Location</th>
|
||||
<th>Bang Path</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Dataforge-1</td>
|
||||
<td>Fort Worth, TX</td>
|
||||
<td>dataforge!dataforge1</td>
|
||||
<td>Running on a real Silicon Graphics O2</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>shiva</td>
|
||||
<td>Netherlands</td>
|
||||
<td>dataforge!shiva</td>
|
||||
<td>shiva.uucp.dataforge.tk</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
<body>
|
||||
|
|
@ -0,0 +1,61 @@
|
|||
<!DOCTYPE html>
|
||||
|
||||
<head>
|
||||
<title>Dataforge UUCP</title>
|
||||
<link rel="stylesheet" href="css/main.css" type="text/css">
|
||||
</head>
|
||||
<body>
|
||||
<div id="container">
|
||||
<div id="header">
|
||||
<h1>Dataforge UUCP</h1>
|
||||
</div>
|
||||
<div id="nav">
|
||||
<ul class="menu">
|
||||
<li><a href="about.html">About Dataforge</a></li>
|
||||
<li><a href="manifesto.html">UUCP Manifesto</a></li>
|
||||
<div style="color: green"><li>Network Sites</li></div>
|
||||
<li><a href="http://uucp.dataforge.tk/~uucp/wiki/">Wiki</a><li>
|
||||
<li>FAQ</li>
|
||||
</ul>
|
||||
<center>
|
||||
<hr class="join">
|
||||
<h3><a href="join.html">Join Us!</a></h3>
|
||||
</center>
|
||||
</div>
|
||||
<div id="content">
|
||||
<h3>Tier 1</h3>
|
||||
<p>
|
||||
Tier 1 sites are decentralized, mesh connected, top-level hosts. These are primarily run by a committee of
|
||||
shell providers and tilde networks. Tier 1 servers are considered the backbone of the UUCP network. However,
|
||||
if a member organization chooses not to particpate, it doesn't unilaterally affect the tolerance of the network
|
||||
as a whole.
|
||||
<p>
|
||||
In order to become a Tier 1 site, it must have the following qualifications:
|
||||
<ul>
|
||||
<li>Dedicated IP infrastructure</li>
|
||||
<li>Reliable server hosting</li>
|
||||
<li>Not be part of a commercial organization</li>
|
||||
<li>Be willing and active participant in the UUCP steering comittee</li>
|
||||
</ul>
|
||||
</p>
|
||||
<p>
|
||||
While the UUCP network is for everyone, including those in the retro scene, running a Tier 1 UUCP site from a retro machine is
|
||||
discouraged. However, there are leaf sites running on retro hardware.
|
||||
</p>
|
||||
<p>
|
||||
While the aim of the UUCP network is to democratize and decentralize it's services, nothing precludes a member from running its
|
||||
Tier 1 site on a cloud based provider, so long as that provider does not receive any monetized benefits for hosting it. Requesting
|
||||
donations from users to maintain services, however, is perfectly fine.
|
||||
</p>
|
||||
<p>
|
||||
Current charter and commitee members are:
|
||||
<ul>
|
||||
<li><a href="http://www.dataforge.tk/">Dataforge (*)(+)</a></li>
|
||||
<li><a href="http://tilde.team">Tilde.Team (*)(+)</a></li>
|
||||
</ul>
|
||||
<h5>(*) Denotes Charter Member (+) Denotes comittee member</h5>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
<body>
|
||||
Loading…
Reference in New Issue