based
Posts by Josh Shaked
Very 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?
Also, I notice that bluesky posts are not included. Is that by design?
WOW, 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)?
I’m in!!
Outside 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?
@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...
Really cool to see @tangled.org natively embedded in @leaflet.pub. Excited to see more experimentation here.
willdot.leaflet.pub/3miiirzf7jc2j
which article are you referring to @danabra.mov ?
If bsky dies, does atproto die alongside it?
Agreed. 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
Bluesky 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
@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
I’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
Not sure I understand the significance of this. Can you help me understand?
1. 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?
I 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:
what would be the advantage of that?
@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?
Thank you @devingaffney.com for the feedback and inspiration.
Custom 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/3mhqtyaufyc26
Feeds = Portable social object
Bluesky = Distribution for feeds
Feeds = USDC
Bluesky = Coinbase
Iykyk
yes 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
Some 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?
What would an atproto-native media company look like?
*site.standard.document*
In 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 :)
Awesome to see! Congrats @anirudh.fi @oppi.li
What'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