Embrace the uncertainty Nobody knows what the future of software engineering looks like, and that's incredibly uncomfortable. But instead of waiting for someone to hand us the answer, I think the move is to embrace the uncer...

I just thought of @brittanyellich.com 's article again. +1; a time of opportunity.

brittanyellich.com/embrace-the-...

Machine-readable attitudes - Computational Semantics++ User intent declarations can be viewed as propositional attitudes (permission, prohibition, desire, intention, belief, etc.) over structured descriptions of data use. Treating them that way gives you ...

tfw @aaronstevenwhite.io brings an analysis as sharp as a knife to your half-baked Saturday-morning thoughts: aaronstevenwhite.leaflet.pub/3miwsz2hdv22i 🤯

If we're going to own our data, let's actually own our data.

Which is to say: No, really, y'all, we're doing this. 💖🧠

Ok, selfhosted.social

So Grain does not also provide PDS

Does @grain.social have their own backend, meaning different PDS, or does it re-use bluesky's?

Two pug dogs in a bathtub with bubbles.

📍 Oakland
Oakland, California, US

Bath time for the pugs, roommate dogs.

grain.social/profile/did:plc:s53e6k6s...

#grainsocial

Don’t miss this - it’s gonna be FIIIIIIIIRRE

cc: @christian.bsky.social

We heard there's some atproto fans in Seattle? 🤔

Screenshot showing a browser with a page titled "My Pets" and has an image of 3 raccoons looking out of a drain hole, and the pet's name is "sewer raccoons"

TFW you are building a new web app, and you notice the placeholder content.

#devlog

screenshot of GitHub comment from @surfdude29 This is exciting to see! 🙌 I realise this is still in draft, but I just wanted to add in my two cents that I think it would be excellent if the new gallery embed type lexicon includes the option of adding license and attribution metadata for each of the media objects, along the lines of what @bnewbold outlined in this post on the ATProtocol Community and as has been discussed in this issue: [link] Introduce an attribution field to app.bsky.feed.post and app.bsky.embed.* record definitions #3562 [screenshot of @bnewbold.net post from ATProtocol Community on 29 January] I can't remember if l've put something out publicly, but I think media objects (blobs) in particular should usually have license and attribution metadata attached when designing lexicons. Two metadata fields: • licenseUri: string, format=uri, optional. standard/normalized URL (or short URI) for common licenses, or can point to more bespoke license/policy page • attribution: string, optional: more free-form field for listing a name or source of the media. can also be a URI that links back to the original source These fields would go alongside things like alt-text. If there are multiple pieces of media in a record, it should be possible to attach different metadata to each (same as with alt-text). 7 likes

a new embed type lexicon is coming: `gallery`

it will allow more images per post – perhaps up to 10

and it will eventually allow a mix of media types, e.g. videos as well as images

this would be a great opportunity to allow optional license and attribution metadata, as @bnewbold.net has proposed

Moving Railway's Frontend Off Next.js We migrated

blog.railway.com/p/moving-rai... interesting

Some personal news:

I've signed a contract for a book! It's called REGIME CHANGE and it's published with Princeton University Press. More details as they become available.

I'm going to do that soon, ending a 39 year streak of not having a license...

particularly excited about this because webrtc data channels mean you can add just about any p2p functionality. for example, you could get around the latency issues with my yjs demo by exchanging updates peer-to-peer rather than using the firehose.

The experiments that @jakelazaroff.com is doing around CRDT syncing and WebRTC signaling is pointing towards a future where the PDS is a server-based user agent. There's no reason that the PDS needs to be limited to storing static data.

I miss IRL interviews.

Looking at github with someone new to it.

"How can my branch be both ahead and behind?"

Seeing things through fresh eyes, it is confusing. Probably could have found better language than "3 commits ahead, 3 commits behind source-repo/main"

#devlog

Devs in the atproto community! I will be organizing some meetups in the near future and will be reaching out

Also- don’t hesitate to reach out if you want to discuss the state and future of the ecosystem, what we’re doing with attie, or anything else. I can’t just … open my DMs but we’ll find a way

I made a thing

This is amazing: somebody has built the first hosting platform for EmDash. This is exactly what I hoped would happen. dashhost.io

this is so painful to read, i love it github.com/stephenturne...

One of the hardest things to get across to most software people with great intentions is *how strong defaults are* and how tired everyone else is of dorking around trying to get things to work, but this understanding is the thing that made Apple, for all its many flaws, such a giant.

The Drill-Down Menu with Details and @scope Even if you nest details elements, you can ensure only one level of them is open at a time, making a menu you can drill down (and up!) from.

frontendmasters.com/blog/the-dri...

via @cassidoo.co 's newsletter

Have been wondering how to do that.

#devlog

Hmm I didn't realize Linux was such a pain. 🙃

Yeah the login via email UX is key.

A screenshot of a chat with Chipotle restaurant AI, where they ask it to reverse a linked list.

This is good.

www.reddit.com/r/ClaudeCode...

#ai

I thought the passkey is all client side, and the backend just saves a public key for each device. Your backend would then need to map each public key to a user.

State of the Atmosphere (CONF 2026) - Brookie’s Blog I should be cleaning the house right now but instead I'm writing about the ~Atmosphere~ again...It's been a full week since I first arrived in Vancouver, for...

did a little writing about Atmosphere Conf, hopefully ur not sick of reading about it yet 🙂‍↔️

brookie.pckt.blog/state-of-the...

In the past Fission had done this with UCANs + web crypto, but imo that still felt kind of clumsy. Now that passkeys (fingerprint readers) are everywhere, it really feels easy & good.

You do still need to account for the public library usecase. That makes it interesting.

Even when making "boring" web apps, there is enough new stuff to keep it interesting, imo.

Not using passwords is my favorite. I have not seen this done really well in any app, honestly. Meaning linking multiple devices to a single user/account -- an opportunity for extremely good & new UX.
#devlog

the desk by @nichoth.com — Grain The good old days, with the pallet desk. TFW you're living inside a shipping container and using a desk made of shipping pallets. Surprisingly, it was very sturdy.

Trying grain.social , @grain.social

grain.social/profile/did:...