at://rude1.blacksky.team/app.bsky.feed.post/3lzra7scq5k2f

Back to Collection

Record JSON

{
  "$type": "app.bsky.feed.post",
  "createdAt": "2025-09-26T19:46:42.469Z",
  "embed": {
    "$type": "app.bsky.embed.images",
    "images": [
      {
        "alt": "This also reduces the “cold start” problem for new apps. If some of the data you care about already exists on the network, you can bootstrap your product off of that. For example, if you’re launching a short video app, you can piggyback on the Bluesky follow records so that people don’t have to find each other again. But if that doesn’t make sense for your app, you can have your own follow records instead, or offer a one-time import. All existing data is up for reuse and remixing.\n\nSome open social apps are explicitly based around this sort or remixing. Anisota is primarily a Bluesky client, but it natively supports showing Leaflet documents. Popfeed can cross-post reviews to both Bluesky and Leaflet. If Leaflet does gets very popular, there’s nothing stopping Bluesky itself from supporting a Leaflet document as another type of post attachment. In fact, some third-party Bluesky client could decide to do that first, and the official one could eventually follow.\n\nThis is why I like “open social” as a term.\n\nOpen social frees up our data like open source freed up our code. Open social ensures that products can get a new life, that people can’t be locked out of what they have created, and that products can be forked and remixed. You don’t need an “everything app” when data from different apps circulates in the open web.",
        "aspectRatio": {
          "height": 611,
          "width": 704
        },
        "image": {
          "$type": "blob",
          "ref": {
            "$link": "bafkreic7uy7z6s7vudrxdce46fbprumrc4zaqw65pszntaqk5wgqcimk2u"
          },
          "mimeType": "image/jpeg",
          "size": 275619
        }
      }
    ]
  },
  "facets": [
    {
      "features": [
        {
          "$type": "app.bsky.richtext.facet#link",
          "uri": "https://api.bsky.app"
        }
      ],
      "index": {
        "byteEnd": 134,
        "byteStart": 122
      }
    }
  ],
  "langs": [
    "en"
  ],
  "reply": {
    "parent": {
      "cid": "bafyreiery24fcfywkydptpc74ygtqpyslijxidwc6yf553v26eygtvmlcq",
      "uri": "at://did:plc:7ax27mj5qwhqaa3ite2ezlzy/app.bsky.feed.post/3lzr76aj7s22e"
    },
    "root": {
      "cid": "bafyreid743xc7woomz6thofvgck2z2o746cqhxqgt5xtd4v5akthlvq6aa",
      "uri": "at://did:plc:w4xbfzo7kqfes5zb7r6qv3rw/app.bsky.feed.post/3lzqw3kscr22d"
    }
  },
  "text": "Exactly. That's what this part refers to.\nI think it's just more explicit to call an App-View an API (theirs is literally api.bsky.app)"
}