@nprofile1q... here's an example run of a github workflow (.yaml) over nostr.

https://hive-ci.treegaze.com/run/2e616b4c08cd20fee97cd2f0af35fd151868f12a34774d1e2fa8d4b9389d19f5

Loom: Arbitrary command execution, paid with cashu
HiveCI: Leverages Loom to run GitHub actions

The underlying loom job that HiveCI executes: https://loom.treegaze.com/job/87d676b0c7c31846862bcfa3d841a32d2e0cc3abef05d689f4789e71fc139f71

Since I follow you you have permission to use my runner and should be able to login and hit re-run job. (make sure you load up some testnut.cashu.space nuts)

“It’s a machine that rewards coherence, which is why incoherence has never been more precious.”

Brilliant!

For whenever it's your turn today:

🎇 HAPPY NEW YEAR WEIRDO'S! 💜

it's separate from noDNS, but the way I did the capture of the '*.nsite' zone is something i want to bring to noDNS as well. That's something I learned about recently. (easier to deploy in existing systems).

Have you tried restarting the blockchain?

🔊 Showing how to install it and walking through what it's doing.



Example site to test when you have it installed:
http://npub1s0veng2gvfwr62acrxhnqexq76sj6ldg3a5t935jy8e6w3shr5vsnwrmq5.nsite/

@nevent1qvz...

Static site does not equal a 'dumb' website. Nostr clients can be served this way too.

If i have my local relay and blossom server running. I can do everything i want to do while offline. Read my timeline, write responses, publish blogs.

https://gitworkshop.dev/npub1hw6amg8p24ne08c9gdq8hhpqx0t0pwanpae9z25crn7m9uy7yarse465gr/relay.ngit.dev/nsite-deck
Clone & build this + install script. (Careful if you run on something other than ubuntu or have custom dns stuff set up)

Will upload a bit better vid shortly.

I agree, immutable is what i want as well. I realized only after implementing that @npub1ye5pt... just updated the spec. This one still uses the old spec.
nvevent1 in domain name might be tricky as there's a 63 character limit to domains.

One option is to have one immutable event for each version of a site, like a snapshot. And one replacable version of the same event to quickly find the latest version. That way I can 'pin' or rollback any version from my end.

I feel like everything I've learned in the last year is coming together. In an actionable way.

Many failed experiments, quite a few interesting ones that I want to iterate on in 2026.

My focus will be the lower layers, the stuff we've forgotten about because the last 25 years they 'just worked'. The cracks are showing but I think we can fix them.

The first load both caches it AND saves to your local relay/blossom setup.

It comes with embedded relay and blossom. If you have your own configured it will use that instead.

I've tested this on Ubuntu (24) and MacOS (Sonoma) btw.

I want the internet in my pocket.

I was bored and got annoyed with nsites being unreliable/slow. So I vibed together this nsite-deck.

- Load any nsite you've visited before when OFFLINE
- Manage locally stored sites at 'home.nsite'


in the video i show:
- Any [npub].nsite gets resolved, locally
- First load = pull from public relays 30ms
- Second load = load from cache 7ms
- Managing cached sites

Source: nostr://@npub1hw6am.../relay.ngit.dev/nsite-deck

CC @nprofile1q... @nprofile1q... @nprofile1q... @nprofile1q...