patricktree.me / overreacted
forked from danabra.mov/overreacted
my blog https://overreacted.io
fork atom

typo

authored by danabra.mov and committed by

GitHub f1076ea6 0a19d5ba

+1 -1
unified split
+1 -1
public/open-social/index.md
··· 227 227 228 228 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. 229 229 230 - Some open social apps are explicitly based *around* this sort or remixing. [Anisota](https://anisota.net/) is primarily a Bluesky client, but it [natively supports](https://anisota.net/profile/dame.is/document/3lxankooyf22l) showing Leaflet documents. [Popfeed](https://popfeed.social/) can [cross-post reviews](https://bsky.app/profile/leaflet.pub/post/3lzjsw7c6os23) 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. 230 + Some open social apps are explicitly based *around* this sort of remixing. [Anisota](https://anisota.net/) is primarily a Bluesky client, but it [natively supports](https://anisota.net/profile/dame.is/document/3lxankooyf22l) showing Leaflet documents. [Popfeed](https://popfeed.social/) can [cross-post reviews](https://bsky.app/profile/leaflet.pub/post/3lzjsw7c6os23) to both Bluesky and Leaflet. If Leaflet does get 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. 231 231 232 232 This is why I like "open social" as a term. 233 233