The main holdup with massive solar in the desert is the national electrical transmission backbone that would be the equivalent of the highway or rail systems.

My understanding is that there is a lot of loss and we could save a bunch of energy(and above) by doing like the interstate highway buildout

when do launch costs become less than permitting and bureaucracy costs?

there is a discord for Roost, I can get a link if you cannot find it

I'm also very open to collaboration on these fronts and more

it's also why I'm building a custom coding agent setup, to bring what I know and have built for deterministic code gen

to move closer to that vibe vision without losing the reliability and maintainability we need in professional software development from keyboard to customer

also always a tinkerer

I've been having the Ai take a few stabs at problems or having multiple work in parallel

I then combine the best of both, what they output and I know

tbh, I wouldn't really rely on these things for important architecture choices that span code and external systems, which is many or most

what happens when it's not a weird nerd who wields this power, or a once revered nerd like elmo/doge?

I'm part way there with: github.com/blebbit/atmu...

it mostly deals with connecting to the atproto network, backfilling, listening to the firehose at this point

next up is feed generation, which I fully intend to build on my recent agent / ADK work, making a labeller of it is not much more after

Are you following @roost.tools?

It's the new home and community for conversations about trust & safety online, many of the who's who in the field are involved as I understand it

for atproto, my first approach would be human/Ai + labelers/lists

The PDS keeps a "record" in the account database of auth sessions (normal sqlite db). This is why you can list and revoke them

no atproto records though

Yes, there is plenty of space right here on earth. The trend has always been towards more efficiency, solar panels and modern nuclear

I think the real advantage for non-Earth space will be avoiding most of the bureaucracy and regulatory costs

One thing I have noticed about coding with Ai, is you see and navigate the code less

there is going to be a palpable loss here to the human

I'm about to give my Ai a new toy for xmas, access to LSP so it can call tools like refactor and lookup def

My ai will use sed too, though I prefer it use the edit tool directly, it's much simpler and good enough (occam's) at reducing complexity for the agent

Tool crafting is underrated

one curiosity about this situation on @bsky.app is that you can craft pro-ai posts that do well with the anti-ai crowd

1. you make a complaint about ai based on actual experience
2. you make it a two parter where you are clearly not anti-ai

I get an amount of pleasure in them liking ai peep posts

they write bad code and are slower, sometimes

other times they write code I couldn't have (because I didn't know) or can make small changes to 20 files much faster and easier than me, and I can look at the combined diff faster

how to wield them to improve this ratio is the skill to learn

do you mean the typical chat interface, if you are using Ai to write code, using an IDE with that chat on the side is the way to go

What my setup looks like now

chat | code & file diffs | git & ai changeset tree

This seems to be working really well now, I'm simply chuffed to bits

github.com/hofstadter-i...

Confirmed, the cloning and splicing appears to work

I usually link commits for transparency, and also because soon I'm going to have my agent analyze these bsky threads I've been making of my work progress

This time though, I'll like to the discussion we've been having on the ADK GitHub, which has a link to the commit

github.com/google/adk-g...