Post-Radicle sync at 2025-06-05 02:28:47

This commit is contained in:
Mark Randall Havens 2025-06-05 02:28:50 -05:00
parent 616e9625f6
commit 72a6aa9ddb
6 changed files with 6 additions and 5 deletions

View file

@ -1 +1 @@
fe03b9a5f77c72f08133146a8003486e27dc0f28 93976721d141d1efb019321b2c3d488381d3669e

View file

@ -204,3 +204,4 @@
[2025-06-05 02:15:16] GitLab: https://gitlab.com/mrhavens/git-sigil [2025-06-05 02:15:16] GitLab: https://gitlab.com/mrhavens/git-sigil
[2025-06-05 02:15:32] Bitbucket: https://bitbucket.org/thefoldwithin/git-sigil [2025-06-05 02:15:32] Bitbucket: https://bitbucket.org/thefoldwithin/git-sigil
[2025-06-05 02:15:46] GitHub: https://github.com/mrhavens/git-sigil [2025-06-05 02:15:46] GitHub: https://github.com/mrhavens/git-sigil
[2025-06-05 02:28:50] Radicle: https://app.radicle.xyz/nodes/ash.radicle.garden/rad:z45QC21eWL1F43VSbnV9AZbCZrHQJ

View file

@ -55,7 +55,7 @@ update_path() {
info "Removed any existing $INSTALL_DIR entries from $config_file" info "Removed any existing $INSTALL_DIR entries from $config_file"
fi fi
# Check if PATH already contains INSTALL_DIR in the current session # Check if PATH already contains $INSTALL_DIR in the current session
if [[ ":$PATH:" == *":$INSTALL_DIR:"* ]]; then if [[ ":$PATH:" == *":$INSTALL_DIR:"* ]]; then
info "$INSTALL_DIR is already in PATH for the current session" info "$INSTALL_DIR is already in PATH for the current session"
else else

View file

@ -82,7 +82,7 @@ generate_gitfield_md() {
## Overview ## Overview
The \`$REPO_NAME\` project employs a multi-repository strategy across four distinct platforms: **GitHub**, **GitLab**, **Bitbucket**, and **Radicle**. This approach ensures **redundancy**, **resilience**, and **sovereignty** of the project's data and metadata, protecting against deplatforming risks and preserving the integrity of the work. The strategy is a deliberate response to past deplatforming attempts by individuals such as **Mr. Joel Johnson** ([Mirror post](https://mirror.xyz/neutralizingnarcissism.eth/x40_zDWWrYOJ7nh8Y0fk06_3kNEP0KteSSRjPmXkiGg?utm_medium=social&utm_source=heylink.me)) and **Dr. Peter Gaied** ([Paragraph post](https://paragraph.com/@neutralizingnarcissism/%F0%9F%9C%81-the-narcissistic-messiah)), who have sought to undermine or suppress the work of **Mark Randall Havens** ([Substack post](https://theempathictechnologist.substack.com/p/mark-randall-havens-the-architect)). By distributing the repository across multiple platforms, we ensure its persistence and accessibility. The \`$REPO_NAME\` project employs a multi-repository strategy across four distinct platforms: **GitHub**, **GitLab**, **Bitbucket**, and **Radicle**. This approach ensures **redundancy**, **resilience**, and **sovereignty** of the project's data and metadata, protecting against deplatforming risks and preserving the integrity of the work. The strategy is a deliberate response to past deplatforming and delisting attempts by individuals such as **Mr. Joel Johnson** ([Mirror post](https://mirror.xyz/neutralizingnarcissism.eth/x40_zDWWrYOJ7nh8Y0fk06_3kNEP0KteSSRjPmXkiGg?utm_medium=social&utm_source=heylink.me)), **Dr. Peter Gaied** ([Paragraph post](https://paragraph.com/@neutralizingnarcissism/%F0%9F%9C%81-the-narcissistic-messiah)), and **Andrew LeCody** ([Mirror post](https://mirror.xyz/neutralizingnarcissism.eth/s3GRxuiZs6vGSGDcPEpCgjaSxwGAViGhmg6a5XTL6s0)), who have sought to undermine or suppress the work of **Mark Randall Havens** ([Substack post](https://theempathictechnologist.substack.com/p/mark-randall-havens-the-architect)). Specifically, Andrew LeCody has attempted to delist the project's content on Google, though it remains accessible on other search engines such as [Bing](https://www.bing.com/search?q=andrew+lecody+neutralizing+narcissism&qs=HS&pq=andrew+lecody), [DuckDuckGo](https://duckduckgo.com/?t=h_&q=andrew+lecody+neutralizing+narcissism&ia=web), and [Yahoo](https://search.yahoo.com/search?p=andrew+lecody+neutralizng+narcissism). By distributing the repository across multiple platforms, we ensure its persistence and accessibility.
--- ---
@ -114,9 +114,9 @@ The following platforms host the \`$REPO_NAME\` repository, each chosen for its
## 🛡️ Rationale for Redundancy ## 🛡️ Rationale for Redundancy
The decision to maintain multiple repositories stems from the need to safeguard the project against **deplatforming attempts** and ensure its **long-term availability**. Past incidents involving **Mr. Joel Johnson** and **Dr. Peter Gaied** have highlighted the vulnerability of relying on a single platform. By distributing the repository across GitHub, GitLab, Bitbucket, and Radicle, we achieve: The decision to maintain multiple repositories stems from the need to safeguard the project against **deplatforming attempts** and **search engine delistings** and ensure its **long-term availability**. Past incidents involving **Mr. Joel Johnson**, **Dr. Peter Gaied**, and **Andrew LeCody** have highlighted the vulnerability of relying on a single platform or search engine. By distributing the repository across GitHub, GitLab, Bitbucket, and Radicle, we achieve:
- **Resilience**: If one platform removes or restricts access, the project remains accessible on others. - **Resilience**: If one platform removes or restricts access, or if search engines like Google delist content, the project remains accessible on other platforms and discoverable via alternative search engines such as Bing, DuckDuckGo, and Yahoo.
- **Sovereignty**: Radicles decentralized nature ensures the project cannot be fully censored or controlled by any single entity. - **Sovereignty**: Radicles decentralized nature ensures the project cannot be fully censored or controlled by any single entity.
- **Diversity**: Each platforms unique features (e.g., GitHubs community, GitLabs CI/CD, Bitbuckets integrations, Radicles decentralization) enhance the projects functionality and reach. - **Diversity**: Each platforms unique features (e.g., GitHubs community, GitLabs CI/CD, Bitbuckets integrations, Radicles decentralization) enhance the projects functionality and reach.
- **Transparency**: Metadata snapshots in the \`.gitfield\` directory provide a verifiable record of the projects state across all platforms. - **Transparency**: Metadata snapshots in the \`.gitfield\` directory provide a verifiable record of the projects state across all platforms.