Doing as little as possible in the runtime makes a lot of sense. Less overhead, less to maintain, etc.

As for the freshness, I was originally thinking perhaps latency sensitive function calls might pose a problem if the process crashes and recovers seconds later and responds with data that’s no longer relevant. Given these are pure functions it makes total sense to just pass along the timestamp (or increment a counter) and these considerations are going to be app dependent anyway.

I’m really excited about this project and plan to experiment with it in the near future. The docs are well written too. Thank you for the work and the thoughtful response!

Thinking more in this: since functions treat memory and storage interchangeably and can be restarted at arbitrary points then does state have timestamps as a first class citizen? Meaning: if my function is sensitive to data freshness then can I easily discern fresh from stale?

Function* state

This is awesome! I’ll need to spend more time digging in later.

So you persist funding state, can send state over the wire to be continued elsewhere, and can run processes in parallel. So this can be a distributed runtime?

Decentralized HPC could work well with this design…

There are several docker images out there which lowers the barrier somewhat.

We could also create a dedicated raspberry pi distro.

We could also create scripts to set up VMs within cloud providers.

There are a lot of technically savvy people that we can lean on for this.

Sigh. It always rebounds by pay day 😞. The 52k sats were too good to last.

To all front end devs: if your product team wants you to put half a dozen modals on your landing page then please push back. We shouldn’t have to click several Xs just to read the content.

Every day I see the progress being made in our community is a reminder that I don’t have enough bitcoin.

Keep stacking y’all!

We need to align the incentives of relays with those of the consumers or we’ll have the same predatory models evolve here too.

Consumers are accustomed to getting “free” services. The relays who can cater to that habit by monetizing their consumption without charging them directly will have an economic advantage. We can fix this, and I’m optimistic, but not sure how to do it.

Discipline is under appreciated

Agreed it would be nice if there was an open version of obsidian. The silver lining is that at least we can keep the markdown files in git. Haven’t heard of zettlr before, but looks interesting!

+1 for zettlekastin. What do you use? I’ve been using obsidian for a few years now and enjoy it.

Just realized I responded to the wrong note 😅. Thank you ❤️⚡️

Someone beat me to my nym’s GitHub handle by 4 years. And here I thought I was original. Well played other Machu. Guess I’ll add the “BTC” suffix.

Mic check. Is this thing on? https://boardwalkcash.com/machupikacchu

Open source decentralized AI training. Coming soon to Nostr?

https://github.com/PrimeIntellect-ai/OpenDiloco

Hypothetically they could collect fees from the guardians periodically. Or if we can figure out how to federate the lightning node itself then each of the guardians could be partially responsible. Mints need to collect fees over time anyway or else they’re incentivized to rug and/or quit.

My understanding is that you can’t have multiple lightning nodes using the same key or you get unpredictable behavior. Maybe that’s just for routing nodes?

I wonder if we could somehow shard the private key using FROST so that outbound payments are still federated? I’m out of my depth on this one.

Who would manage the lightning gateway?

What role does she think stable channels will play in international trade.

Given the recent talks about a US bitcoin reserve it makes sense for the Fed and/or Treasury to set up stable channels, print dollars, and have sats flow to their side of the channel.