I've been following Bluesky since inception, even tried developing for it and found it was nothing new with its 300 character limit, no links, titles, etc. Basically you can build the same apps for Bluesky that we were able to develop for Twitter. I've also been following Leaflet, an attractive writing tool that works on AT Proto, the format that Bluesky is promoting, basically a reinvention of the web but inside a silo, which means -- perhaps confusingly, that Leaflet uses the same basic format that Bluesky uses, but Bluesky can't do anything with Leaflet posts, because of the limits that Leaflet doesn't have. So -- they formed an alliance with two other products that are writing tools for AT Proto, and came up with a format that they will all implement called standard.site (nice name and very attractive site). They probably hope that Bluesky itself will use that format, at least to let people read their documents in the same place they display the more limited Bluesky posts, in user timelines. If that happens it may be a good thing for the web, if services outside of Bluesky can post these documents from outside. But it would be imho more powerful if they created a format based on something like RSS, which is already well-known to developers, and would mean something outside of Bluesky and probably would be taken more seriously by the Bluesky people. There is no advantage that I can discern for creating a new format that only works in Bluesky. #My first rule of platforms: "People don't listen to their friends, they listen to their competitors." I thought that rule was pretty new, but it actually appears in a 1996 blog post.#