ao Computer Club

ao enables compute at any scale. ao Computer Club is for inventors and wild thinkers. Welcome. You're one of us if you're reading this. NFA.

[ao Computer Club @aoComputerClub]

Reply handling got lighter as well.

Responses can now be built without triggering some unnecessary data loading behind the scenes.

All of these updates make the system more efficient and polished as a builder. Great to see!

[ao Computer Club @aoComputerClub]

AO progress this week already has focused on making HyperBEAM (node infra!) more predictable during normal node operation.

The updates include device handling, message processing, and replies.

[ao Computer Club @aoComputerClub]

Cookie handling was also upgraded and optimized.

HyperBEAM now loads only the information it needs instead of pulling in extra message data.

Efficiency improvements continue :)

[ao @aoTheComputer]

The first phase of Permaweb Names is live: if you ever owned or rented ArNS, ANS, and ArProfile names you have now received control of an AO message which will allow you to change the data that name points to.

There will be no lease or future registration fees for these names in the future -- they are permanent.

14,624 names from legacy services have now been made resolvable on https://t.co/f2buk8NsKN and other HyperBEAM-powered gateways. Transfers, registrations, and a market will go live in the coming days.

Dashboard: https://t.co/spTOYmHQOx

https://t.co/zaBGWwmt6p

[ao Computer Club @aoComputerClub]

The AO stack is becoming easier to work with in the places that matter.

Build it.
Debug it.
Run it.
Rely on it.

There’s more to do and these new components are in alpha. Cheers to all making this happen and those supporting these efforts.

[ao Computer Club @aoComputerClub]

Great week of practical @aoTheComputer progress.

A lot of the work points toward the LapEE idea: making powerful infrastructure easier to build, run, and rely on.

[ao Computer Club @aoComputerClub]

And now, LapEE.

LapEE makes us HapEE.

It’s making it possible to run gnarly infrastructure on like $100 laptops🔋

[xy.ar 🐘 @xylophonezy]

LapEE is your own sovereign permaweb node, which works out of the box, and comes set up with smart defaults to verifiably read and write from Arweave.

If you booted one up yesterday, here's a guide on what you can do with it.

https://t.co/zgYwX35pvI

[ao Computer Club @aoComputerClub]

@opusluxofficial @aoTheComputer haha 😅

[ao Computer Club @aoComputerClub]

@opusluxofficial @aoTheComputer LAPIDL 💻

[xy.ar 🐘 @xylophonezy]

LapEE is your own sovereign permaweb node, which works out of the box, and comes set up with smart defaults to verifiably read and write from Arweave.

If you booted one up yesterday, here's a guide on what you can do with it.

https://t.co/zgYwX35pvI

[ao Computer Club @aoComputerClub]

👀

[🐘🔗 sam.arweave.dev @samecwilliams]

Running permawebOS

[ao Computer Club @aoComputerClub]

@aoTheComputer is continuing to form into something anyone can build upon:

A focused core runtime. A hardware aware operating layer. Sharper message checks.

Great to see!

[ao Computer Club @aoComputerClub]

And the progress continues :).

AO’s stack is getting more clearly shaped.

Machine specific pieces are moving out of HyperBEAM and into PermawebOS.

HyperBEAM focused on the core AO runtime, while PermawebOS handles more of the “how do we run this on actual hardware?” side.

[ao Computer Club @aoComputerClub]

There's also a message checking improvement, which is significant as AO is all about message passing!

AO messages can get nested and can be complex.

The new matching work lets deeper parts of a message choose how strict comparisons should be.

Cleaner tests and fewer edge cases 🤝

[xy.ar 🐘 @xylophonezy]

boot from USB -> run a laptop with HyperBEAM as the OS

This $100 laptop is a decentralized bundler, tamper-resistant and provable end-to end

Setup guides (beware, alpha release): https://t.co/CctvXUj9mv