субота, 10 січня 2026 р.

 


Noosphere, Connectivity, and Decentralized Networks: Why Open Development Became Critical Infrastructure for Thought
#Noosphere #Decentralization #OpenSource #Networks #DigitalRights

Alternative SEO Headlines

  1. Decentralized Networks Are No Longer IT—they Are the Noosphere

  2. Open Networks and the Noosphere: How Connectivity Shapes Collective Thinking

  3. Decentralization as the Survival Condition for the Noosphere


Readable Subheadline

How communication has stopped being just a tool and became the environment itself—where control over networks is control over collective intelligence.


Section Subheadings

  • The Noosphere Is No Longer Just a Metaphor

  • Connectivity as Habitat, Not Service

  • Centralized Networks and Cognitive Hierarchies

  • Decentralization as an Attempt to Restore Symbiosis

  • Technical Choices Are Questions of Freedom

  • Open Development as the Noosphere’s Self-Reflection

  • Bifurcation Point: Distributed Mind or Managed User


Target Audience

Primary:

  • Network administrators and engineers

  • Developers of decentralized and alternative networks

  • Security and protocol architecture specialists

  • Open-source community members

Secondary:

  • Digital philosophers and tech-humanitarians

  • Privacy and digital rights activists

  • Analysts studying societal impact of technology

  • Experienced users frustrated by marketing-driven security

Not Target Audience:

  • Web3 hobbyists

  • Consumers of pre-packaged ecosystems without interest in architecture

  • Slogan-minded readers without technical engagement


Editorial Introduction

The noosphere—the layer of collective thought above the biosphere—was long a philosophical abstraction, elegant yet disconnected from practical engineering. Today, it has become an engineering reality. Humanity has embedded coordination, memory, and cognition into communication networks so tightly that losing connectivity does more than inconvenience us: it erodes society’s ability to think and act as a coherent whole.

The noosphere no longer exists “above” technology—it manifests through it. Networks are now the environment where economies, sciences, culture, governance, and even basic social solidarity operate. Any failure, centralized control, or asymmetry in access directly distorts collective cognition. Network architecture is thus not merely a technical question but a civilizational one.

Decentralized networks matter precisely because centralized models, while convenient and efficient, introduce systemic distortions: single points of control, surveillance, and coercion. They shape a noosphere with “gravity centers,” where some nodes think and others merely serve. This is not symbiosis—it is hierarchy.

Decentralized networks—such as Yggdrasil, Mycelium, Reticulum—offer a different model: a centerless noosphere. Not perfect, not magically secure, but fundamentally more resilient to political, economic, and technical failures. Every node is both participant and consumer, closer to biological or neural systems than to corporate data centers.

However, decentralization alone guarantees nothing. Layering “security,” “convenience,” or “user-friendly” defaults over it can recreate alienation under a new brand. Discussions over TLS, mandatory encryption, automatic routing, and “correct” configurations are thus not debates about bytes—they are debates about the limits of autonomy.

Open development is critical—not because it’s “free” or ideologically pure, but because it allows the noosphere to reflect on itself. Closed systems cannot collectively understand their own limitations. Open ones can—even if only a few take full advantage.

We now live at a point where the noosphere is symbiotic with connectivity. Losing control over network architecture is tantamount to losing control over the future of thought. This is not yet catastrophic, but it is a bifurcation point. Networks will either remain extensions of human cooperation or reduce humans to peripheral devices for someone else’s protocols.

In this sense, discussions about decentralized networks are not for “geeks” or “enthusiasts.” They are about whether intelligence will remain distributed—or once again be consolidated in a few racks with backup power and a marketing department.



 # Thoughts Regarding TLS in Yggdrasil and Mycelium Networks | DevZone


# Thoughts Regarding TLS in Yggdrasil and Mycelium Networks


3 min. reading


September 1


[

1

](https://devzone.org.ua/votes/show/post/40076)


· 40 ·


[

0

](#comments)


·


*Internet version of my publication for the site of the local community of alternative networks administrators.*


In the environment of overlay networks, it is somehow accepted that if node keys are permanent and connections between nodes are protected by TLS, then an additional SSL layer is supposedly not needed. However, lately, I have started to doubt this.


## Key Compromise


In networks like [Yggdrasil](https://devzone.org.ua/post/yggdrasil-mereza-z-detsentralizovanym-routynhom) / [Mycelium](https://github.com/threefoldtech/mycelium), there is no level of complexity in generating private keys, so theoretically (though unlikely) a collision is possible. For this reason, it is recommended to use main addresses instead of subnets, and the latter - developers plan to, but have not yet removed. And they are convenient within shared hosting. Anyway, this does not exclude the possibility of accidental extraction of a copy, or not accidental, considering the potential capabilities of the crypto industry; the question is only the appropriateness of using a supercomputer for this purpose; how many users these networks will include and of what wealth, for potential attacks on routing based on a fixed algorithm for building a tree from peer ID.


## Double Layer


Technically, the Yggdrasil transport protocol takes on the role of traffic encryption when it may not be necessary. For example, in cases:


- saving electricity and CPU resources when forwarding large media files

- when the SSL / HTTPS layer is already used at the software level - to avoid interceptions of login/password or simply confidential forwarding of GET requests through proxies


Practical example: the requirement for traffic encryption [Gemini](https://devzone.org.ua/post/protokol-gemini-iak-alternatyva-http) within Yggdrasil, because the first one wants to be protected for the Internet, but I use it not where the author intended. For this reason, for some time I used the alternative [Nex](https://devzone.org.ua/post/protokol-nex-lehka-alternatyva-gemini), but later realized that some data potentially may still require a certificate, and therefore, I need the old-good HTTP+HTTPS model on sensitive forms.


If sensitive data is transmitted from the client to the server, then in my opinion, it is worth using an SSL certificate, which will serve as a safeguard, but the router has already "taken care" of everything, creating unnecessary problems.


## Certification in Local Networks


Due to the isolation of local networks, in Yggdrasil it is a problem to set up a valid certificate, for example with Let's Encrypt. But in the case of the Gemini protocol - certification authorities are not used at all. Instead, the [TOFU](https://en.wikipedia.org/wiki/Trust_on_first_use) principle is applied, which significantly reduces the risk of data interception over time - until the leak is detected. I even had thoughts about organizing an internal network certification center, why not; why not even make such a service paid?


## Conclusions


When and how exactly to encrypt data - should be decided by the user / network administrator, for those streams / data that require it. Whereas Yggdrasil and Mycelium - do it "voluntarily-compulsorily" as, in fact, other newfangled software with the label "absolutely secure". Modern software, whose developers compete for the right to be called "protected" resembles crypto-cabbage with a security coefficient was == became.


Somehow it already starts to annoy when someone starts deciding something for me where they are not asked. Marketing is marketing, slogans are slogans, but experienced users leave because of such discomfort, and tourists don't stay anyway.


And also the conclusions are that effective network solutions were invented by post-war specialists half a century ago, who had to survive, not play commercial experiments. Nothing fundamentally new has been invented in this time. Perhaps the next breakthrough will be quantum data transmission, not such nonsense: laying an automatic route to probably compromised nodes, while encrypting tons of garbage that goes through it.


Noticed an error? Notify the author, for this it is enough to highlight the text with the error and press Ctrl+Enter


[

Subscribe

](https://devzone.org.ua/login)


##### p.s.  1.3K


Joined:

    1 year ago


##### Comments (0)


#### There are no comments yet


To leave a comment, you need to log in.


Login


#### Similar Articles


1) 


[

My Alfis DNS Preset on Yggdrasil / Mycelium Router

](https://devzone.org.ua/post/miy-preset-alfis-dns-na-routeri-yggdrasilmycelium)


            I managed to crash the operating system again here, so I had to set up the con...

        

2) 


[

About Fediverse Server in Alternative Networks

](https://devzone.org.ua/post/pro-server-fediverse-v-alternatyvnykh-merezakh)


            I have been using Fediverse for a long time, but I set up my own instance relatively recently: approxima...

        

3) 


[

Yggdrasil - Network with Decentralized Routing

](https://devzone.org.ua/post/yggdrasil-mereza-z-detsentralizovanym-routynhom)


            Yggdrasil - experimental protocol for building a self-organized local...

        

4) 


[

Organization of e-mail Mailbox for Local Networks without DNS

](https://devzone.org.ua/post/orhanizatsiia-poshtovoyi-skrynky-e-mail-dlia-lokalnykh-merez-bez-dns)


            This material is an adaptation of the instructions for users of the local [admin community...

        

5) 


[

Reticulum / MeshChat with Connection via Yggdrasil

](https://devzone.org.ua/post/reticulum-vstanovlennia-na-prykladi-meshchat-z-pidkliuchenniam-cherez-yggdrasil)


            Reticulum - a relatively new communication protocol, created primarily for radio-m...

        

6) 


[

Isolation of Linux from Direct Internet Connections Based on QEMU / Virtual Machine Manager with VSOCK

](https://devzone.org.ua/post/izoliatsiia-linux-vid-priamykh-internet-zyednan-na-bazi-qemu-virtual-machine-manager-i-vsock)


            The material provides an example of isolating a virtual Linux operating system (and...

        

7) 


[

Installation and Configuration of IRC Bouncer ZNC in Linux

](https://devzone.org.ua/post/vstanovlennia-ta-nalashtuvannia-irc-baunsera-znc-v-linux)


            IRC is one of the oldest multi-user chat protocols, which is still alive...

        

8) 


[

Limiting Outgoing Connections to the Internet with ufw

](https://devzone.org.ua/post/obmezennia-vykhidnykh-zyednan-na-internet-z-ufw)


            *ufw is a command-line utility frontend for simplified management of iptables rules i...


##### Subscribe to the Weekly Newsletter


Get the best articles of the week by email


Subscribe


Subscribe to the Weekly Newsletter


Subscribe

 Перевод на русский с интеграцией хэштегов прямо в текст.


Настройка Fedi-сервера Snac для сети Yggdrasil | DevZone

#Fediverse #Yggdrasil #SelfHosting #P2P #Linux

Время чтения: 15 минут
11 мая

Вскоре после моих размышлений о p2p я решил попробовать развернуть собственный экспериментальный инстанс #Fediverse. Причём сделать это средствами оверлейной сети #Yggdrasil, так как я не планирую покупать выделенный IP или VPS для этой игрушки; вместо этого сервер будет хоститься за модемом — на одноплатнике или даже на ПК, когда я в сети, с динамическим адресом за NAT.

Эта заметка в первую очередь написана для себя, но может быть полезна тем, кто, как и я, только начинает эксперименты с администрированием собственного узла Fediverse и интересуется альтернативными сетями в контексте #Linux.

Что такое Snac

#Snac #ActivityPub #Minimalism

Snac — это минималистичная альтернатива серверу #Mastodon, написанная на C, без JavaScript и без необходимости установки PostgreSQL. Все данные профилей хранятся в JSON-файлах. Недавно в сервер была добавлена поддержка IPv6, поэтому он корректно работает и с диапазоном Yggdrasil 0200::/7.

Поскольку Yggdrasil позволяет бесплатно генерировать неограниченное количество статических IP (на основе приватного ключа #Ed25519), в DNS здесь обычно нет необходимости. Опционально можно прикрутить #Alfis, но лично я этого не делаю (в том числе из-за до сих пор нерешённой проблемы #364), поэтому и не навязываю его в рамках протокола ActivityPub — формат будет просто username@IPv6, без необходимости что-то обновлять или «майнить» позже.

Установка

#BuildFromSource #LinuxAdmin

  1. Точный список пакетов для Debian я не знаю — система не новая и многое уже установлено. Согласно README, мне понадобились только libssl-dev и libcurl4-openssl-dev (в Fedora — примерно то же самое, но с суффиксом -devel).

  2. Создаём отдельного системного пользователя для изоляции от потенциальных уязвимостей:

    useradd -m snac
    
  3. Для удобства меняем shell на bash в /etc/passwd.

  4. Логинимся su snac и переходим в домашний каталог: cd.

  5. Качаем исходники:
    git clone https://codeberg.org/grunfink/snac2.git

  6. Переходим в каталог проекта: cd snac2.

  7. Компилируем и устанавливаем:
    make && sudo make install.

  8. Инициализируем хранилище сервера:
    snac init /home/snac/storage.

  9. Добавляем первого пользователя:
    snac adduser /home/snac/storage.

  10. Выходим обратно под root: exit.

Конфигурация

#Networking #Yggdrasil

У меня уже установлен и настроен узел Yggdrasil. Если интересно — см. предыдущую публикацию или официальную документацию.

Адрес подсети Yggdrasil

#IPv6

Этот шаг можно пропустить и использовать основной адрес 2*, если порты 80 или 8001 свободны. Но важно понимать: в API ActivityPub сервер Snac сообщает свой адрес другим узлам, и те кэшируют его как часть ID. Поскольку адрес хранится в файлах, а не в БД, заменить его потом будет сложно. Поэтому лучше сразу выделить отдельный адрес, особенно для продакшена.

  1. yggdrasilctl getself — узнаём свой IP и диапазон IPv6.

  2. ifconfig lo inet6 add IP — вместо IP указываем произвольный адрес из полученного диапазона, например 3xx:xxxx:xxxx:xxxx::fed/64.

⚠️ Данные, добавленные через ifconfig, не сохраняются после перезагрузки. Команду нужно прописать, например, в /etc/netplan/01-ygglo.yaml, /etc/network/interfaces или в systemd-сервис yggdrasil.service (через ExecStartPost=).

Nginx-прокси

#Nginx #ReverseProxy

На сервере уже установлен Nginx, занимающий порт 80. Менять это я не хочу, как и светить Snac на стандартном порту 8001. Поэтому, имея выделенный IPv6-адрес, просто проксирую API на 80, используя пример из оригинальной конфигурации:

server {
    listen [3xx:xxxx:xxxx:xxxx::fed]:80;
    server_name 3xx:xxxx:xxxx:xxxx::fed;

    location @proxy {
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_redirect off;
        proxy_pass http://[3xx:xxxx:xxxx:xxxx::fed]:8001;
    }

    location /.well-known/webfinger { try_files $uri @proxy; }
    location /.well-known/nodeinfo { try_files $uri @proxy; }
    location / { try_files $uri @proxy; }
    location /fedi/ { try_files $uri @proxy; }
}

SSL здесь намеренно отсутствует: #Yggdrasil уже обеспечивает защищённый канал, и дополнительный слой не нужен.

Административный API (admin и oauth) я ограничил по IP, поскольку у клиентов Yggdrasil адреса тоже статические:

location ~ /([^\/]+/admin|oauth) {
    allow ADMIN_IP;
    deny all;
    try_files $uri @proxy;
}

Конфигурация Snac

#JSON #Config

Редактируем /home/snac/storage/server.json, созданный командой snac init:

{
  "host": "[3xx:xxxx:xxxx:xxxx::fed]",
  "address": "3xx:xxxx:xxxx:xxxx::fed",
  "port": 8001,
  "protocol": "http"
}

В моём случае протокол намеренно http.

Доступ через iptables / ufw

#Firewall

Открываю порт только для диапазона Yggdrasil:

ufw allow from 0200::/7 to any port 80

Если не используете Nginx — указывайте реальный порт, например 8001.

systemd

#Systemd

На основе официального примера:

[Unit]
After=network-online.target
Wants=network-online.target

[Service]
User=snac
ExecStart=/usr/local/bin/snac httpd /home/snac/storage

[Install]
WantedBy=multi-user.target

Бэкапы

#Backup #Rsync

Так как база — это файлы, резервное копирование тривиально. Использую rsync через crontab -e:

@daily   rsync -av --delete /home/snac/storage /path/to/snac/daily
@weekly  rsync -av --delete /home/snac/storage /path/to/snac/weekly
@monthly rsync -av --delete /home/snac/storage /path/to/snac/monthly

Использование

#FediverseAdmin

После запуска (snac httpd /home/snac/storage или через systemd) можно открыть
http://[3xx:xxxx:xxxx:xxxx::fed] в браузере.

Тест взаимодействия

#ActivityPub

Для проверки федерации разверните второй узел в Yggdrasil и попробуйте подписку или переписку через Web UI или клиент.

Настройка браузера

#Firefox #IPv6

При первом использовании Yggdrasil-сайтов в Firefox может понадобиться изменить параметры в about:config:

  • browser.fixup.fallback-to-https = false

  • browser.fixup.alternate.enabled = false


#Fediverse #YggdrasilNetwork #Decentralization #AltNet #SelfHosted

  Noosphere, Connectivity, and Decentralized Networks: Why Open Development Became Critical Infrastructure for Thought #Noosphere #Decentral...