Reorganizing a link -- new RSS articles

This commit is contained in:
DarkFeather 2022-02-17 10:40:02 -06:00
parent c88cb8a329
commit 7e7c2c0afb
Signed by: DarkFeather
GPG Key ID: 1CC1E3F4ED06F296
4 changed files with 31 additions and 2 deletions

View File

@ -0,0 +1,9 @@
# Web
# SSH Keys
# GPG Keys
```
gpg --allow-freeform-uid --gen-key
```

View File

@ -35,14 +35,14 @@ As a small self-hosted site with only a single replica, we don't have much of an
As such, we need to validate that the world can route to us. We use a service called [Freshping][freshping] to monitor us. Freshping emails our admin reports, and it also can trigger webhooks. We haven't had much success linking Freshping to [Discord][discord] directly, so we use [Zapier][zapier] as an intermediary. Discord is the notification service of choice, because if we're off-site and our site is offline, then there'll be no notification and we cannot escalate to our ISP.
Discord serves an ancilliary function for us, as well. Discord is our primary telephony solution for making video and voice calls within the network. While there are services we could host to do this, voice prints are necessarily identifying and can be falsified -- IRC identity validation by authentication and GPG-encrypting messages is more secure and anonymous. Moreover, having our telephony solution remote also allows our admins to fall back to it when the network is offline to discuss root-cause and remediation. We maintain a [FreeConferenceCall.com][fcf] account and a Google Voice number for more traditional phone systems, but we rarely use them because of poor spam and authentication.
Discord serves an ancilliary function for us, as well. Discord is our primary telephony solution for making video and voice calls within the network. While there are services we could host to do this, voice prints are necessarily identifying and can be falsified -- IRC identity validation by authentication and GPG-encrypting messages is more secure and anonymous. Moreover, having our telephony solution remote also allows our admins to fall back to it when the network is offline to discuss root-cause and remediation. We maintain a [FreeConferenceCall.com][fcf] account and a [Google Voice][voice] number for more traditional phone systems, but we rarely use them because of poor spam and authentication.
## Google: Communicating with the outside World
We use Google for a few things.
* Initial site analytics & external validation of our web development practices via [Google Analytics][analytics].
* Domain DNS via [Google Domains][domain].
* Direct phone number via [Google Voice][voice].
* Direct phone number via Google Voice.
* We are considering using Google Workspace in [AniNIX/Wiki#8](/AniNIX/Wiki/issues/8) for our SMTP presence, even though we don't like email. As we look toward being a contract organization, being able to interact with business people on their level is an unfortunate necessity.
Effectively, Google services here are handling all the legacy cruft for us in dealing with the external world. These services are typically more difficult to secure, though they are more familiar to average users.

View File

@ -11,6 +11,16 @@
<id>https://aninix.net/</id>
<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>

View File

@ -11,6 +11,16 @@
<id>https://aninix.net/martialarts</id>
<entry>
<title>February Ruck</title>
<link href="https://discord.gg/2bmggfR#signups-ruck"></link>
<updated>2022-02-17T16:31:55Z</updated>
<id>https://discord.gg/2bmggfR#signups-ruck</id>
<summary>
We will be doing a basic 6-mile ruck-march in two 3-mile legs. Each leg will start and end at 225 Blaser Dr. You should expect to dress for the cold weather, pack a water source of sufficient volume to carry you for the duration, and good socks and boots. If you're bringing any kind of training weight, make sure your kit is appropriately packed. Connor will review all kit and lead a warmup prior to step-off.
</summary>
</entry>
<entry>
<title>Updated Class Policy</title>
<link href="https://foundation.aninix.net/mawiki/HapKiDo/pulls/1"></link>