Daily Journal 📓

There’s no reason to silo AI chat away from human chat.

• error "components/tryghost-adapter-cache-redis-5.40.1.tgz": Tarball is not in network and can not be located in cache

brew uninstall --ignore-dependencies node
brew uninstall --force node

• brew install nvm

it seems likely to me that all computer users will soon have ability to 1) develop small software tools from scratch, 2) describe changes they’d like made to existing software they’re already using. what will this mean for software ecosystems?? 2/ https://twitter.com/geoffreylitt/status/1637592620888121344

• I think that software built to be user modifiable is going to have the most success with using an LLM to modify it, like #TiddlyWiki
• I’d say #Airtable too… except it’s designed for point and click first.

Report cards are good things and should be designed so nobody can ever coast to good outcomes on them as I did. Good report cards should force you to adapt to a received view of the world that cannot be entirely captured by your nerdy aptitudes, but doesn’t entirely waste nerd energy either.

What if we had social networks that are actually incentivized to help us form complex friendships and groups that work well together over time?

Classes teach you all about advanced topics within CS, from operating systems to machine learning, but there’s one critical subject that’s rarely covered, and is instead left to students to figure out on their own: proficiency with their tools. We’ll teach you how to master the command-line, use a powerful text editor, use fancy features of version control systems, and much more!

Students spend hundreds of hours using these tools over the course of their education (and thousands over their career), so it makes sense to make the experience as fluid and frictionless as possible. Mastering these tools not only enables you to spend less time on figuring out how to bend your tools to your will, but it also lets you solve problems that would previously seem impossibly complex.

@[email protected] To me the very first question is the last one: How do we answer questions? At the moment there is no canonical venue. There’s

1. SocialHub.
2. FEPs, which are kind of sort of tied into SocialHub.
3. Public SWICG mailing list, but it isn’t clear that this has “better domain” than, say, SocialHub.
4. The Mastodon project’s github.
5. Various hashtags on here. It isn’t clear if someone wanted to participate where to do so or what would be involved in that.

I’ve been working on a tricky project to move Val.town’s internals to Deno and adding better isolation between execution and the host environment. Luckily, it feels like we’re in the right place at the right time - there are a lot of new V8 Isolate-based JavaScript runtimes coming to the surface, standards emerging for them like WinterCG, and frameworks built for them like Hono and Remix. The last mile - isolation, code bundling, and communication - is still the wild west, and that’s what I’ve been building.

As a developer, ==you can freely build apps on atproto because open protocols are locked-open APIs==. However, if you just want to introduce another way of showing people posts, or moderating content in the network, we are designing interfaces for you to plug in and do exactly that, accessible through our app. ==If you’re building a new social app, you’ll be able to tap into the social graph and interest graph of atproto users the way you are currently able to bootstrap off of a user’s phone contacts.==

The promise of building an audience on apps built on atproto is that long term, it should become a protocol like email that lets you keep direct connections with people regardless of how the services mediating that relationship change.

“The Fediverse” needs to end, and I don’t think anything should replace it. Speak instead about communities, and prioritize the strength of those communities. Speak about the way those communities interact, and don’t; the way they form strands and islands and gulfs. ==I’ve taken to calling this the Social Archipelago.==

A bounty on competence encourages competence.

So we’ll seesaw back from open a bit toward closed again. That is what we know how to do for security. There’s opportunity in making—intermediating, monopolizing—that transition. But the greater bounty lies on understanding the logic of the balance. Not just “how do we make open more secure?”, but “what would a more securable kind of open look like?”

We are not ready for the future of Analytic Engines. I think every organization that has a substantial analysis or writing component to their work will need to figure out how to incorporate these new tools fast, because the competitive advantage gain is potentially enormous. If highly-skilled writers and analysts can save 30-80% of their time by using AI to assist with basic writing and analysis, what does that mean? How do we adopt these technologies into our work and lives? What happens when the web is flooded with convincing but wrong content from these tools? Again, I don’t think anyone has a clear idea. Maybe the productivity gains will be illusory, but, based on my experience and conversations with other users, I don’t think so.