ADA compliance clarification

Policies/Design_Principles.md

@@ -61,15 +61,19 @@ GUI elements will generally be deployed by a Web page, as this is a cross-platfo
 ##  Mobile Access Design
 With the rise of the smartphone, remotely accessible services should offer a simple means via some app to reduce network traffic. The app interface should be intuitive and quick to use.
 
+## Accessibility
+
+AniNIX will, within reason, attempt to make its pages as accessible as possible to those with disabilities. To this end, internally-written UI elements should attempt to [maintain ADA / WCAG compliance](https://www.ada.gov/resources/web-guidance/) -- audit tools [such as this one](https://www.accessibilitychecker.org/) can assist.
+
+Additionally, our protocols-over-apps implementation preference with RSS, IRC, and Git should hopefully make the majority of our content accessible for anyone. This preference should allow designers to create tools to consume content irrespective of the method of perception or interaction for the user.
+
 ##  Etymology
 
-The AniNIX attaches a unique name, such as Sora for OpenLDAP or Yggdrasil for Emby, to packages and services it instantiates. The reason for this is that the name defines a scope of functionality the AniNIX expects to rely on -- should the underlying package change, such as replacing Plex Media Server with Emby, documentation and AniNIX packages will use the same name.
+The AniNIX attaches a unique name, such as Sora for OpenLDAP or Yggdrasil for Emby, to packages and services it instantiates. The reason for this is that the name defines a scope of functionality the AniNIX expects to rely on -- should the underlying package change, such as replacing Plex Media Server with Emby, documentation and AniNIX packages will use the same name. We also need a naming convention for unique code we are writing, like Uniglot & TheRaven
 
-Names given should be chosen for relevance to the function being provided (Singularity being a pull service, Foundation being the basis on which we're built, etc.) and for ease of memory. Only the most basic services, such as IRC, WebServer, and SSH, will be left unnamed.
+These names are not intended to supersede the licensing or attribution of other packages -- applications, once installed, should only update the minimal allowable elements to be usable under AniNIX principles. Wherever possible, this should be done via the application's provided interface, such as enabling dark modes. We also should not remove any links that the application provides to its own documentation, licensing, or websites. This means that AniNIX etymology only applies to administrators and is otherwise invisible to end users. Where the AniNIX is deploying services created by others, we should only use the names in two places: DNS and Kapisi roles. This makes it possible for others to look up the service as we swap out tools without overriding the attribution once the service is accessed.
 
-These names are not intended to supersede the licensing or attribution of other packages -- applications, once installed, should only update the minimal allowable elements to be usable under AniNIX principles. Wherever possible, this should be done via the application's provided interface, such as enabling dark modes. We also should not remove any links that the application provides to its own documentation, licensing, or websites. This means that AniNIX etymology only applies to administrators and is otherwise invisible to end users.
-
-Additionally, these names should be selected from one of the following categories:
+Names given should be chosen for relevance to the function being provided (Singularity being a pull service, Foundation being the basis on which we're built, etc.) and for ease of memory. Only the most basic services, such as IRC, WebServer, and SSH, will be left unnamed. Additionally, these names should be selected from one of the following categories:
 
 1. A natural phenomenon that describes the function, such as Singularity or Aether
 1. Mythological figures that provide wisdom (such as Odin for Yggdrasil, Raven, and Wolfpack), truth (like Wiccan Grimoire), and morality (such as Maat)

rss/aninix.xml

@@ -12,32 +12,22 @@
     <id>https://aninix.net/</id>
 
     <entry>
-        <title>Lunch-And-Learns Paused Until 2024FEB29</title>
-        <link href="https://aninix.net/AniNIX/Wiki/commit/48e6e1b31adaf649d9f375570bd85109fa694d9b"></link>
-        <updated>2023-10-23T04:09:00Z</updated>
-        <id>https://aninix.net/AniNIX/Wiki/commit/48e6e1b31adaf649d9f375570bd85109fa694d9b</id>
+        <title>Lunch-and-Learns Paused 20240502 through 20240627</title>
+        <link href="https://aninix.net/aninix.xml#lnl-pause-20240502"></link>
+        <updated>2024-04-25T17:21:00Z</updated>
+        <id>https://aninix.net/aninix.xml#lnl-pause-20240502</id>
         <summary>
-            Lunch-and-learns are paused until February 29th -- I have real-life obligations that won't allow me to keep the streaming window. We will instead hold conversations in our Discord #tech channel. I'll post something there when I can and mention the Lunch&amp;Learn role with a commit of interest off the AniNIX projects. If you have questions you want to talk about, ask away!
+            AniNIX will be pausing Lunch-and-Learns effective 20240502 through 20240627 for real-life training. We will merge AniNIX/Wiki#24 on our return.
         </summary>
     </entry>
 
      <entry>
-        <title>Expanded Lunch-And-Learns</title>
-        <link href="https://www.youtube.com/channel/UCe-WNM2mbI51xoVZp3K_wFQ#20231023"></link>
-        <updated>2023-10-23T04:09:00Z</updated>
-        <id>https://www.youtube.com/channel/UCe-WNM2mbI51xoVZp3K_wFQ#20231023</id>
+        <title>CVE-2024-3094 Follow-up</title>
+        <link href="https://aninix.net/aninix.xml#CVE-2024-3094"></link>
+        <updated>2024-04-17T20:15:00Z</updated>
+        <id>https://aninix.net/aninix.xml#CVE-2024-3094</id>
         <summary>
-            We are expanding our Lunch-and-Learns to both YouTube and Twitch in an attempt to reach more people. Lunch-and-learns will also move to Thursdays to try to better reach our existing contributors.
-        </summary>
-    </entry>
-
-    <entry>
-        <title>Outage 2023-10-23</title>
-        <link href="https://aninix.net/AniNIX/Wiki/src/branch/main/Operation/Continuity.md#business-continuity"></link>
-        <updated>2023-10-23T04:09:00Z</updated>
-        <id>https://aninix.net/aninix.xml#20231024</id>
-        <summary>
-                We will have an extended outage 2023-10-24 0700 US Central until late in the evening, as our primary site is undergoing construction. Please watch #tech on Discord fo r tracking service recovery. During this time, please fall back on business continuity procedures to keep access to services provided by the AniNIX.
+            AniNIX was informed of CVE-2024-3094 via our OSINT community on 2024-03-28 -- patching was completed in AniNIX/Maat on 2024-03-29 and in all systems the day after. Security review of our access logs in AniNIX/Sharingan do not indicate a compromise, using dork `"accepted" AND application_name:"sshd" AND NOT "Accepted publickey"` and others. We apologize for the delay in follow-up and transparency, but other considerations have required attention prior to this post.
         </summary>
     </entry>
 
@@ -51,36 +41,6 @@
         </summary>
     </entry>
 
-    <entry>
-        <title>How to Grow Your HomeLab</title>
-        <link href="https://foundation.aninix.net/AniNIX/Wiki/src/branch/main/Articles/Grow_Your_Homelab.md"></link>
-        <updated>2022-04-22T20:30:20Z</updated>
-        <id>https://foundation.aninix.net/AniNIX/Wiki/src/branch/main/Articles/Grow_Your_Homelab.md</id>
-        <summary>
-            For some folks who are just starting out, the initial cost of a complete HomeLab stack and the administration required is a bit much. This article is a growth plan for how to get started, what technologies and tools to buy/deploy first, etc.
-        </summary>
-    </entry>
-
-    <entry>
-        <title>Lunch And Learns</title>
-        <link href="https://foundation.aninix.net/AniNIX/Wiki/src/branch/main/Articles/Lunch-And-Learns.md"></link>
-        <updated>2022-04-14T20:30:20Z</updated>
-        <id>https://foundation.aninix.net/AniNIX/Wiki/src/branch/main/Articles/Lunch-And-Learns.md</id>
-        <summary>
-            I've had a request to do some lunch-and-learns about the AniNIX, how we self-host, and how we manage some of our tools. We'll burn roughly the first 30-45 minutes talking through some concepts of how the AniNIX does what it does -- the rest of the time will be an open floor to ask anything you'd like. If you're interested, swing by! Google Calendar link is on the article page.
-        </summary>
-    </entry>
-
-    <entry>
-        <title>The Complicated Cloud</title>
-        <link href="https://foundation.aninix.net/AniNIX/Wiki/src/branch/main/Articles/The_Complicated_Cloud.md"></link>
-        <updated>2022-02-17T16:30:20Z</updated>
-        <id>https://foundation.aninix.net/AniNIX/Wiki/src/branch/cloud/Articles/The_Complicated_Cloud.md</id>
-        <summary>
-            The AniNIX is a self-hosted system, as much as we can make it. However, because we don't operate in isolation, it's worth documenting how we use the cloud for what declassified information we replicate onto cloud stores and why we need some cloud services.
-        </summary>
-    </entry>
-
     <entry>
         <title>GPG Key Distribution</title>
         <link href="https://foundation.aninix.net/AniNIX/ShadowArch/src/branch/main/EtcFiles/aninix.gpg"></link>