Jake Gold

odeo.com screenshot from Jul 20, 2006 showing a 'Twttr' link in a top notification bar

Some of us early users on Twitter (initially Twttr) learned about it in 2006 on the Odeo web site, which was a podcast directory created by Evan Williams (the creator of Blogger).

It's more than likely that I was looking for a new episode of @dancarlin.bsky.social's Hardcore History.

He also failed entirely to evolve the idea in ways users would have found useful.

He probably could have solved the "information bubble" problem if he had been willing (or able) to iterate on the product in substantial ways.

Instead he let it stagnate and deteriorate for a decade then sold it...

Jack seems to share many people's disdain for VC-backed companies without understanding the history of technology very well (e.g. Netscape's history).

Some companies do good.

Most of the cool technology, including open source projects like Linux, has *largely* been funded by VC-backed companies.

Jack's idea for Twitter was basically just sharing your status (e.g. "at a night club downtown").

Evan Williams, who had created Blogger previously, was IMHO the prime mover behind Twitter becoming a microblogging network.

Jack gets credit for "inventing Twitter" which is just not really true.

Anyone who wants to write me a $13 million, equity-free check to create an open protocol and then talk a little shit or ghost me is free to do so as many times as they deem necessary.

The best senior engineers can now ship much faster than ever before and have less need of junior assistance.

But the best junior engineers can now level up much faster than ever before.

So you can create senior engineers faster but the learning rate is still limited by the physics of time+brains.

Yay. This is great to see.

Welcome to the network @doctorow.pluralistic.net!

Using did:web for your identity and your own PDS for data makes you highly resistant to ENSHITTIFICATION.

Haha. Well there are some legitimately good ideas in the idea of decentralized digital money.

But there was no legitimate/useful use-case so the scammers and speculators took over and ruined it.

But it seems like there may still be a "baby" in the bathwater.

I'm as against cryptocurrency scammers as anyone.

But not all cryptocurrency transactions have to be expensive or slow. And LLM tokens will continue to drop in price dramatically as we create new hardware.

It seems likely that we'll finally have one legitimate use for *some* cryptocurrency thing.

Just agents sending/receiving money in controlled ways. There are lots of payment methods but it might just end up being the best way to do it.

Even if it does happen, it wouldn't validate any of the cryptocurrency ponzi schemes of course.

AI agents may very well end up giving some form of cryptocurrency a large, legitimate, and genuinely useful purpose.

But anyone who claims they predicted this (without proof) will have to serve a little time in a hot closet full of ASICs mining still-useless shitcoins.

Normalize rejecting PRs from authors that are incapable of properly designing, testing, and reviewing their own code.

It's not "gatekeeping" or a "bet against AI" to uphold standards that we know to be critical to creating high quality production software.

Pray your competitors do the opposite!

Neither does he!

My sentiments exactly.

Maybe there's a cool way to roll out Buckets for simple use cases (subcommunities) quickly and then define more complex ACL types (or whatever) later, so the experimenting/learning can begin.

Buckets could do more but I'm most excited about subcommunities!

1. Someone creates a bucket for a topic like `r/raspberrypi`

2. Other users publish posts in their own repos with a reference to that bucket

3. Apps merge those posts into subcommunity feeds

Some complexity but very workable.

Mixture-of-Experts (MoE) harnessed by a Mess-of-Files (MoF)

What's cool about the web (HTTP) is the analogy to AT is very strong. It provides a really good example to follow and learn from.

Too fast can be as dangerous as too slow.

If I wanted to slow down any software engineering team I'd add thousands and thousands of poorly vetted and designed code contributions to their projects.

Maybe it depends on your type of product.

In most cases, seems better to me to sacrifice features/scope to gain speed not quality.

I see a lot of startups fail with big/janky products that seem like they might have succeeded with smaller/quality products.

Many teams aren't good at reducing scope.

"I'm hot fixing prod on the toilet using a product that was created on a toilet"

This is an extremely clunky and buggy prerelease, so don't try to hot fix prod from the toilet without a different mobile frontend. Right now: - You can't interrupt Claude (you press stop and he keeps going!) - At best it stops but just keeps spinning - The UI disconnects intermittently - It disconnects if you switch to other parts of Claude - It can get stuck in plan mode - Introspection is poor - You see XML in the output instead of things like buttons - One session at a time - Sessions at times don't load - Everytime you navigate away from Code you need to wait for your session to reappear I'm sure I'm missing a few things.

Getting high on your own supply is risky.

The amount of AI slop jankiness in Anthropic products might end up being their undoing.

They're gambling on speed over quality.

But we've already run this experiment. We know running up tech debt is faster/jankier at first and then quickly jankier/slower.

Grip strength

Someone brought a grip strength thingie to the office and I got a pretty good score for a non-weight lifter.

Beware anyone trying to open a jar near me for the next few days.It’s going to come up.

Perfect Decentralization is the enemy of Practical Decentralization.

The internet, DNS, email, and the web are examples of Practical Decentralization.

Nothing beats this track record.

What AT needs to get to the next level is *many thousands* more independent+funded teams building on the network.

I went skiing for the first time in a long time and put so much stress on my knees keeping my speed controllable.

Got a lot easier as I remembered how to ski a little better.

Go that way really fast.

If something gets in your way, turn.

I should have added a link:

"Hardware is really just software crystallized early."

-- Alan Kay (of course)

Seems like "agent" might just get rewritten to mean OpenClaw-like agents even if it takes a while.

In any case, I hope we can do better than calling them Claws lol

Looks like you guys are cooking!