From 010f34f4f23eb190f5ae6326b5641a32a7685df0 Mon Sep 17 00:00:00 2001 From: Deon George Date: Sat, 14 Dec 2024 18:43:28 +0700 Subject: [PATCH] Update our welcome page with feature updates and more information --- public/robots.txt | 3 ++- resources/views/about.blade.php | 28 +++++++++++++++++----------- 2 files changed, 19 insertions(+), 12 deletions(-) diff --git a/public/robots.txt b/public/robots.txt index eb05362..1504053 100644 --- a/public/robots.txt +++ b/public/robots.txt @@ -1,2 +1,3 @@ User-agent: * -Disallow: +Allow: /about +Disallow: / diff --git a/resources/views/about.blade.php b/resources/views/about.blade.php index 46b2bdc..e23bb38 100644 --- a/resources/views/about.blade.php +++ b/resources/views/about.blade.php @@ -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.

-

Building this software is driven by three main goals:

+

Building this software is driven by four main goals:

    -
  1. Self Service - so that users can setup and re-jig their configuration themselves, or new users can join a +
  2. 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).
    3. -
  3. Automation - so that repetitive tasks can be done with minimal effort.
    4. +
  4. Automation - so that repetitive tasks can be done with minimal effort.
  5. - High Availability - So if one hub goes down, users can automatically connect to an alternate hub to keep + 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. - + effort. 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. +
    6. +
  6. Connectivity - 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.
@@ -77,7 +83,7 @@ FSC-0039, FSC-0045, FSC-0048 -
  • Automatic delisting of idle nodes (to be implemented)
    • +
  • Automatic delisting of idle nodes, including marking them HOLD, then DOWN
  • DNS server, to enable resolving of registered nodes using domain dns names FTS-5004 with pN.fN.nN.zN.domain.ftn, or pN.fN.nN.zN.[domain dns zone] @@ -89,7 +95,7 @@

    If you are here to link to BBS, please get started by logging in.

    @@ -99,16 +105,16 @@ with nodes.

    This web UI has been inspired by the great work at int10h.org. If you have ideas to make it even better, please send me a message, or submit your comments in gitlab

    + href="https://gitea.dege.au/bbs/clrghouz">gitea

    Other technology that drives the Clearing Houz

    FTN Clearing Houz is made available by these technologies: