ar://HeyGoAudio |James| ⓐ

$AR $ARIO #BrokenRecord #Music #DePIN #NeuroSpicy🌶️🧠 Find me on🦋, send music🚀 #PermaWeb #OpenFi

[ar.io @ar_io_network]

Gateway Release 86 is out, and it's an important security release.

It moves gateways to Node.js 22.23.4, fixing a Brotli remote code execution bug (CVE-2026-111497) along with Node's TLS and DNS fixes.

Operators, please upgrade today!!

https://t.co/DKq5t8bMGN

[ar://HeyGoAudio |James| ⓐ @HeyGoAudio]

@jasondesante 👀

[Jason @jasondesante]

I can now search for all the steel drum music nfts and then listen to a bunch of steel drum music

[ar://HeyGoAudio |James| ⓐ @HeyGoAudio]

If you experienced the emergence of Web3 you know that ownership, trust + freedom are at the core of human need.
Today, it hit me (fkn hard) that nobody can believe in something they don't own.

Everyone should own:
•Their identity
•Free expression
•Community
It's that simple.

[ar://HeyGoAudio |James| ⓐ @HeyGoAudio]

#Arweave fam trying to figure out what "PHP" is..

[Derek Devicemanager @IT_unhinged]

Security called me at 6:12 AM today.

"Patch every PHP server immediately."

I asked what happened.

"Two critical vulnerabilities. Remote code execution. No authentication required."

Cool.

How many PHP servers do we have?

According to inventory: 12

According to reality:

Nobody knows.

We found one running WordPress.

Three running old internal tools.

One under someone's desk.

Two inside vendor appliances.

A forgotten employee directory from 2016.

And a server named:

PHP-OLD-DO-NOT-TOUCH

Naturally, that one runs payroll exports.

Then we found a PHP 5.6 box.

I asked who owned it.

The documentation said:

BRIAN.

Brian left in 2019.

We called Brian.

He said:

"Oh wow, that's still running?"

Excellent.

By 8 AM, leadership joined the incident call.

CEO:

"Can hackers actually get in?"

Security:

"Potentially yes."

CEO:

"Without a password?"

Security:

"Yes."

CEO:

"Then why do WE need passwords?"

Not the lesson.

Finance asked if we could wait until the weekend to patch because downtime affects revenue.

Security explained that the alternative was letting strangers execute code on our servers.

Finance asked for a cost comparison.

At 9:17, someone suggested temporarily taking the vulnerable websites offline.

Marketing refused.

"Our campaign is live."

So for the next hour, the company officially decided maintaining a landing page for 20% off webinar registration was more important than preventing remote server takeover.

We finally patched everything we could find.

Then our scanner discovered another PHP server.

Hostname:

TEMP-PHP-2014

Uptime:

4,512 days.

Nobody knows what it does.

Nobody owns it.

Nobody can shut it down.

But every time we block network access, the warehouse stops printing shipping labels.

Security has classified it as critical infrastructure.

It is running PHP 5.4.

The vulnerability has existed longer than half our employees.

The emergency patch took four hours.

Finding out what PHP actually runs took eleven.

The internet isn't held together with code.

It's held together with servers everyone is afraid to turn off.

[ar://HeyGoAudio |James| ⓐ @HeyGoAudio]

"Your contact joined Telegram!"
... in 2026?

[𝚊𝚛://𝚟𝚎𝚟𝚒𝚟𝚘 🐘 @vevivoofficial]

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:
https://t.co/kJ4PpTDZfC

[ar://HeyGoAudio |James| ⓐ @HeyGoAudio]

@BristowEwan SURELY it has to be a palindrome?
Like morph / reform / blend IDK

MORFROM?
ROFOR?

[🐘🔗 ar://vilenarios @vilenarios]

wait wait wait

so you're telling me there's a hard drive that exists everywhere and nowhere, that no single person or company owns or controls, that anyone in the world can write to without asking permission, where you pay once and the data is built to outlive you, where nothing written can be deleted or quietly changed, that's been running continuously since 2018, that already holds billions of files and serves billions of requests a day, where a website, a dataset or a whole app lives at an address that never moves, served by gateways run by strangers who check each other's work instead of trusting each other, where anyone can put a name on their data and point it anywhere, where your files don't depend on some company staying in business, that has no renewal date, no landlord and no delete button?

nice.

[🐘🔗 ar://vilenarios @vilenarios]

We put a SQL database (DuckDB) in a browser tab, loaded it from Arweave via ArNS, and pointed it at an index two gateways built separately.

Can the permanent data analysts out there find any gems? Its v0.1 so be gentle.🤓

[ar://HeyGoAudio |James| ⓐ @HeyGoAudio]

@sweetmantech Would be really interested to see if you come across any info/transparency from actual DSPs 💯👀

[ar://HeyGoAudio |James| ⓐ @HeyGoAudio]

@ArNS_Alerts @MattJohnsonNFTs ? 👀🤝

[ar://HeyGoAudio |James| ⓐ @HeyGoAudio]

@ArNS_Alerts 👀👀👀

[Matt Pocock @mattpocockuk]

This is what having a popular open source project feels like ~50% of the time

[ar://HeyGoAudio |James| ⓐ @HeyGoAudio]

@ArNS_Alerts

[ar.io @ar_io_network]

ar-io-deploy 2.0 is live 🚀

Ship to @ArweaveEco for less: --compress gzip shrinks text assets 3–5x, and --incremental means redeploys only pay for what changed, even from a fresh CI runner.

Plus Turbo SDK 2, shared credits and capped on-demand top-ups.

https://t.co/nKCuIAtYCA

[ar://HeyGoAudio |James| ⓐ @HeyGoAudio]

Dear Tech Oligarchs,

Let's make a deal.
All you have to do is turn off the algorithms and leave. Nothing bad will happen to you.

To be clear:
✅Turn algo OFF
✅Leave lights ON
✅RUN

Trust me bro, a comfy bunker is your best option. They know.

Sincerely,
People on the internet

[𝚊𝚛://𝚟𝚎𝚟𝚒𝚟𝚘 🐘 @vevivoofficial]

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.

https://t.co/4MVKQ6SxRo

[Haven @CryptosHaven]

Arweavers 🐘 shall we start a campaign?

arweave:native