bbs/clrghouz
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Update our welcome page with feature updates and more information
All checks were successful
Create Docker Image / Build Docker Image (x86_64) (push) Successful in 40s
Details
Create Docker Image / Build Docker Image (arm64) (push) Successful in 1m38s
Details
Create Docker Image / Final Docker Image Manifest (push) Successful in 10s
Details

Browse Source
This commit is contained in:
Deon George 2024-12-14 18:43:28 +07:00
parent aa55d05ccb
commit 010f34f4f2
2 changed files with 19 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
public/robots.txt
View File

@ -1,2 +1,3 @@
User-agent: *
Disallow:
Allow: /about
Disallow: /

28
resources/views/about.blade.php
View File

@ -32,18 +32,24 @@
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 FTN Clearing Houz was created to help address that.</p>
<p>Building this software is driven by three main goals:</p>
<p>Building this software is driven by four main goals:</p>
<ol>
<li>Self Service - so that users can setup and re-jig their configuration themselves, or new users can join a
<li><strong class="highlight">Self Service</strong> - 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><strong class="highlight">Automation</strong> - so that repetitive tasks can be done with minimal effort.</li>
<li>
<strike>High Availability - So if one hub goes down, users can automatically connect to an alternate hub to keep
<span style="text-decoration: line-through;"><strong class="highlight">High Availability</strong> - 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.
</strike>
effort.</span> This goal was attempted with CockroachDB, but abandoned due to he resource requirements it required and latency that it introduced.
I welcome any ideas to help achieve this goal.
</li>
<li><strong class="highlight">Connectivity</strong> - with all the different types of connectivity options between the different BBS/Mailer types.
Clearing Houz currently supports BINKP and EMSI/ZModem mailer types, and 4 FTN packet types. If you have a BBS that uses
a unique packet type (eg: QWK or ?) or a unique transfer type (eg: NNTP or ?) and would like to get access to other messages
networks that use a different mailer/packet type, then let me know. I'll happily work on it to make a bridge
to open up access to things you cannot access.
</li>
</ol>
@ -77,7 +83,7 @@
<a href="http://ftsc.org/docs/fsc-0039.004">FSC-0039</a>,
<a href="http://ftsc.org/docs/fsc-0045.001">FSC-0045</a>,
<a href="http://ftsc.org/docs/fsc-0048.002">FSC-0048</a></li>
<li>Automatic delisting of idle nodes <sup>(to be implemented)</sup></li>
<li>Automatic delisting of idle nodes, including marking them HOLD, then DOWN</li>
<li>DNS server, to enable resolving of registered nodes using domain dns names <a href="http://ftsc.org/docs/fts-5004.001">FTS-5004</a>
with <strong class="highlight">p<em>N</em>.f<em>N</em>.n<em>N</em>.z<em>N</em>.<em>domain</em>.ftn</strong>, or
<strong class="highlight">p<em>N</em>.f<em>N</em>.n<em>N</em>.z<em>N</em>.<em>[domain dns zone]</em></strong>
@ -89,7 +95,7 @@
<ul>
<li>SMTP integration</li>
<li>PGP signed mail and mail verification</li>
<li>SQRL simple authentication <small>(so there is 1 less username/password you need to remember)</small></li>
<li><span style="text-decoration: line-through;">SQRL simple authentication <small>(so there is 1 less username/password you need to remember)</small></span> Sadly SQRL never really took off, and was replaced with Passkeys (which is supported).</li>
</ul>
<p>If you are here to link to BBS, please get started by <a href="{{ url('login') }}">logging in</a>.</p>
@ -99,16 +105,16 @@
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>
href="https://gitea.dege.au/bbs/clrghouz">gitea</a></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><strike>CockroachDB - a high available, geodispersable database, that enables accessing configuration and
<li><span style="text-decoration: line-through;">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>
mail</span> For now, Clearing Houz is using PostgreSQL</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>