Standard.site
Standard.site

Shared lexicons for long-form publishing on AT Protocol.

Posts that mention this listing (matched by product handle, link, or name). Showing up to 50 most recent.

In atproto, I can't directly follow my pckt blog on my Bluesky feed, and we need things like (the excellent) standard.site and implementing it in Bluesky to kinda sorta make these sorts of interactions possible. Basically, at the level of data storage, atproto interoperates by default, but at

7/26/26, 4:48 PM

1. Ability to collapse the “article” pane on mobile (I wanna read on ipad and it takes up fair many of space) 2. Enabling comments/likes from socialwire for standard.site posts - right now I’ve to login and that doesn’t even seem to work (cuz frame prob) + doesn’t seem to detect post(s) w blog

7/20/26, 6:14 PM

that was a generalized statement about readers if you see i’m talking about how standard.site could help spec this out for readers if you’re open to that. what about the rest of the unthread?

7/20/26, 5:47 PM

Is that a chronological feed with all standard.site publications?

7/20/26, 8:41 AM

Welcome to the blogosphere. All @standard.site publications in one place.

7/20/26, 8:16 AM

Adding a blogosphere feed to @twinkl.social and there'a Malawi news site using @standard.site

7/20/26, 8:04 AM

@standard.site is it intentional that the public appview doesn't have a simple way to get documents of a single user? I can get publications but not documents for them and getLatestFeed did filter doesn't work.

7/20/26, 7:57 AM

Now with shinny standard.site integration! 🥳

7/20/26, 2:03 AM

The robot and I have spent the weekend working on personal / professional website for me that pulls photos in from @grain.social and lets me add blog posts via @standard.site and to test the site, it pulled in this post and I kinda have to keep it now

7/20/26, 1:10 AM

I’ll try & get standard.site wired back, I had the WP plugin but it was flaky. Couldn’t keep auth. Need to investigate what that means for existing records though.

7/19/26, 11:20 PM

A standard similar to standard.site but for storefronts could be cool, standard.shop?

7/19/26, 10:20 PM

The combination of @standard.site powered blogs and @standard-reader.app, even as early as both are in their development, already feels like a healthier and more pleasant way to do internet.

7/19/26, 5:40 PM

bsky is both creation and consumption standard.site platforms are creation, apps like standard reader, skyreader, social wire, etc are consumption Each side can be competitive :D

7/19/26, 4:50 PM

I thought our Standard.site support was broken, but then remembered it only works when Micro.blog is configured to embed previews for links. Updated the help page of Bluesky technical bits to document this.

7/19/26, 4:22 PM

this could have been a standard.site

7/19/26, 3:30 PM

This is exactly my plan with larakin.systems. I have my astro.dev site up and running on the dev machine, I've back-ported all my blog posts (including from my blog in 2004). I'm just getting all the standard.site integrations figured out. Coming Soon!

Larakin Systems

Thoughts, stories and ideas.

https://larakin.systems

7/19/26, 2:13 PM

I recently found if I use `standard.site`, my posts just show up on pckt/other reader apps without me doing anything.

7/19/26, 10:23 AM

tempting to make my (soon, currently in the shelf) @standard.site publication called "jb's ramblings" so I can say somewhere "we are jb's ramblings, please read us"

7/4/26, 9:15 AM

Love that you’re making moves with @standard.site! Would be awesome to hear more about it! 😏

7/4/26, 5:47 AM

Being able to just use the standard.site feed for every app that has one would be the nicest solution

7/2/26, 2:03 PM

This doesn't solve the "how do you call publishing on the bluesky lexicon". Atmo could be anything : standard.site, rpg.actor etc. The "problem" is, the lexicon is named bluesky 😅. I mean fair enough, but it's still confusing.

7/2/26, 1:36 PM

Despite spending an afternoon making my site @standard.site compliant, I enjoyed reading this on why you might not want to. The complexity part is hard to argue with. I had to experiment a bit to get this right so that it's completely hands free & easy to rip out. Let's see if atproto catches on.

7/2/26, 11:20 AM

My blog is not on the AT Protocol, standard.site is not for me Since you landed on my blog, the chance is high you’re a tech-savvy web geek. If you publish stuff yourself, the chance is even high... Origin | Interest | Match

7/2/26, 7:59 AM

Obviously not @standard.site support, but there is some method to my madness of running many multiple blogs and link blogs and and and...

6/29/26, 6:54 AM

hahaha yessss starting to get fancy standard.site preview cards working with #QuartoPub - more to come later once I get it fully figured out

6/29/26, 3:31 AM

This standard site validation checker might help isitstandard.site/inspect?url=...

6/29/26, 3:18 AM

sooooo the server handling our semantic search blew up 🔥😬 we are in the process of re-indexing posts, search is working in limited capacity right now, but should be fully restored by morning as posts catch up :) btw did you know we had a pretty cool search feature for @standard.site documents?

Read on pckt

Explore blog posts and articles from across the ATmosphere.

https://read.pckt.blog

5/22/26, 6:45 AM

Alright, I'm excited about this one. Have been playing around with some site integrations that never entirely worked for me. The @standard.site support, lexicon and backfill are all pretty cool 🥳

5/20/26, 7:23 PM

Really exciting. I hope to see @ghost.org build upon its ActivityPub integration to include the ATmosphere and standard.site support, too.

5/20/26, 6:57 PM

Every @wordpress.org site can now publish to the Atmosphere with this new @standard.site integration

5/20/26, 5:31 PM

RE: long posts, you might be interested in standard.site, @pfefferle.org; that solves this problem explicitly and blackskyweb.xyz has been toying with having these posts show up natively in the interface (like Twitter's support of articles).

5/20/26, 5:01 PM

Not concretely planned, but would love to support something like that eventually. Next step would probably be getting a language tag in @standard.site

5/19/26, 8:14 PM

まあstandard.siteがここまでこれたのは既に大手だったLeafletが主導してたとか独自部分と共通部分の分離とか色々な要因があるだろうけど、何にせよそう簡単に真似できるものではなさそう。

5/19/26, 6:55 PM

結局standard.siteはデファクトスタンダードの立場を勝ち取ってatproto.comブログにも使われるようになったけど、off protocolのメタデータは多分既存lexiconのどれとも互換性無いんだよな。現状のatprotoポッドキャストはまだどれも立場が弱い。

5/19/26, 6:52 PM

The metadata defined by @standard.site is the same, your social graph remains, the migration would be converting the `content` block — pretty straightforward.

5/19/26, 1:03 PM

standard.site 対応のサービスってことで最初にmochottで記事書いて、その後offprintで書いてみたところ、それぞれのサイトでしかそれぞれの記事を確認できなかったからなんで??と思ったけどmochottが特殊らしいね。Leafretならちゃんとoffprintの記事も自分のものとしてみれた

Standard.site - One schema. Every platform.

Standard.site provides shared lexicons for long-form publishing on AT Protocol. Making content easier to discover, index, and move across the ATmosphere.

https://standard.site

5/19/26, 9:22 AM

noteからの移行先と無理やり絡めて言うと、ちょうど昨日 app.bsky.embed.external (リンクカード)に associatedRecords が追加されたようで https://github.com/bluesky-social/atproto/blame/main/lexicons/app/bsky/embed/external.json#L28C10-L28C27 公式も standard.site のような3rdPartyへ歩み寄っているんですよね。なのでちょっと頑張れば各クライアントでもnoteの代わりになるようなviewを提供できるんじゃないかと…公式でも…無理か

5/19/26, 3:09 AM

When we relaunch (soon!) you'll be able to convert your old PiPup posts to @standard.site format with 1 click. #atproto #atdev

5/18/26, 6:19 PM

(The closest thing to blogger is probably the stuff people have done integrating standard.site into various static site generators because Blogger was, for a long time, a static site generator. Just one that lived on a webserver somewhere.)

5/18/26, 12:56 AM

At the very least that seems to be the target every current standard.site based thing is aiming for. That or substack.

5/18/26, 12:56 AM

Let me check if we even can detect the difference (as both use the same @standard.site lexicon, and that is what is visible in the PDS, not the app that created the activity)

5/17/26, 9:45 PM

Currently having the client crawl the PDS for all of the @standard.site and @skyreader.app records and caching them While this means I don't have a backend or database to manage myself...whenever the browser flushes the cache we have to crawl the PDS again Which isn't fun

5/17/26, 8:10 PM

might as well use whtwnd.com instead until standard.site apps bother being athmospheric imo...

5/17/26, 11:55 AM

is there any atproto blogging client that a) uses the standard.site lexicon, b) doesn't implement vanity urls but make use of your handle, and c) actually makes an attempt at rendering other .content types, and uses .textContent as a fallback, maybe with a link to the original page?

5/17/26, 11:55 AM

Not sure where or who to ask, but looking at the lexicons for @standard.site there doesn't seem to be a standard for `content`? Am I supposed to create my own if I wanted to self publish? standard.site/docs/lexicon...

Document Lexicon - Standard.site

Schema reference for documents, used to provide metadata for documents published on the web.

https://standard.site/docs/lexicons/document/#content-format

5/16/26, 11:56 PM