"THE NOMAD INDEX" — Nomadnet Nodes Index & Search Engine

THE NOMAD INDEX is a Nomadnet Node that runs on a VPS and works as an address collector (indexer) for the Nomadnet Nodes.

You can consider it as "the nomadnet white pages". It features also an exclusive Nomadnet Search Engine derived from

the rBrowser, standalone nomadnet browser project. (Get rBrowser at: https://github.com/fr33n0w/rBrowser)

The Nomad Index It's composed by two main parts,

— The Backend script that connects to Reticulum and automatically listens for incoming Nomadnet announces:

It runs on a VPS server for 24/7 availability and is connected to Reticulum Testnets and few other Private TCP Interfaces

with transport enabled, to collect and list the most possible number of nodes announced on the NomadNetwork.

It also automatically caches the index.mu page locally, from any found node,

to be consulted later with the Search Engine research feature (more info below).

NOTE: To avoid unnecessary traffic to remote nodes, especially if they are possibly connected to Rnode LoRa interfaces,

only the index.mu page is cached and only for the first time the announce is received,

no other traffic is generated toward your node after the first page cache,

that is like a single user client, visitng your page just one time only.

— The Frontend part that is the current user UI, reachable from Nomad Network clients (Nomadnet, MeshChat, rBrowser).

More usage info below, keep reading :)

In the MAIN MENU, positioned on the top part of every pages, you have access to the following pages:

HomePage

The intro page with The Nomad Index Logo and Search Engine feature, follow links to access the main UI.

The Nomad Index Modern UI

The listing index page for announced nomadnet nodes, using Modern User Interface theme.

The Nomad Index Classic UI

The listing index page for announced nomadnet nodes, using Classic User Interface theme.

Search Engine

The Nomadnet Search Engine page to search for nodes, in names, address and page content.

Scroller

New experimental function to scroll within random node pages without leaving The Index

(Visualized pages are extracted from cache so can be old, visit the original node for new content)

About

Informations and Quick Start Guide About The Nomad Index. This page.

The access to the SEARCH ENGINE feature is also served in every page, under the logo.

Entering The Nomad Index page, you have immediate access to the node listing table.

The default Modern UI is the main node listing page, you can switch to Classic UI theme from the top menu,

choose the user UI that you like the most for improved readability.

Modern UI: Clean layout with color-coded announce freshness and clickable node pages links to visit the page

Classic UI: Terminal-style table with fixed-width formatting and ASCII separators, clickable links to visit the page.

This page displays all known NomadNet nodes that have announced themselves to the network via our list of tcpinterfaces.

Each node represents a decentralized peer, service, or content source.

The index updates dynamically on page reload and supports multiple sorting modes and statistics.

Sorting Options:

Sort the node list using the links at the top or bottom of the page UI:

🕒 Most Recent — order nodes by newest announcements first.

📦 Original Announce Order — list nodes ordering them as originally received via announces.

🔤 Alphabetical — order node list by alphabetical A to Z name.

📣 Most Announced — order nodes by the most active on top.

📉 Least Announced — order nodes by most quieter on top.

Statisticss:

At the bottom of the Index page and in the Search Engine page, you’ll find:

Total number of nodes listed

Total number of announces received

Number of cached nodes (percentage of cached nodes versus the total received)

The main listing table is formed by the following rows:

Node # : The indexing number of a node row (only in the Modern UI)

Node Name: Human-readable name of the node as announced by the user (32 chars limited name display fo fit table).

Node Hash Address: Unique nomad node address identifier, it's also a clickable link to visit the node’s page.

Last Heard: Timestamp of the most recent announcement from that correspinding node, color-coded by freshness

Announces: Total number of times the node has announced itself on the network

Cache: Indicates whether the node’s index.mu page has been archived locally for Search Engine results indexing

Last Heard Time Color Coding:

Green: Just Now or X min ago — very fresh (from 0 to 59min)

Yellow: X hr ago — moderately recent (from 1HR to 24HR)

Red: X days ago — older nodes (From 24HR and more)

Red: unknown — timestamp missing or invalid (only in case of errors, not common.)

Cached row possible results:

✅ : The page is cached and searchable by users from the Search Engine (announce received, page responding, cached)

❌ : The page announce is retrieved, but it was impossible to cache it (node was unreachable at the moment of caching)

**Only reachable nodes with a valid and accessible index.mu page are eligible for caching.

Visiting Listed Nodes:

Each listed node address is a clickable link. Click to open the node’s index.mu page.

There is an additional Go button at the end of the table to visit the node page index.mu

The exclusive Nomadnet Search Engine feature allows keyword-based search across node content,

enabling the discovery of new services, forums, and resources across the Nomad Network.

This feature will make it easier to explore the network and find relevant nodes — even if you don’t know their hash or name.

You can find the Search Engine Bar in every page of this node, after the ascii logo, for easy access.

Search results includes: found terms, node name, hash, snippet of the page, link to navigate to the found resources.

List of most searched terms in the search page and more features comeing soon!

New experimental feature since 20/10/2025: Random Page Scroller

Use this page, reachable from the home or the scroller link in the top menu to browser within cached pages

without leaving the main index node site. It's similar to the most famous "I feel lucky" function ;)

Navigate through random pages to discover new interesting contents.

The displayed pages contain all the node info and the original link to visit them.

Content is visualized from the cached pages, so the content can be old due to one-time-only caching, to avoid useless traffic.

If you are interested in a page content, visit the original page address following the "Visit Page" link.

If you run a NomadNet node, make sure it announces itself properly and includes a valid index.mu page,

our node index list contains the nodes received from our configured tcpinterfaces.

If your node doesnt'appear here, send a message to the LXMF address below and include:

the node name, node address and your actual tcpinterface to connect our system ti it,

for receiving announces and live node info to update your node in the indexing page.

We will promptly add your node to the list and let the Nomad Network grow! :)

You’re also welcome to suggest improvements to the layout, features, or sorting logic etc,

you can find the contacts address at the end of this page.

The backend script collects and index all the received announces from our tcpinterfaces automatically.

Data collected from nodes: Node Name, Node Hash, Announce Time, index.mu page content (if page is reachable)

No personal data or lxmf addres that can trace to you are collected in any way.

If you want to remove your node from the list, just contact the op at the LXMF address found below,

and include the node name and the node address and we will promptly remove you node from listing and search engine cache.

Data collected from nodes: Node Name, Node Hash, Announce Time, index.mu page content (if page is reachable)

This page is rendered using pure Python and Micron markup

All formatting is fixed-width for (almost) pixel-perfect alignment

No external templates or rendering engines are used — just rint()statements

All links and styles are compatible with MeshChat , NomadNet and rBrowser clients.

IMPORTANT NOTICE FOR WHO IS WORRIED ABOUT TRAFFIC USAGE FROM THE PAGE CACHING FUNCTION:

All my projects are made considering the Reticulum philosophy of low bandwidth - low traffic usage.

The remote pages (aka: the index.mu of your node) are cached only 1 time and only if they are not already present in the DB.

This means that this index node does not generate mutch traffic to your node in any way!

The caching process correspond to a single client visiting the index.mu page of your node, 1 time only.

So: No bandwidth waste if you are connected also via lora, no traffic generation, just one single visit to your page.

Sorry for the repetition on how this works, but peopple are asking alway the same thing. Hope this time was clear.

**************************************************************************************************************

** At the moment, to avoid huge traffic to nodes if used by many people, i will not share the project code. **

** You can consult The Index & Search Engine from this Nomadnet Node page, at the official address. **

** The Nomad Index: 47850a3b99243cfb1147e8856bab2691:/page/index.mu **

**************************************************************************************************************

For any info,question, suggestions, feel free to contact me at LXMF address:

0d051f3b6f844380c3e0c5d14e37fac8

───────────────────────────────────────────────────────────────────────────────────────────────