Paul Rohr

But at least it gave me an opportunity to reminisce about a different feature ("hush")

Sorry for not choosing between alternate designs there. Means I hadn't given the feature enough thought yet

My design guru would not approve

A quick skim suggests that the GNU folks would say no:

www.gnu.org/licenses/lic...

I'm not a lawyer, but do any of the licenses here come close to what you'd want?

opendefinition.org/licenses/

Yo (app) - Wikipedia

Note that the "yo" app's infamous zero-character constraint wouldn't count as a nanoblog any more than FB's old "poke" feature, because both functioned as pure notifications where individuals provided the momentary context to interpret each ping

Nobody ever tried to *read* logs of such actions

The "every accusation is a confession" principle in action:

courtiers = rush to file the accusation as a scoop

stenographers = seek a response from the accused before filing "he said, she said" pieces

investigators = treat each confession as a tip, then report out THAT as a potential story

The Resonant Computing Manifesto Technology should bring out the best in humanity, not the worst—a manifesto for resonant computing built on five principles that reject hyper-scale extraction for human flourishing.

These principles name the opposite of the oppressive design elements being used against us, but like other cyberlibertarian frameworks, they stop short of the root cause: politics. Liberation depends on shifting political power, because power determines which values take hold.

resonantcomputing.org

To the extent that democratization meant establishing a clear and independently verifiable record of what everyone was reading in a given text, a word generator with opaque sources and personalized outputs is the exact opposite of the press, and has the exact opposite effect.

« What they mean here is that the printing press produced more units of certain class of commodity (words on paper) and made that commodity more affordable. As a result more people could own this commodity. [..] The issue is whether allowing more people to buy something is a democratizing process. »

I've been exploring the Cooperative Election Study data since learning about it via @adambonica.bsky.social and @jakemgrumbach.bsky.social. I made this variation of their racial resentment by age chart showing the response breakdowns for one of the questions. #dataviz bsky.app/profile/adam...

How fast is your datastore?

Seeking "blog posts and trip reports talking about big AT data indexing attempts, and what the resource costs, bottlenecks, and pain points were. Maybe even a benchmark/leaderboard could emerge around how long it takes to backfill the full network and how much it costs"

"don't make me think:

you don't want to be thinking about content addressing. You want to grab this off the shelf and have something that works out of the box. Nothing weird, no impedance mismatch with the systems you know and love (or maybe know and hate, but whatever, it just works)."

see also: talking nice about people behind their backs.

sure, you could talk shit about people behind their backs, but gossiping with your friends about how cool and good your mutual pals are is genuinely so much fun.

get loved, nerds! get absolutely adored!

Where is the impedance mismatch between those off-protocol services + the patterns that bsky currently uses for pumping around small records of public data?

Is it more about how/where data flows? Or that lexicons are currently too awkward for describing:

- data formats +/or
- service APIs?

Can you say more about the kinds of services whose APIs or data are fundamentally incompatible with existing inside some extended notion of the PDS/relay/AppView model?

The AT paradigm describes APIs where data moves through pipelines of different services. Where is that abstraction too limiting?

Over the long run, off-protocol data + APIs should be reserved for exceptional circumstances

We all -- including service designers making pragmatic decisions to do otherwise for now -- want to see common use cases for new services become efficiently + reliably achievable on-protocol, right?

But as @willem.dobs.nl points out, DID-based service discovery shouldn't be the preferred approach over the long term

My data belongs in my PDS -- where I can see, control, + use it -- not hidden behind other non-lexicon-flavored service-specific APIs

Sure, in their current incarnation, lexicons may be overly optimized for the needs of a large-scale public-only microblogging service

Until there's consensus on how to solve common problems within the AT paradigm, services can + will forge their own paths outside this model

Likewise, being able to someday see lexicon-formatted views of all my service endpoints in @pdsls.dev might be even more powerful

Thinking about the problem from a data-centric perspective, it's amazingly powerful to be able to scan my PDS to see lexicon-formatted views of all my data

I'm wary of any service who's not interested in extending the capabilities of this paradigm for their novel ways of storing + using my data

... especially for services which need data in different:

- shapes (formats, scale)
- access modes (private, shared)
- etc.

There's been lots of ink spilled about the third invariant, which is why that's (rightly) being standardized first

But people's willingness to consider breaking the other two invariants suggests they may not appreciate how radical it'd be to accept those design constraints ...

☝️ This. One of the most underappreciated things about the current AT design is the power of combining three invariants:

1. data + services are specified using lexicons

2. your PDS brokers access to *both*

3. verifiable updates can be (un)bundled to flow independently for aggregation + indexing

Insofar as blogging inherently has a public audience, it's hard to imagine how expressive this constraint would be

... but it might be fun to watch artists try to pull off a new #oulipo subgenre 😉

A tall world map projection showing the Earth’s continents at the top, transitioning downward into the icy landscape of Antarctica. Near the South Pole, a research station is visible surrounded by snow and ice. Below that, the image artistically fades into patterns resembling frost crystals or snowflakes, blending scientific imagery with decorative ice textures.

The Mercator projection if it weren’t cropped

(click to view full size)

danabra.mov/sidetrail an app to share curated trails

cool news, sidetrail.app is now open source on @tangled.org!

the stack:

- atproto (jetstream + new lex client)
- next 16 + cacheComponents (yes, a recent version)
- postgres + drizzle, redis
- vitest

The fact that I can ignore all the identity/auth/user stuff for #atproto apps is such a superpower. That always stops me on personal projects. I don't want to have to care about those things. I just want to make stuff.

Build the thing you wish to see in the world For most of my career, I've been confusing building products with building businesses—and that confusion kept me from pursuing a lot of ideas. Two weeks off helped me realize that not everything needs...

Build the thing you wish to see in the world

A blog post about building things because you want to, learning about #ATProto, and some recently influential conversations I've had on the @overcommitted.dev with @bradhe.net @turoczy.bsky.social and @ngerakines.me

brittanyellich.com/build-the-th...

Yeah, rhyming with "ih-tee-itts" wouldn't be a good reason

NREL has produced 1000 patents and 50,000 publications and billions of dollars in economic benefit and the people in charge probably want to kill it