Weird aspires to be a digital garden for personal web spaces. That means facilitating small beginnings that can mature over time. A key aspect of this is version-controlled documents.

Using the excellent Loro CRDT, we've got a functional demo of 'Git for writing' working.

https://loro.dev/

With our first pass of theming completed, Weird.one is officially a MySpace competitor. (just kidding, sort of)

We partnered with the wonderful https://hazy.sh to demonstrate the capabilities of Themes v1, based on Jinja 2 templates.

All of her themes are available for free: https://git.gay/h/weirdone-themes

“Here I posted a link to Fp, it was automatically reposted to my Bluesky profile.

Another left a comment on Frontpage, that I also replied to. These were translated to a thread on Bluesky.

I voted the reply on Frontpage, this vote translated to a like on Bluesky.

Now consider another user noticed this bsky thread, and left a reply to one of these comments from the Bluesky app.

We can show this reply inside of Fp; now the discourse stays together with all of its context!”

#Lemmy #Mastodon

“If I'm at all right about there being a sudden explosion of local, home-cooked software, how does this affect the strategy of the local-first movement?

How would you try and make sure local-first is baked into this future by default?

Because this default tool set for barefoot developers should really have a database that’s a local-first database, right?

(…)

Whatever defaults are baked into these agents and their available tools are going to make a lot of decisions for them.”

“[Barefoot developers] are people who are technically savvy and interested in solving problems for themselves and people around them, but don't want to become fully-fledged programmers.

(…)

At the moment, they rely on low and no-code tools. And they do wildly complex things within them, pushing these apps to their limits.

They are the kinds of people who would be thrilled to have more agency and power over computers.

(…)

But they never make it over what I call the command line wall.”

“My friend Kasey Klimes wrote a fantastic piece called “When to Design for Emergence” on the design dynamics of large-scale software after working on Google Maps.

He points out that our current approach is designed to only solve the most common needs of the most number of users.

Anything beyond that is what we call the long tail of user needs. These are things only a few people need, but there's a nearly infinite amount of them.”

“small-scale, specific software [is] the land of opportunity”

“And so here's what we're going to talk about:

Local-first Beyond Local Data
Home Cooked vs Industrial Software
My Pitch for Barefoot Developers
Why Language Model Legos Need Glue
How We Can Bake Local-first Into Everything.”