Josh Shaked @jshaked.com · 27/07/2026Next step to get advertisers more interested in atproto + unlock new forms of monetization 110
Josh Shaked @jshaked.com · 02/06/2026Definitely and I think this could be potentially synergistic with @awarm.space’s mention service as it proliferates across the atmosphere 010
Josh Shaked @jshaked.com · 02/06/2026checked in at @atproto.nyc - June 2026 [5pjg55kg] #atprotonyc 080
Josh Shaked @jshaked.com · 02/06/2026Permissioned data is the unlock for atmospheric monetization 130
Josh Shaked @jshaked.com · 21/04/2026Custom feeds feel like the perfect medium for feed-native media companies like MTS 130
Josh Shaked @jshaked.com · 16/04/2026@awarm.space when you mention one underrated feature is "the ability to search and mention just normal webpages," are you assuming that said website already has an associated identity/account on atproto? 100
Josh Shaked @jshaked.com · 10/04/2026Very cool! Can this mention/embed feature be integrated into any website or text editor? Additionally, what are the requirements for a project to make their data available to this mention service? 030
Josh Shaked @jshaked.com · 10/04/2026Also, I notice that bluesky posts are not included. Is that by design? 010
Josh Shaked @jshaked.com · 10/04/2026WOW, this is unbelievably cool! @awarm.space will these mentions/embeds live on protocol (i.e. when I mention a semble collection on a given leaflet, there is a strong connection between that semble collection and that leaflet post that lives on protocol)? 250
Josh Shaked @jshaked.com · 09/04/2026Outside of @leaflet.pub, are there any other apps that allow for natively referencing app.bsky.feed.post at-uris? See below for example from @willdot.net's recent post on distributed PDSs (willdot.leaflet.pub/3miiirzf7jc2j) @semble.so? @offprint.app? @margin.at? @pckt.blog? 470
Josh Shaked @jshaked.com · 07/04/2026@scanash.com did you know that the initial idea for Google was to build a "decentralized annotation system for websites." Sounds a lot like @margin.at. It's still so early! Source: www.acquired.fm/episodes/goo... 160
Josh Shaked @jshaked.com · 06/04/2026Really cool to see @tangled.org natively embedded in @leaflet.pub. Excited to see more experimentation here. willdot.leaflet.pub/3miiirzf7jc2jwilldot.leaflet.pubThe journey to a distributed PDS - Wills thoughts 0182
Josh Shaked @jshaked.com · 03/04/2026Agreed. Frankly, I don’t think there’s a way to get around this issue. I expect a few interfaces to win a significant majority of user attention. I still think this is better than status quo where there is no user choice for interfaces and users are forced into a single first-party client/interface 010
Josh Shaked @jshaked.com · 03/04/2026Bluesky trying to use AI to enable users to define their own custom interfaces, but that still means that Bluesky sits in between the user and the content he/she sees 100
Josh Shaked @jshaked.com · 03/04/2026@moja.blue I 100% agree with this. The entity that owns the interface / screen real estate users see has lots of leverage over portable feeds, especially if it continues to be expensive to build appviews 100
Josh Shaked @jshaked.com · 02/04/2026I’d love to see where my blog is rendered / referenced across the web and for me to be able to bring that context natively into my blog 121
Josh Shaked @jshaked.com · 02/04/2026Not sure I understand the significance of this. Can you help me understand? 000
Josh Shaked @jshaked.com · 02/04/20261. Which person, organization, or site is driving distribution for a particular piece of content? 2. How popular is this piece of content based on how many sites / curators rendered it? 3. How is this piece of content being contextualized across different communities and audiences? 111
Josh Shaked @jshaked.com · 02/04/2026I could see a lot of value in a system that indexes which websites a piece of content (at uri) is rendered / referenced. Would help us understand how a piece of content is distributed and contextually referenced across the web and help us answer questions like: 101
Josh Shaked @jshaked.com · 02/04/2026@awarm.space are you suggesting that we should not only see which sites render a given at-uri but that we should be able to render those sites in a unified interface? 110
Josh Shaked @jshaked.com · 25/03/2026Who would have thought social media is addicting www.wsj.com/tech/meta-an...wsj.comMeta and YouTube Lose Landmark Social-Media Addiction TrialJurors found the companies were negligent, and the design of their apps caused harm to children. 010
Josh Shaked @jshaked.com · 24/03/2026Thank you @devingaffney.com for the feedback and inspiration. 070
Josh Shaked @jshaked.com · 24/03/2026Custom feeds are the singular theory of action for growing the open social web and reorienting distribution and monetization in the attention economy. I don't have all the answers, but the future of social is becoming clearer everyday. jshaked.leaflet.pub/3mhqtyaufyc26jshaked.leaflet.pubExploring the Frontier of Feeds - The Open GardenReorienting distribution and monetization in the attention economy. 1306
Josh Shaked @jshaked.com · 20/03/2026Feeds = Portable social object Bluesky = Distribution for feeds Feeds = USDC Bluesky = Coinbase Iykyk 030
Josh Shaked @jshaked.com · 10/03/2026yes I agree. A media company should be defined by its content, not by the platform where that content lives. I would imagine an atproto-native media company would be "headless" in this regard 000
Josh Shaked @jshaked.com · 10/03/2026Some thoughts: - blogs / articles published to @standard.site - curated feeds built on @graze.social - collective bookmarks on @semble.so - annotations and highlights on @margin.at - mentions of people / organizations link out to their atproto identity / internet handle What am I missing? 260
Josh Shaked @jshaked.com · 05/03/2026In theory, anything can be published as a loose document under the standard.site.document lexicon - a twitter post, a youtube video, an amazon review. Excited to see further explore extending standard.site beyond long-form content, even though that's not what it was meant for :) 150
Josh Shaked @jshaked.com · 27/02/2026What's actually going on under the hood here? Are you just converting whitewind lexicons to pckt lexicons? Content migration across different lexicons feels like an unexplored space 100
Josh Shaked @jshaked.com · 27/02/2026+1 to this. I am growing increasingly convinced that atproto will not enable content portability but rather identity and social metadata portability. Big difference, still a good outcome for the world 010
Josh Shaked @jshaked.com · 27/02/2026That assumes that the user's content is stored in the PDS. And even if it is, Pckt has a very different data content format than Leaflet. Is it possible for a user to migrate their Leaflet data to Pack for example? 400
Josh Shaked @jshaked.com · 27/02/2026Right, but there's inherent conflict of interest when you're tied to an app-specific PDS. Assume that Pckt turns evil and they don't want its users to leave to join competing publishing platforms. What is stopping Pckt from refusing to host lexicons of competing publishing apps on their hosted PDS? 100
Josh Shaked @jshaked.com · 27/02/2026In the long-run, I think each atproto app will have its own PDS to ease onboarding of new users without internet handles. How do we prevent a world in which data and identity is fragmented across app-specific PDSes? Isn't this the situation that atproto was ironically trying to solve for? 300
Josh Shaked @jshaked.com · 26/02/2026Business models in the atmosphere?!?! Let's talk about how atproto and standard.site can move social media away from enshittifying, attention-based business models towards intent-based business models that better align revenues with openness and interoperability. jshaked.leaflet.pub/3mfrgv2aezc2gjshaked.leaflet.pubFrom Attention to Intention - The Open GardenExploring business models for atproto and the open social web 0293
Josh Shaked @jshaked.com · 29/01/2026can someone explain in simple terms the situation that led to this conclusion? 130
Reposted by Josh ShakedEli Mallon @iame.li · 19/01/2026atproto is so funny. Leading protocol explorer in the previous ecosystem I worked in: Etherscan, a 70-person company with ~$35,000,000 in yearly revenue Leading protocol explorer in the ecosystem I work in now: @pdsls.dev by @juli.ee, it's great 41219
