Skip to content

Commit 2beb83b

Browse files
author
sam bacha
authored
Create behind_the_name.md
1 parent c4bb0bc commit 2beb83b

File tree

1 file changed

+62
-0
lines changed

1 file changed

+62
-0
lines changed

content/posts/behind_the_name.md

Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
aliases = ["dogma","informative","blog","showcase","about"]
2+
title = "Origin behind the name, `Backbone Cabal`"
3+
author = "YCabal Contibutors"
4+
tags = ["index"]
5+
6+
Backbone Cabal takes its name from an effort to facilitate the reliable propagation of
7+
new Usenet posts. While in the 1970s and 1980s many news servers only
8+
operated during night time to save on the cost of long distance
9+
communication, servers of the backbone cabal were available 24 hours a
10+
day.
11+
12+
That is our modern day mission: to faciliate the reliable propagation of
13+
blockchain transactions (ethereum, etc), and to ensure sufficient decentralization
14+
of these services.
15+
16+
Here is an article explaining the original, `Backbone Cabal`
17+
18+
19+
After its humble birth in 1979, Usenet flourished at a surprising rate,
20+
leading to various problems and headaches for its developers and users.
21+
In an attempt to establish collaboration between Usenet site
22+
administrators to more easily resolve these issues, Mark Horton
23+
organized a list of large Usenet sites and the contact information for
24+
their administrators. That list would remain dormant for a few years
25+
until Gene Spafford became a Usenet administrator at Georgia Tech. He
26+
took Horton's list of hosts and facilitated conversations between their
27+
operators. This group would become the Backbone Cabal. Horton is
28+
considered the organizer of the 'physical' backbone Cabal, while
29+
Spafford established the 'political' Cabal.
30+
31+
When asked about the impetus behind the organization of the political
32+
aspect of the Cabal, Gene Spafford detailed:
33+
34+
"When I took over the administration of Usenet on the Georgia Tech
35+
machines in about 1983, I noted that it took a long time for some
36+
articles to propagate, and often discussion threads got all out of order
37+
for many of us who were trying to follow many subthreads. So, I looked
38+
at the "map" of connections that Mark had put together. This was in the
39+
early 1980s, and Mark's original "backbone" was in it. I identified a
40+
set of about 10 machines that had high capacity links, many subfeeds,
41+
and seemed to be maintained by clueful people. I contacted them one at a
42+
time and suggested cross linking that they might establish to reduce
43+
latency and increase redundancy. Most agreed. We ended up with a pretty
44+
robust "core" which was the new backbone."
45+
46+
Issues that Cabal members commonly addressed included approving new
47+
newsgroups, managing article propagation, and otherwise attending to the
48+
administrative needs of the rapidly growing network.
49+
50+
The Backbone Cabal played a large part in The Great Renaming which
51+
created the hierarchy and naming structure that is still used to create
52+
and organize Usenet newsgroups today. This reorganization was made
53+
possible by the influence that the Cabal had earned amongst the Usenet
54+
community, but, ironically, the voting system that was implemented with
55+
the Great Renaming resulted in the lessening of the Cabal's power.
56+
57+
Though rumors of the Cabal's activity survived into the late 1990s, it
58+
is generally agreed that the Cabal's active years ended in 1993 when
59+
Gene Spafford withdrew from his Usenet duties and moved on to new
60+
projects.
61+
62+
source: https://www.giganews.com/usenet-history/cabal.html

0 commit comments

Comments
 (0)