ooh that could be such a nice effect

a computer can never be held accountable therefore *all management decisions must be made with computers*

leaked software industry training manual (2026)

we got content-addressed records, bidirectional linking, "transclusion" (pointers), signed provenance, account portability, etc

pretty wild that one of history's most esoteric vaporware projects just kinda exists now, albeit with a very different shape after 50+ years of hypertext evolution

wait a second, it just dawned on me that atproto delivers on most of the project xanadu concepts that don't require a shit ton of lsd to understand?? minus payments which is what sunk xanadu anyway.

fun cs lore rabbit hole for the uninitiated! www.xanadu.net

compiler: implement method-set based AssignableTo and Implements by jakebailey · Pull Request #5304 · tinygo-org/tinygo Fixes #4277 Fixes #3580 Fixes #4873 Closes #4375 Closes #4376 Updates #4894 Based on the design from #4375/#4376 by @aykevl; I've Co-authored-by it since it's obviously based on those chang...

My PR to @tinygo.org to add full support for reflect.Type's AssignableTo and Implements methods just got merged!

This now gets tinygo passing the tests for errors, go/token, net/url, and gets the json package working for a lot more cases (and probably similar cases elsewhere).

oh THE CREDIT CARD EXECS say consumer spending remains perfectly solid?? lmao fuck off

love this interaction! atproto folks continue to be the most interesting people on the internet

never has there been a more accurate shot call than @reckless.bsky.social on google zero

this sticky chat footer is a brazen ux choice

lexicons are a psyop by Big Domain™ to sell more domains

on a completely unrelated note, new .at domain purchased 🙈 you're welcome for the revenue, austria!

gotta get that clean NSID namespace locked down early

hence why i prefer to do my banking on x, the everything app. gork send eva $1, make no mistakes.

font nerds might be a bit too detailed-oriented for this to happen tbf

yesss, saw that. huge fan!! texture healing is an incredible innovation and the writeup was super cool.

i must admit, learning that all the "greatest city in the fuckin world!!" new yorkers have just been piling trash bags on the curb this whole time has really helped my impostor syndrome

can't wait for the first vibecoded monospace font to come out so i can call it sloperator mono

The old internet is dying, and the new internet struggles to be born: Now is the time of monsters.

We're watching the open web as it existed die in real time.

We all have days like this

a bluejay elegantly sits on the fence near a sick bird feeder that looks like a tiny grill

hell yeah i love allbirds

allbirds who visit the new bird feeder outside my front window that looks like the world's tiniest grill

heh, fuckin gottem

if you ever feel compelled to write a keydown handler that includes `e.key === 'Tab'`... turn in your badge and gun immediately

depends on the scale! if you have customers with compliance requirements, there's really no avoiding CSP

I'll admit from the open source side, it's easy to dismiss CSP violations as niche issues—I have definitely brushed these off in the past because I didn't feel the daily pain.

On the other side, the cognitive load of violations is very high! Few devs with CSPs have the power to change them.

CSP error triggered in production - `z.config({ jitless: true })` is not a great workaround · Issue #5789 · colinhacks/zod We see CSP errors in production builds because Zod checks new Function("") to determine whether unsafe-eval is possible. I don't really care that Zod tries to use unsafe-eval, because our policy wi...

Noticed Sentry's CSP was catching a violation and learned that Zod v4 triggers `unsafe-eval` by default 😞

You can call `z.config({ jitless: true })` but that's brittle and depends on import order.

Better fix: pnpm patch zod, set `allowsEval = () => false`

github.com/getsentry/se...

as i said

Hell yeah, can't wait for vertical Sentry 🙏

The Vertical Codebase Let's take a look at why the common, horizontal code structure is not ideal, where it breaks down, and what we can do about it.

📚 Colocation matters. Cognitive load matters. Boundaries matter. High cohesion matters. Yes, even in the age of AI (maybe even more so).

Enter the vertical codebase:

tbh I see y'all in my For You feed so frequently that I never thought to check 🧡

excited to see movement on this! payments infrastructure is essential for avoiding future enshittification of atproto.

hand-waving money problems away was the fundamental miscalculation of the early web, which we now have a real chance to correct.

The Internet's Most Powerful Archiving Tool Is in Peril As major news outlets cut off the Wayback Machine, journalists and advocacy groups are rallying to protect the Internet Archive’s vast collection of web pages.

Journalists know that losing the Wayback Machine would be a nightmare: www.wired.com/story/the-in...

the year is 1126: the emporer quarrels with the papacy while his banners fly towards persia to seize the spice routes. literacy is a sin of the few. a loaf of rye costs a month's wages, but fret not, the high clerics swear that by the coming new moon, they shall summon The Oracle to deliver us

the pope is the president of rome right?

at least we're seeing concrete improvements to our daily lives, right? 🫠