Updates to about page
This commit is contained in:
Deon George
parent
34f289953d
commit
edd41ad187
36
public/css/fixes.css
vendored
36
public/css/fixes.css
vendored
@ -16,4 +16,40 @@
|
||||
.input-group .form-select {
|
||||
border-top-right-radius: 4px !important;
|
||||
border-bottom-right-radius: 4px !important;
|
||||
}
|
||||
|
||||
/* Using OL instead of UL */
|
||||
ol {
|
||||
text-align: left;
|
||||
}
|
||||
|
||||
#content ol {
|
||||
margin: 0 1ch;
|
||||
padding-left: 1ch;
|
||||
list-style-type: none;
|
||||
}
|
||||
|
||||
#content ol:not(.pagination) li {
|
||||
margin: 0 1ch;
|
||||
text-indent: -3ch;
|
||||
padding-left: 3ch;
|
||||
display: block;
|
||||
counter-increment: count-me;
|
||||
}
|
||||
|
||||
#content ol:not(.pagination) li::before {
|
||||
content: counter(count-me) ") ";
|
||||
color: #0a0;
|
||||
}
|
||||
|
||||
#content ol li:last-child {
|
||||
margin-bottom: 16px;
|
||||
}
|
||||
|
||||
/* Fix h5 which is 25% larger than h4 */
|
||||
#content h4:not(.alert-heading) {
|
||||
color: #c60;
|
||||
}
|
||||
#content h5:not(.alert-heading) {
|
||||
font-size: 0.9rem;
|
||||
}
|
||||
@ -4,54 +4,59 @@
|
||||
@endsection
|
||||
|
||||
@section('content')
|
||||
<h2>About the FTN Clearing House</h2>
|
||||
<h2>About the FTN Clearing Houz</h2>
|
||||
|
||||
<p>Welcome to the FTN Clearing House.</p>
|
||||
<p>Welcome to the <strong class="highlight">FTN Clearing Houz</strong>.</p>
|
||||
|
||||
<div class="float-end ps-3 pb-3" id="network_traffic"></div>
|
||||
<p>The FTN Clearing House (FCH) is both a FTN Mailer and FTN message tosser, where mail is stored internally in a DB. FCH can also hatch and toss files into FTN networks for both up/downstream nodes.</p>
|
||||
<p>It was created as an idea to bring modern technology and capabilities to a legacy computing network that existed in the 1970's, 1980's and 1990's (before the Internet basically).</p>
|
||||
<p>FTN is an abbreviation for FidoNet Technology Network, and the most well known FTN is "<a href="https://wikipedia.org/wiki/FidoNet">FidoNet</a>" that still exists today.
|
||||
There were many other "Othernets" also created around that time and since, and some still in operation today as well.</p>
|
||||
<p>FidoNet was born in the 1980's (well before the public Internet) when personal computers were being introduced to homes, and modems were being invented.
|
||||
Some very clever people developed protocols and standards to exchange mail and files with peers, with the network growing to around 40,000 systems in the mid 1990's.
|
||||
Those systems were called BBSes or <a href="https://wikipedia.org/wiki/Bulletin_board_system">Bulletin Board Systems</a>.
|
||||
As "the Internet" became more accessible, the usage of FidoNet and BBSes drastically reduced, but there are some systems still in operation today.</p>
|
||||
<p>The <strong class="highlight">FTN Clearing Houz</strong> is both an FTN Mailer and FTN message tosser, where mail is stored internally in a DB, and files in an S3 bucket. It can also hatch and toss files into FTN networks for both upstream and downstream nodes.</p>
|
||||
<p>It was created as an idea to bring modern technology and capabilities to that legacy computing network that existed in the 1980's and 1990's, where many of those programs from the 1980's and 1990's are still in use today too.</p>
|
||||
|
||||
<p>Setting up a BBS is fun, but using a BBS for the long term, in amongst our busy lives can involve some repetitive tasks.
|
||||
<p>Setting up an FTN network is fun, but managing one for the longer term, in amongst our busy lives can involve some tedious repetitive tasks.
|
||||
In the same vain, maintaining and growing an FTN network also can be time consuming, especially when your effort (or lack thereof) can affect the experience of your users.
|
||||
So FCH was created to help address that.
|
||||
</p>
|
||||
So FTN Clearing Houz was created to help address that.</p>
|
||||
|
||||
<p>Building this software is driven by three main goals:</p>
|
||||
<ul>
|
||||
<li>Self Service - so that users can setup and re-jig their configuration themselves, or new users can join a network with the minimum of effort.</li>
|
||||
<li>Automation - so that repetitive tasks can be done with minimal effort</li>
|
||||
<ol>
|
||||
<li>Self Service - so that users can setup and re-jig their configuration themselves, or new users can join a network with the minimum of effort (relieving a dependancy on an admin to set you up, and thus freeing up time for those admins).</li>
|
||||
<li>Automation - so that repetitive tasks can be done with minimal effort.</li>
|
||||
<li>High Availability - So if one hub goes down, users can automatically connect to an alternate hub to keep mail flowing. Furthermore, as hubs retire, new hubs can assume the role of the retiring hub with minimal effort.</li>
|
||||
</ul>
|
||||
</ol>
|
||||
|
||||
<p>So that you can spend your time playing on your BBS rather than managing messages, failures or keeping an FTN network running.</p>
|
||||
<p>...all so that you can spend your time playing on your BBS rather than managing messages, failures or keeping an FTN network running.</p>
|
||||
|
||||
<h3>For the BBS Sysop</h3>
|
||||
<p>For the BBS sysop, the FTN Clearing House has the following features (or planned ones):</p>
|
||||
<p>For the BBS sysop, the FTN Clearing Houz has the following features:</p>
|
||||
<ul>
|
||||
<li>Supports BINKP network transfers</li>
|
||||
<li>Supports EMSI network transfers</li>
|
||||
<li>Supports PING responses</li>
|
||||
<li>A consistent reliable echomail/netmail hub for your BBSes.<br>
|
||||
If you have more than 1 BBS, then the Clearing House can receive all your mail from your uplinks and feed them to your BBSes.
|
||||
<li>Supports EMSI network transfers (for legacy "frontend" mailers)</li>
|
||||
<li>Supports PING responses (to netmails)</li>
|
||||
<li>A consistent reliable echomail/netmail hub for your BBSes, while you reconfigure your BBS.<br>
|
||||
If you have more than 1 BBS, then the Clearing Houz can receive all your mail from your uplinks and feed them to your BBSes.
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h3>For the FTN network operator</h3>
|
||||
<p>For the FTN network operator, the FTN Clearing House has the following features (or planned ones):</p>
|
||||
<p>For the FTN network operator, the FTN Clearing Houz has the following features (or planned ones):</p>
|
||||
<ul>
|
||||
<li>Supports BINKP network transfers</li>
|
||||
<li>Supports EMSI network transfers</li>
|
||||
<li>Automatic route configuration</li>
|
||||
<li>Manages ECHO areas and FILE areas <sup>To be implemented</sup></li>
|
||||
<li>Supports PING and TRACE responses <sup>To be implemented</sup></li>
|
||||
<li>Nodelist Management <sup>To be implemented</sup></li>
|
||||
<li>Network Applications <sup>To be implemented</sup></li>
|
||||
<li>Dynamic mail bundling for upstream and downstream nodes</li>
|
||||
<li>Automatic delisting of idle nodes <sup>To be implemented</sup></li>
|
||||
<li>Automatic route configuration, routing netmail directly where links exist, or to the next uplink/downlink</li>
|
||||
<li>Manages ECHO areas and FILE areas</li>
|
||||
<li>Supports PING and TRACE responses <sup>(TRACE to be implemented)</sup></li>
|
||||
<li>Nodelist Management</li>
|
||||
<li>Self service FTN Network Applications <sup>being implemented</sup></li>
|
||||
<li>Dynamic mail bundling for upstream and downstream nodes (no more "inbounds" and "outbounds")</li>
|
||||
<li>Automatic delisting of idle nodes</li>
|
||||
</ul>
|
||||
|
||||
<h5>Other things</h5>
|
||||
<h4>Other things</h4>
|
||||
<p>Other ideas that may make it into this tool:</p>
|
||||
<ul>
|
||||
<li>SMTP integration</li>
|
||||
@ -59,23 +64,25 @@ If you have more than 1 BBS, then the Clearing House can receive all your mail f
|
||||
<li>SQRL simple authentication <small>(so there is 1 less username/password you need to remember)</small></li>
|
||||
</ul>
|
||||
|
||||
<p>To get started, please <a href="{{ url('login') }}">login</a>.</p>
|
||||
<p>If you are here to link to BBS, please get started by <a href="{{ url('login') }}">logging in</a>.</p>
|
||||
|
||||
<h4>Open Source</h4>
|
||||
<p>FTN Clearing House is built with Open Source software. At it's core, PHP drives this web UI and the interaction with nodes.</p>
|
||||
<p>This web UI has been inspired by the great work at <a href="https://int10h.org">int10h.org</a>. If you have ideas to make it even better, please send me a message, or submit your comments in <a href="https://dev.leenooks.net/bbs/clrghouz">gitlab</a></p>
|
||||
<h2>Open Source</h2>
|
||||
<p>FTN Clearing Houz is built with Open Source software. At it's core, PHP drives this web UI and the interaction with nodes.</p>
|
||||
<p>This web UI has been inspired by the great work at <a href="https://int10h.org">int10h.org</a>. If you have ideas to make it even better, please send me a message, or submit your comments in <a href="https://dev.dege.au/bbs/clrghouz">gitlab</a></p>
|
||||
|
||||
<h4>Other technology that drives the Clearing Houz</h4>
|
||||
<p>FCH is made availabe by these technologies:</p>
|
||||
<h3>Other technology that drives the Clearing Houz</h3>
|
||||
<p>FTN Clearing Houz is made available by these technologies:</p>
|
||||
<ul>
|
||||
<li>Docker - taking the effort out of building, deploying and easing the effort of upgrading.</li>
|
||||
<li>CockroachDB - a high available, geodispersable database, that enables accessing configuration and data from multiple locations. CockroachDB enables the FCH to appear as the same hub from multiple locations, providing a high available environment for Sysops to drop off and collect mail</li>
|
||||
<li>Memcached - to take some of the pressure off CockroachDB</li>
|
||||
<li><strike>CockroachDB - a high available, geodispersable database, that enables accessing configuration and data from multiple locations. CockroachDB enables the FTN Clearing Houz to appear as the same hub from multiple locations, providing a high available environment for Sysops to drop off and collect mail</strike></li>
|
||||
<li>PostgreSQL - to store all the data
|
||||
<li>Memcached - to take some of the pressure off the database</li>
|
||||
<li>PHP/Laravel - the coding framework used to create this UI, and to enable the transfer of mail between systems</li>
|
||||
<li>jQuery - to help with the web UI</li>
|
||||
<li>Highcharts - to render the graphs</li>
|
||||
</ul>
|
||||
|
||||
<p>If you'd like to support enhancing Clearing Houz, <a href="https://buymeacoffee.com/dege">Buy me a coffee!</a></p>
|
||||
<span class="float-end"><strong class="highlight">clrghouz</strong> <small>[<strong class="gray">{{ gethostname() }}</strong>@if (File::exists('../VERSION')) @ <strong class="success">{{ chop(File::get('../VERSION')) }}</strong>@endif]</small></span>
|
||||
@endsection
|
||||
|
||||
|
||||
@ -1 +1 @@
|
||||
<a href="/" class="goback">{{ request()->getHost() }}</a> © {{ \Carbon\Carbon::now()->year }} Alterego
|
||||
<a href="/" class="goback">{{ request()->getHost() }}</a> © {{ \Carbon\Carbon::now()->year }} Deon George
|
||||
@ -4,7 +4,9 @@
|
||||
<ul id="navlist-desktop">
|
||||
<li><a href="{{ url($user ? 'dashboard' : '/') }}" class="@if(preg_match('#^/#',request()->path()))thispage @endif"><span>Home</span></a></li>
|
||||
<li><a href="{{ url('about') }}" class="@if(preg_match('#^about#',request()->path()))thispage @endif"><span>About</span></a></li>
|
||||
{{--
|
||||
<li><a href="{{ url('help') }}" class="@if(preg_match('#^help#',request()->path()))thispage @endif disabled"><span>Help</span></a></li>
|
||||
--}}
|
||||
@can('admin')
|
||||
<li><a href="{{ url('setup') }}" class="@if(preg_match('#^setup#',request()->path()))thispage @endif"><span>Setup</span></a></li>
|
||||
@endcan
|
||||
|
||||
Loading…
Reference in New Issue
Block a user