OH: "I don't know if was my watch, one of my agents, or my computer was hacked"

I really like this approach. I called it a "CommunityBot" in some internal doc at Bluesky, PBC.

The model is IRC bots, which provide features and enforce rules for a channel on top of the very simple IRC protocol.

My idea was just bots that decide to repost using @mentions/web, but DMs exist now.

This a very exciting idea!

It's a huge personal goal of mine to launch one of my Cool Atmosphere Ideas for the next #atmosphereconf and I'd love to it every year until we Fix The Internet.

@justinmezzell.bsky.social you tried building a new Digg without the compelling differentiator of being an open social app.

Now try building on the AT network!

You have to give up control over users' identity+data but you can build a great app and make money at scale: bsky.app/profile/jaco...

GL!

Yeah, that makes sense then.

Not paying super close attention, I assumed records would just reference a bucket in some special way and PDS would mediate access etc.

Generic term like partition/slice/shard seems pretty good. With maybe a way to "type" them as "bucket" if other containers will come.

Buckets seem pretty hard to beat for the container name. Easy to get "too cute" with naming containers / elements.

thread < replies

bucket < submissions

Or similar seems sufficient?

Convenient to have a label like "replies" but seems unnecessary to have a name for "thread partitions" themselves.

Two flawless options

#1 hidden dot files:
at://.self/app.bsky.feed.post/foobar
at://.shared/mutuals/app.bsky.feed.post/foobar

#2 Unix permissions:
at://rw-------/app.bsky.feed.post/foobar
at://rwxrwxrwx/app.bsky.feed.post/foobar

One pint and you wouldn't have to ask twice.

I want "actually, just give me a prompt" on a t-shirt

My advice: when in doubt trust @divy.zone's judgement.

(Feel like Paul and Dan would agree with this)

@jay.bsky.team deserves a ton of credit for making Bluesky an independent company and hiring the founding team.

@toni.bsky.team seems to have a sense for how much Bluesky has captured lightning in a bottle and how precious that is.

Let's all hope the right person is found for the permanent role!

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.