#yggdrasil — Public Fediverse posts

Adding a single Reticulum node to `services.md` looks almost insignificant at first. A couple of lines in the documentation. No new protocol, no new router, no flashy release.

But the idea itself is more interesting than the size of the diff.

What we are looking at is a combination of two different overlay networks. Yggdrasil provides IPv6 routing over existing networks, while Reticulum builds its own cryptographically secured networking architecture that can operate over IP, Wi-Fi, LoRa, radio links, and other transports.

In this case, Yggdrasil effectively becomes a transport for Reticulum:

**Reticulum => TCP => Yggdrasil => other Yggdrasil nodes**

That distinction matters. The commit does not “integrate Reticulum into Yggdrasil.” It simply makes a specific Reticulum endpoint accessible through a Yggdrasil address.

And this is where things get interesting.

The conventional Internet model assumes that a service is tied to a public IP address, a domain, a provider, a hosting platform, or at least a stable access path. If the provider changes routing, blocks a port, the hosting service disappears, or the server ends up behind NAT, problems begin.

The overlay model moves that dependency to another layer.

A Reticulum node does not necessarily need its own public IPv4 address. It can be reachable through Yggdrasil. And Yggdrasil itself can use different physical and IP-based transports.

This is no longer simply “another VPN.”

It is an attempt to separate networking into layers:

physical link => transport => overlay routing => application-level mesh.

And if one transport disappears, the upper layers do not necessarily have to disappear with it.

But this is where we should not overstate the evidence.

The appearance of a node in `services.md` **does not prove** that the network became more resilient, that the node is still operational, or that it provides a reliable channel in any particular scenario.

It proves something much simpler:

**the Yggdrasil community had a Reticulum endpoint available and chose to publish it as a service.**

Everything beyond that requires separate verification.

And that is actually a good example of what a real decentralized networking ecosystem can look like. Not one “Internet-killer network,” but multiple independent protocols capable of using one another as transport.

Yggdrasil can carry Reticulum.

Reticulum can operate over completely different channels.

And underneath those layers you can have Ethernet, Wi-Fi, Starlink, radio, or LoRa.

So the real value here is not the specific node at `202:68d0:f0d5:b88d:1d1a:555e:2f6b:3148:4242`.

The value is the ability to build **a network from multiple independent layers**, where failure of one layer does not necessarily mean failure of the entire system.

For Ukraine, this is particularly interesting as an architecture. Not because Yggdrasil or Reticulum magically make communications “invulnerable.” They do not.

But because different access paths can be combined:

**Starlink => Yggdrasil => Reticulum**

or

**Wi-Fi mesh => Yggdrasil => Reticulum**

or, with appropriate hardware,

**radio/LoRa => Reticulum => IP/Yggdrasil**

And on top of that, you can run messaging, services, file exchange, and other decentralized applications.

That is no longer a fight over yet another “better messenger.”

It is a fight to make **the transport itself stop being a single point of failure**.

#Yggdrasil #Reticulum #MeshNetwork #P2P #Decentralization #OpenSource #NetworkResilience #PrivacyTech #Ukraine

Adding a single Reticulum node to `services.md` looks almost insignificant at first. A couple of lines in the documentation. No new protocol, no new router, no flashy release.

But the idea itself is more interesting than the size of the diff.

What we are looking at is a combination of two different overlay networks. Yggdrasil provides IPv6 routing over existing networks, while Reticulum builds its own cryptographically secured networking architecture that can operate over IP, Wi-Fi, LoRa, radio links, and other transports.

In this case, Yggdrasil effectively becomes a transport for Reticulum:

**Reticulum => TCP => Yggdrasil => other Yggdrasil nodes**

That distinction matters. The commit does not “integrate Reticulum into Yggdrasil.” It simply makes a specific Reticulum endpoint accessible through a Yggdrasil address.

And this is where things get interesting.

The conventional Internet model assumes that a service is tied to a public IP address, a domain, a provider, a hosting platform, or at least a stable access path. If the provider changes routing, blocks a port, the hosting service disappears, or the server ends up behind NAT, problems begin.

The overlay model moves that dependency to another layer.

A Reticulum node does not necessarily need its own public IPv4 address. It can be reachable through Yggdrasil. And Yggdrasil itself can use different physical and IP-based transports.

This is no longer simply “another VPN.”

It is an attempt to separate networking into layers:

physical link => transport => overlay routing => application-level mesh.

And if one transport disappears, the upper layers do not necessarily have to disappear with it.

But this is where we should not overstate the evidence.

The appearance of a node in `services.md` **does not prove** that the network became more resilient, that the node is still operational, or that it provides a reliable channel in any particular scenario.

It proves something much simpler:

**the Yggdrasil community had a Reticulum endpoint available and chose to publish it as a service.**

Everything beyond that requires separate verification.

And that is actually a good example of what a real decentralized networking ecosystem can look like. Not one “Internet-killer network,” but multiple independent protocols capable of using one another as transport.

Yggdrasil can carry Reticulum.

Reticulum can operate over completely different channels.

And underneath those layers you can have Ethernet, Wi-Fi, Starlink, radio, or LoRa.

So the real value here is not the specific node at `202:68d0:f0d5:b88d:1d1a:555e:2f6b:3148:4242`.

The value is the ability to build **a network from multiple independent layers**, where failure of one layer does not necessarily mean failure of the entire system.

For Ukraine, this is particularly interesting as an architecture. Not because Yggdrasil or Reticulum magically make communications “invulnerable.” They do not.

But because different access paths can be combined:

**Starlink => Yggdrasil => Reticulum**

or

**Wi-Fi mesh => Yggdrasil => Reticulum**

or, with appropriate hardware,

**radio/LoRa => Reticulum => IP/Yggdrasil**

And on top of that, you can run messaging, services, file exchange, and other decentralized applications.

That is no longer a fight over yet another “better messenger.”

It is a fight to make **the transport itself stop being a single point of failure**.

#Yggdrasil #Reticulum #MeshNetwork #P2P #Decentralization #OpenSource #NetworkResilience #PrivacyTech #Ukraine

It seems that about 50% of Btracker seeds have firewall issues, so created simple Web app in #Rust called #seedtest to check your client connectivity:

https://codeberg.org/YGGverse/seedtest

Working instance for #Yggdrasil:
http://[202:68d0:f0d5:b88d:1d1a:555e:2f6b:3148]:6969/seedtest

The Ash Yggdrasil (1886) by Lørenz Frolich, from Asgard and the Gods.

Source: California Digital Library / Internet Archive

https://pdimagearchive.org/images/d71b4451-13f6-4aa9-adda-d662bd421935

#ash #yggdrasil #trees #mythology #serpents #bookillustration #art #publicdomain

The Ash Yggdrasil (1886) by Lørenz Frolich, from Asgard and the Gods.

Source: California Digital Library / Internet Archive

https://pdimagearchive.org/images/d71b4451-13f6-4aa9-adda-d662bd421935

#ash #yggdrasil #trees #mythology #serpents #bookillustration #art #publicdomain

The Ash Yggdrasil (1886) by Lørenz Frolich, from Asgard and the Gods.

Source: California Digital Library / Internet Archive

https://pdimagearchive.org/images/d71b4451-13f6-4aa9-adda-d662bd421935

#ash #yggdrasil #trees #mythology #serpents #bookillustration #art #publicdomain

The Ash Yggdrasil (1886) by Lørenz Frolich, from Asgard and the Gods.

Source: California Digital Library / Internet Archive

https://pdimagearchive.org/images/d71b4451-13f6-4aa9-adda-d662bd421935

#ash #yggdrasil #trees #mythology #serpents #bookillustration #art #publicdomain

The requirement for an #impressum with name and address of the operator in DE for sites that might not be considered to fall under the exemption of being for personal or family use only, seems to me to be a bit ... how can I put it ... well you know ... What do you do in view of this? Anyone actually have a solution? #reticulum #nomadnet #i2p #eepsite #mesh #yggdrasil #tor

The requirement for an #impressum with name and address of the operator in DE for sites that might not be considered to fall under the exemption of being for personal or family use only, seems to me to be a bit ... how can I put it ... well you know ... What do you do in view of this? Anyone actually have a solution? #reticulum #nomadnet #i2p #eepsite #mesh #yggdrasil #tor

The requirement for an #impressum with name and address of the operator in DE for sites that might not be considered to fall under the exemption of being for personal or family use only, seems to me to be a bit ... how can I put it ... well you know ... What do you do in view of this? Anyone actually have a solution? #reticulum #nomadnet #i2p #eepsite #mesh #yggdrasil #tor

The requirement for an #impressum with name and address of the operator in DE for sites that might not be considered to fall under the exemption of being for personal or family use only, seems to me to be a bit ... how can I put it ... well you know ... What do you do in view of this? Anyone actually have a solution? #reticulum #nomadnet #i2p #eepsite #mesh #yggdrasil #tor

Auf https://repoducible.net kann man ausprobieren, wie schnell sich #NomadNet über verschiedene #Reticulum Interfaces browsen lässt.

Als Testinhalt dient beispielsweise ein Git-Repository. Man kann gezielt unterschiedliche Verbindungen auswählen und vergleichen, z. B. I2P, Yggdrasil oder TCP mit einem TCP-Interface direkt zum Server.

#tcp #i2p #yggdrasil #nururl
#Reticulum #nomadnet #reticuluminterfaces

Auf https://repoducible.net kann man ausprobieren, wie schnell sich #NomadNet über verschiedene #Reticulum Interfaces browsen lässt.

Als Testinhalt dient beispielsweise ein Git-Repository. Man kann gezielt unterschiedliche Verbindungen auswählen und vergleichen, z. B. I2P, Yggdrasil oder TCP mit einem TCP-Interface direkt zum Server.

#tcp #i2p #yggdrasil #nururl
#Reticulum #nomadnet #reticuluminterfaces

Auf https://repoducible.net kann man ausprobieren, wie schnell sich #NomadNet über verschiedene #Reticulum Interfaces browsen lässt.

Als Testinhalt dient beispielsweise ein Git-Repository. Man kann gezielt unterschiedliche Verbindungen auswählen und vergleichen, z. B. I2P, Yggdrasil oder TCP mit einem TCP-Interface direkt zum Server.

#tcp #i2p #yggdrasil #nururl
#Reticulum #nomadnet #reticuluminterfaces

Auf https://repoducible.net kann man ausprobieren, wie schnell sich #NomadNet über verschiedene #Reticulum Interfaces browsen lässt.

Als Testinhalt dient beispielsweise ein Git-Repository. Man kann gezielt unterschiedliche Verbindungen auswählen und vergleichen, z. B. I2P, Yggdrasil oder TCP mit einem TCP-Interface direkt zum Server.

#tcp #i2p #yggdrasil #nururl
#Reticulum #nomadnet #reticuluminterfaces

Обратил внимание, что сегодня сильно печально с получением арчёвых пакетиков. Рефлектор минут 5 маялся с поиском зеркала.

Поэтому, если у кого yggdrasil включён, можно использовать http://[201:fdd3:b236:edda:67f5:ff3c:af8d:4132]

Там обновления вроде стабильно проходят, сейчас проверял - всё ок было.

#archlinux #yggdrasil

Обратил внимание, что сегодня сильно печально с получением арчёвых пакетиков. Рефлектор минут 5 маялся с поиском зеркала.

Поэтому, если у кого yggdrasil включён, можно использовать http://[201:fdd3:b236:edda:67f5:ff3c:af8d:4132]

Там обновления вроде стабильно проходят, сейчас проверял - всё ок было.

#archlinux #yggdrasil

Обратил внимание, что сегодня сильно печально с получением арчёвых пакетиков. Рефлектор минут 5 маялся с поиском зеркала.

Поэтому, если у кого yggdrasil включён, можно использовать http://[201:fdd3:b236:edda:67f5:ff3c:af8d:4132]

Там обновления вроде стабильно проходят, сейчас проверял - всё ок было.

#archlinux #yggdrasil

@kvuzet Projects like this need to be built on anonymous routing protocols like I2P or Tor; I know less about them but perhaps including Yggdrasil, Reticulum or Meshtastic could further improve the censorship resilience. I would like to see a government try to ban an I2P site

#I2P #PSAD #Tor #Yggdrasil #Reticulum #Meshtastic #Censorship #Anonymity

@kvuzet Projects like this need to be built on anonymous routing protocols like I2P or Tor; I know less about them but perhaps including Yggdrasil, Reticulum or Meshtastic could further improve the censorship resilience. I would like to see a government try to ban an I2P site

#I2P #PSAD #Tor #Yggdrasil #Reticulum #Meshtastic #Censorship #Anonymity

@kvuzet Projects like this need to be built on anonymous routing protocols like I2P or Tor; I know less about them but perhaps including Yggdrasil, Reticulum or Meshtastic could further improve the censorship resilience. I would like to see a government try to ban an I2P site

#I2P #PSAD #Tor #Yggdrasil #Reticulum #Meshtastic #Censorship #Anonymity

@kvuzet Projects like this need to be built on anonymous routing protocols like I2P or Tor; I know less about them but perhaps including Yggdrasil, Reticulum or Meshtastic could further improve the censorship resilience. I would like to see a government try to ban an I2P site

#I2P #PSAD #Tor #Yggdrasil #Reticulum #Meshtastic #Censorship #Anonymity

What I would like for #atomique  to have in terms of #yggdrasil support is easily join a separate isolated network.

So you can have a family Sphere  which is essentailly a private yggdrasil network for your and your family.

And another Sphere says for work, a club, a project, people in your Mastodon instance or whatever.

So Having 10 networks is not iminaginable. But for that I'd need an yddgrasil executable that can spawn networks without  multiplying everything in memory and not 10 go executables.

What I would like for #atomique  to have in terms of #yggdrasil support is easily join a separate isolated network.

So you can have a family Sphere  which is essentailly a private yggdrasil network for your and your family.

And another Sphere says for work, a club, a project, people in your Mastodon instance or whatever.

So Having 10 networks is not iminaginable. But for that I'd need an yddgrasil executable that can spawn networks without  multiplying everything in memory and not 10 go executables.

What I would like for #atomique  to have in terms of #yggdrasil support is easily join a separate isolated network.

So you can have a family Sphere  which is essentailly a private yggdrasil network for your and your family.

And another Sphere says for work, a club, a project, people in your Mastodon instance or whatever.

So Having 10 networks is not iminaginable. But for that I'd need an yddgrasil executable that can spawn networks without  multiplying everything in memory and not 10 go executables.

What I would like for #atomique  to have in terms of #yggdrasil support is easily join a separate isolated network.

So you can have a family Sphere  which is essentailly a private yggdrasil network for your and your family.

And another Sphere says for work, a club, a project, people in your Mastodon instance or whatever.

So Having 10 networks is not iminaginable. But for that I'd need an yddgrasil executable that can spawn networks without  multiplying everything in memory and not 10 go executables.

The main issue I see with #yggdrasil is that is a Go app. Not an issue per se as it is one executable but the problem is I envision several networks connected simultaneously, not one.  Apparently the official solution is to run one process per network ? So if I want 10 isolated networks, that's 10 times the whole go runtime ?

The main issue I see with #yggdrasil is that is a Go app. Not an issue per se as it is one executable but the problem is I envision several networks connected simultaneously, not one.  Apparently the official solution is to run one process per network ? So if I want 10 isolated networks, that's 10 times the whole go runtime ?

The main issue I see with #yggdrasil is that is a Go app. Not an issue per se as it is one executable but the problem is I envision several networks connected simultaneously, not one.  Apparently the official solution is to run one process per network ? So if I want 10 isolated networks, that's 10 times the whole go runtime ?

The main issue I see with #yggdrasil is that is a Go app. Not an issue per se as it is one executable but the problem is I envision several networks connected simultaneously, not one.  Apparently the official solution is to run one process per network ? So if I want 10 isolated networks, that's 10 times the whole go runtime ?

Currently reading about #yggdrasil network to think about possible integration in #atomique.  Unlike Tor the goal isn't  anonimity. Just decentrazling communication between hosts.

And I want to make this easy like maybe cacher a list of public peers from https://publicpeers.neilalexander.dev/ and let the system get a json to get the closest ones to auto configure from atomique.org

Currently reading about #yggdrasil network to think about possible integration in #atomique.  Unlike Tor the goal isn't  anonimity. Just decentrazling communication between hosts.

And I want to make this easy like maybe cacher a list of public peers from https://publicpeers.neilalexander.dev/ and let the system get a json to get the closest ones to auto configure from atomique.org

Currently reading about #yggdrasil network to think about possible integration in #atomique.  Unlike Tor the goal isn't  anonimity. Just decentrazling communication between hosts.

And I want to make this easy like maybe cacher a list of public peers from https://publicpeers.neilalexander.dev/ and let the system get a json to get the closest ones to auto configure from atomique.org

Currently reading about #yggdrasil network to think about possible integration in #atomique.  Unlike Tor the goal isn't  anonimity. Just decentrazling communication between hosts.

And I want to make this easy like maybe cacher a list of public peers from https://publicpeers.neilalexander.dev/ and let the system get a json to get the closest ones to auto configure from atomique.org

Could somebody please create HTTPS nginx proxy to our #Blossom server http://[302:68d0:f0d5:b88d::bdb] ( #Yggdrasil ) to make it accessible from the Internet?

There is also #Mycelium gateway http://[505:6847:c778:61a1::bdb] that could be useful as the fallback and may work faster.

PR to whitelist to add your #nostr account: https://codeberg.org/YGGverse/server/src/branch/main/etc/route96/whitelist.txt

Could somebody please create HTTPS nginx proxy to our #Blossom server http://[302:68d0:f0d5:b88d::bdb] ( #Yggdrasil ) to make it accessible from the Internet?

There is also #Mycelium gateway http://[505:6847:c778:61a1::bdb] that could be useful as the fallback and may work faster.

PR to whitelist to add your #nostr account: https://codeberg.org/YGGverse/server/src/branch/main/etc/route96/whitelist.txt

Playing around #nostube (YouTube alternative via #nostr / #blossom ecosystem)

http://[302:68d0:f0d5:b88d::2be] - #Yggdrasil
http://[505:6847:c778:61a1::2be] - #Mycelium

At this moment there is mixed connections out of the box; Take a look also at our Blossom server (mention to witelist your npub)

http://[302:68d0:f0d5:b88d::bdb]
http://[505:6847:c778:61a1::bdb]

#tor, #yggdrasil, and #i2p walk into a bar...

how does this joke go?

#tor, #yggdrasil, and #i2p walk into a bar...

how does this joke go?

#tor, #yggdrasil, and #i2p walk into a bar...

how does this joke go?

#Yggdrasil private exit node. #Yggstack + dns64 + nat64 https://github.com/DrewCyber/ydn64

Yet another #Tor bridge for #Yggdrasil network https://github.com/yggdrasil-network/yggdrasil-network.github.io/pull/342/changes/b98bdfbcb4762006f966a990267a018921f11ef3

Yet another #Tor bridge for #Yggdrasil network https://github.com/yggdrasil-network/yggdrasil-network.github.io/pull/342/changes/b98bdfbcb4762006f966a990267a018921f11ef3

Yet another #Tor bridge for #Yggdrasil network https://github.com/yggdrasil-network/yggdrasil-network.github.io/pull/342/changes/b98bdfbcb4762006f966a990267a018921f11ef3

Insolvenz bei Spielecafé #Yggdrasil in Kiel: „Bis September muss Lösung her“

https://www.kn-online.de/lokales/kiel/insolvenz-bei-spielecafe-yggdrasil-in-kiel-bis-september-muss-loesung-her-UGI2KQPHOJFVLNSWI72YEA4TEY.html

> Kurz nach einer großzügigen Spielespende an die Jugendarbeit der Stadt Kiel musste das Spielecafé Yggdrasil Insolvenz anmelden. Der Inhaber wollte sich vom Spieleverkauf trennen und sich auf den Cafébetrieb konzentrieren

Weird

#Kiel

Insolvenz bei Spielecafé #Yggdrasil in Kiel: „Bis September muss Lösung her“

https://www.kn-online.de/lokales/kiel/insolvenz-bei-spielecafe-yggdrasil-in-kiel-bis-september-muss-loesung-her-UGI2KQPHOJFVLNSWI72YEA4TEY.html

> Kurz nach einer großzügigen Spielespende an die Jugendarbeit der Stadt Kiel musste das Spielecafé Yggdrasil Insolvenz anmelden. Der Inhaber wollte sich vom Spieleverkauf trennen und sich auf den Cafébetrieb konzentrieren

Weird

#Kiel

Insolvenz bei Spielecafé #Yggdrasil in Kiel: „Bis September muss Lösung her“

https://www.kn-online.de/lokales/kiel/insolvenz-bei-spielecafe-yggdrasil-in-kiel-bis-september-muss-loesung-her-UGI2KQPHOJFVLNSWI72YEA4TEY.html

> Kurz nach einer großzügigen Spielespende an die Jugendarbeit der Stadt Kiel musste das Spielecafé Yggdrasil Insolvenz anmelden. Der Inhaber wollte sich vom Spieleverkauf trennen und sich auf den Cafébetrieb konzentrieren

Weird

#Kiel

Insolvenz bei Spielecafé #Yggdrasil in Kiel: „Bis September muss Lösung her“

https://www.kn-online.de/lokales/kiel/insolvenz-bei-spielecafe-yggdrasil-in-kiel-bis-september-muss-loesung-her-UGI2KQPHOJFVLNSWI72YEA4TEY.html

> Kurz nach einer großzügigen Spielespende an die Jugendarbeit der Stadt Kiel musste das Spielecafé Yggdrasil Insolvenz anmelden. Der Inhaber wollte sich vom Spieleverkauf trennen und sich auf den Cafébetrieb konzentrieren

Weird

#Kiel

#barev protocol in maemo-leste

https://leste.maemo.org/Extras/Barev
gemini://bbs.geminispace.org/s/Yggdrasil/45714

#Yggdrasil

Aker BP narrows 2026 production guidance as major Norway projects advance https://www.byteseu.com/2197943/ #AkerBP #AkerBPQ22026 #Equinor #JohanSverdrupPhase3 #NorthSea #Norway #NorwayOffshore #NorwegianContinentalShelf #OffshoreDevelopment #OilProduction #ProductionGuidance #SkarvSatellites #UpstreamOilAndGas #ValhallPWPFenris #WorldOil #Yggdrasil

Вчера потребовался iso образ ArchLinux и оказалось, что в зеркале, который я поддерживаю в #yggdrasil, эти файлы не копируются. Папка исключена была. Исправил и по /iso/ теперь лежат свежие образы. Если у кого с доступами в пакетам и iso будет проблема, можно взять там.

Есть мысль и #endeavour так же зеркалировать, но пока руки не дошли и не знаю, есть ли там открытый rsync.

Вчера потребовался iso образ ArchLinux и оказалось, что в зеркале, который я поддерживаю в #yggdrasil, эти файлы не копируются. Папка исключена была. Исправил и по /iso/ теперь лежат свежие образы. Если у кого с доступами в пакетам и iso будет проблема, можно взять там.

Есть мысль и #endeavour так же зеркалировать, но пока руки не дошли и не знаю, есть ли там открытый rsync.

Das Bild ist eine detaillierte und kunstvolle Darstellung von #Yggdrasil, dem Weltenbaum, aus der nordischen Mythologie, umgeben von verschiedenen symbolischen Elementen und erläuternden Texten. Der Stil ist illustrativ und erinnert an alte wissenschaftliche oder mythologische Abhandlungen.

Im Zentrum des Bildes steht ein massiver, alter Baum mit weit ausladenden Ästen und Wurzeln. Der Baumstamm ist grob und mit Furchen durchzogen, was sein hohes Alter und seine Stärke betont. Aus den Ästen hängen zahlreiche kleine, versiegelte Briefe oder Pakete, die miteinander verbunden sind und eine Art Kommunikationsnetzwerk darstellen. Die Blätter des Baumes sind in satten Grüntönen gehalten, mit einigen helleren und dunkleren Nuancen, die Tiefe und Textur erzeugen.

Auf den Ästen und um den Baum herum sind verschiedene Tiere abgebildet:

Oben auf einem Ast sitzt ein majestätischer Adler mit weit ausgebreiteten Flügeln, der in den Himmel blickt. Neben ihm flattert ein Falke. Weiter unten auf den Ästen tummeln sich Eichhörnchen, die eifrig mit den Briefen interagieren. Eine Krähe sitzt auf einem Ast und schaut nach unten, in der Nähe einer Darstellung von Huginn & Muninn.

Am Fuße des Baumes sind mehrere Hirsche zu sehen, die friedlich grasen. Sie scheinen Teil der natürlichen Umgebung des Baumes zu sein.

Am Stamm des Baumes, im unteren rechten Bereich, steht ein Wolf, der die Szene ruhig beobachtet. Seine Präsenz strahlt eine gewisse Ernsthaftigkeit aus. Daneben ist ein Grabstein mit der Inschrift "Memento Mori" platziert, was auf Vergänglichkeit und Erinnerung hinweist.

Im unteren linken Bereich des Stammes ist eine Schlange mit einem Hut mit einem "T" darauf in einer Erdhöhle dargestellt. Dies könnte Nidhöggr symbolisieren.

Weiter unten sind mehrere Schlangen in verschiedenen Größen und Farben dargestellt, die sich winden. Dies wird mit den Konzepten Gier, Geltungssucht und Geiz assoziiert.

Zwischen den Wurzeln des Baumes werden auch andere Elemente dargestellt:

In der unteren linken Ecke liegt ein Stapel alter, verschnürter Papiere oder Bücher, die mit einem Siegel versehen sind, auf dem eine kleine Fliege oder ein Käfer abgebildet ist. Dies scheint einen Aspekt der Weisheit oder der Archivierung zu repräsentieren.

Unterhalb der Darstellung der Schlangen befindet sich ein Kompass mit den Himmelsrichtungen und weiteren Symbolen: ein Briefumschlag, ein Blatt, ein Zweig und ein Baumstumpf. Diese Symbole werden mit verschiedenen Begriffen wie "Orientierung", "Nachricht", "Leben" und "Stabilität" in Verbindung gebracht.

Die Farbpalette ist überwiegend warm und erdig, mit vielen Braun-, Grün- und Beigetönen. Die Farben sind gedämpft und verleihen dem Bild eine alte, fast historische Anmutung. Der Hintergrund ist ein pergamentfarbener, leicht gemaserter Ton, der das Gefühl eines alten Dokuments verstärkt.

Die Komposition ist symmetrisch und ausgewogen, mit dem Weltenbaum als klarem Zentrum. Die Tiere und Symbole sind geschickt um den Baum herum platziert, um die verschiedenen Aspekte seiner Bedeutung zu illustrieren. Die Texte, die in verschiedenen Abschnitten um die Illustration herum angeordnet sind, erklären die dargestellten Elemente und Konzepte. Die Schrift ist in einer dekorativen, leicht geschwungenen Schriftart gehalten.

Die Gesamtkomposition vermittelt ein Gefühl von Harmonie, Weisheit und der tiefen Verbindung zwischen dem Leben, dem Kosmos und der menschlichen Existenz. Die Details, wie die feine Ausarbeitung der Tiere, die Texturen des Baumes und die feinen Linien der Illustration, zeugen von hoher künstlerischer Handwerkskunst.

3/3 …Et bien, sans internet, directement de device à device, ça marche
Alors disons que sur un campus sans Internet de Proxima du Centaure, vous avez une 50aine de hotspots wifis, cablés entre eux par ethernet, qui sont sous un Vrai OS™ comme #OpenWRT et ont tous #Yggdrasil, ils vont automagiquement s'interconnecter (autopeering). Et tous les téléphones, les dizaines, centaines, de téléphones clients de ces points d'accès, avec leur Yggdrasil, leur DeltaChat, seront tous mutuellement joignables.

Our #Blossom backend server changed from blossom-rs to #route96
https://github.com/v0l/route96

WebUI: http://[302:68d0:f0d5:b88d::bdb]
* #Yggdrasil, same for #Mycelium and #I2P - shared storage

The member list location changed to
https://codeberg.org/YGGverse/server/src/commit/bf4b7b90a7ba046bfdc5c88f42eb82dea01cb557/etc/route96/whitelist.txt

#Rust #nostr

На сайте Публичного пира сетей #I2P и #Yggdrasil есть страничка про Fediverse.
https://publicpeer.ru.eu.org/news.html

Там, помимо прочего, сказано про отличие #Fediverse от централизованных социальных сетей; как выбрать #инстанс #Mastodon (пара десятков ссылок), #зарегистрироваться на выбранном инстансе, заполнить свой профиль.

Если вы хотите #рассказать своим знакомым или читателям про Fediverse, дайте им эту ссылку.

@russian_mastodon @rf @Russia #соцсети #сеть #сети #Интернет #publicpeer #tech #technology

На сайте Публичного пира сетей #I2P и #Yggdrasil есть страничка про Fediverse.
https://publicpeer.ru.eu.org/news.html

Там, помимо прочего, сказано про отличие #Fediverse от централизованных социальных сетей; как выбрать #инстанс #Mastodon (пара десятков ссылок), #зарегистрироваться на выбранном инстансе, заполнить свой профиль.

Если вы хотите #рассказать своим знакомым или читателям про Fediverse, дайте им эту ссылку.

@russian_mastodon @rf @Russia #соцсети #сеть #сети #Интернет #publicpeer #tech #technology

На сайте Публичного пира сетей #I2P и #Yggdrasil есть страничка про Fediverse.
https://publicpeer.ru.eu.org/news.html

Там, помимо прочего, сказано про отличие #Fediverse от централизованных социальных сетей; как выбрать #инстанс #Mastodon (пара десятков ссылок), #зарегистрироваться на выбранном инстансе, заполнить свой профиль.

Если вы хотите #рассказать своим знакомым или читателям про Fediverse, дайте им эту ссылку.

@russian_mastodon @rf @Russia #соцсети #сеть #сети #Интернет #publicpeer #tech #technology

На сайте Публичного пира сетей #I2P и #Yggdrasil есть страничка про Fediverse.
https://publicpeer.ru.eu.org/news.html

Там, помимо прочего, сказано про отличие #Fediverse от централизованных социальных сетей; как выбрать #инстанс #Mastodon (пара десятков ссылок), #зарегистрироваться на выбранном инстансе, заполнить свой профиль.

Если вы хотите #рассказать своим знакомым или читателям про Fediverse, дайте им эту ссылку.

@russian_mastodon @rf @Russia #соцсети #сеть #сети #Интернет #publicpeer #tech #technology

7 channels from https://radio.miliukhin.xyz #radio is now on #Pidpilne (unofficial cast)

http://mrkssh4b2qkrf5hl4yxrwbtuowbmjugozaa7emaybnokw5jtcydq.b32.i2p - #I2P
http://[202:68d0:f0d5:b88d:1d1a:555e:2f6b:3148]:8000 - #Yggdrasil
http://[505:6847:c778:61a1:5c6d:e802:d291:8191]:8000 - #Mycelium