Post

Yesss love it, I do! (And want all y'all to make $ here too in all sorts of ways!) Pairs pretty well with my recent post/talk, I kept it high level & didn't get into monetization details, this is really good & I want to explore lots of what you talk about around $ interop and permissioned data

brendan@schlage.town

My talk from last month's @atproto.nyc, on Atmospheric Stacks! How the Atmosphere can compete with incumbents like Substack — not by recreating 'em app for app, but by replacing 'em collectively, as an ecosystem. With @leaflet.pub & @standard.site as case study + expanded with a few *addenda* :)

Definitely pairs well! I love the notion of stacks. I should’ve mentioned your post in there, might squeeze it in. I have a lot more to talk about RE spaces and payments - veryyyy soon

Niceee may be some time til I can dig in more (out on parental leave starting now) but hope you can jam on all this w/ Jared & Celine soon :D

Definitely! Congratulations and hope you have great parental leave!!

0 reposts3 likes

Your article is fascinating. And exciting. On the advertising, would that depend on private data? Otherwise, how would, say, a writer block a reading app that stripped out his ads or refused to share ad revenue?

Great question. I believe an ad system on ATProto needs to be contextual - ie placed on the public signal of the content and users it’s in proximity to, not personal data. There still needs to be a ‘success’ metric to be met for that ad buy to be paid out and that lies with consumption interface

If the content is paywalled, the creator (or maybe ad network on behalf of creator) could revoke payment capture for that client or space-management. For public ad-based revenue, an app could strip an ad - but they won’t make any money, so there’s much less incentive to do so.

I was thinking of a reader app that strips ads from the public content (e.g., a standard.site record of the article) and then inserts their own ads with no revenue share. If the article is public in the PDS, the writer (or their blogging platform) doesn't seem to have a technical way to stop that.