Enter an ArNS name and open the website without being redirected to a domain address. 🌐 I’m developing Mesh to make ArNS content more accessible and strengthen its availability during disruptions. Today, Mesh is a working Windows desktop application. You can enter an ArNS name like ar://vevivo in the address bar, and the application retrieves, verifies, and opens the content directly over IP, without redirecting you to another domain address. Development is ongoing. ArNS Search is a separate discovery feature: You can search for a topic or keyword, discover relevant ArNS names, and open their websites by clicking the results. Descriptions, keywords, and information extracted from prepared pages help make content discoverable. Supporter nodes prepare content in the background without waiting for users to visit a website. During normal operation, they continuously monitor new ArNS registrations and content updates, refresh the search catalogue, and download, verify, and retain files from newer versions. This automated preparation operates within configured storage and bandwidth limits, preserving previously prepared copies until newer versions are ready. Mesh also benefits from ario’s Index Sharing infrastructure. By using shared, signed CDB64 indexes, supporters can locate covered Arweave files through their locally stored indexes. This reduces the discovery work needed to find content locations. Mesh then retrieves, verifies, and retains the actual files. But what if DNS and domain-based access became unavailable worldwide? This is where Mesh’s core mission comes into play: keeping ArNS content accessible as long as IP connectivity between Mesh participants remains available. Even if Solana RPC and direct #Arweave access also become unavailable, supporter nodes can continue serving previously prepared ArNS records and verified files to Mesh users. Losing access to new data does not mean losing access to the data already preserved. When all live upstream sources become unreachable, Mesh can serve the latest successfully prepared versions available before the disruption. Users do not need to have downloaded those websites to their own devices beforehand. This behavior has already been demonstrated with selected, prepared content in controlled tests where external connectivity was blocked. It is not a claim that every website would remain functional during a global outage, but a concrete result demonstrating that the underlying mechanism works. My long-term goal is to make Mesh increasingly decentralized through independent supporters operated by different people across different networks. I want to strengthen a system where ArNS names and content are continuously kept up to date, and where other supporters can continue providing access if one server goes offline. Downloading and testing Mesh before a potential disruption is also part of being prepared. I’d really appreciate feedback from anyone willing to try Mesh on Windows. Your experiences with ArNS Search, websites that open or fail to load, and any issues you encounter would be extremely valuable for development. Contributions from people interested in running independent supporter nodes would also be greatly appreciated. 🙌 I’d also especially welcome honest, constructive, and technically grounded criticism from experienced developers and researchers. If I’ve overlooked a fundamental technical limitation, or if the approach I’m pursuing cannot realistically achieve its intended goals, please tell me. I don’t want to blindly hold on to an idea. My goal is to contribute something genuinely useful to ArNS. If that means reconsidering my approach or directing my energy toward a more valuable solution, I’d sincerely appreciate your guidance. More ways to access content. A more resilient ArNS experience. Code, downloads, and setup: github.com/Vevivo/arns-mesh

A small update for fellow Permabulls running @ar_io_network gateways: Certificate expiry tracking now also shows domain expiration dates as an additional reference. SSL certificate countdowns remain the main focus. A little more visibility, one less thing to forget. certs_vevivo.ar.io