Post

Does this allow publishing content to an existing publication from a different tool? For example, suppose I create a a blog in leaflet and write another tool to post documents to it by updating the pds directly. Is that going to work, or is something going to fail due to "verification?"

@leaflet.pub Can I update my publication tool to use @standard.site's lexicon to be published on pankzsoft.leaflet.pub now?

We're working on lexicon migration now, stay tuned, should be ready soon!

You should be able to subscribe, at-mention others blogs, tag your posts, and more. Regardless of which host you choose to use. At the same time, every developer building tools here should be free to experiment and own the formats and metadata they need to ship their products.

The standard.site lexicons define whats necessary for content to move across social boundaries. It doesn't define things like complex themes, or content formats, but since lexicons are extensible, each developer can add those themselves. We think we struck a pretty good balance.

This is still very early, and there's lots to improve on documentation and tooling, but the lexicons are in a good place to start building on. There's a lot more to build, so if you have ideas/needs/complaints/questions, start a conversation on bsky or open an issue on tangled.

This! What I've been trying to explain. For everything data, standard lexicon. Likes, emoji reactions, title, subtitle, categories, tags, authors (for multi-authoring), Canonical URL (for search engine bot use to avoid getting penalised), publish datetime (UTC), last edited datetime (UTC), …

👀

Do you have an example site that has implemented the standard? Also how should the lexicons be formatted?

Hello Standard.site ! Please make my day and tell me that there is a repository somewhere with these definitions? ( I'll take @tangled.org or @github.com ) I've been generating a page for known lexicons, and want to make it a Standard.Site.

Now on tangled! tangled.org/standard.sit...

So, the lexicons themselves aren't on there. That repository is just the tooling to generate them. You can view them here though: lexicon.garden/identity/@st...

Ooh, this is really exciting! I’ve been tinkering with atproto dev myself recently and have been running into a few data types that would be well-served to have premade - are there plans to expand the scope to stuff beyond the necessities for longform content at the moment?

(The main one to note right now is that there’s a lack of a standard object type for a translatable string - it’d be really nice yo have for i18n efforts!)

I think lexicon.community might be a better home for the kind of stuff it sounds like you're thinking about! we're really thinking of standard.site specifically for "sites", longform content on the internet

nitpick on website: can make scrolly stuff less intrusive? i get the animation is fun but it actively *delays* recognition. like i can't scroll and scan. can either reduce duration or make it trigger on load (rather than on each block getting into viewport)

dan coming along and giving some critique on the site 😭 felt like it wasn’t too over the top, but I can tone it down a bit. just gimme some time to play with it a bit, got some stuff to finish first

wonder if it can be done more quickly based on visibility vs just doing one after the other

> ..began as a conversation between developers building long-form platforms on AT. Coordination was the missing piece. I’d love to hear the full story alluded to here. I realize it boils down to ‘so we talked’, but to a lot of techies that’s a major challenge; explicit examples help lower the bar.

Amazing! Could this be implemented into Wordpress with a plugin?

Another question, what motivated the decision to form a separate body and domain from @lexicon.community?

I think the main motivation was that there's a bunch of interconnected stuff that's domain specific, and that a legible namespace for that makes communication and adoption easier. We haven't set any governance stuff in stone yet, so could be potential for a shared body or process there mayhap

Why are URLs primarily referencing / giving examples for https:// URIs? How does one link a publication to a document the atproto way?

The url on the publication record is for the publication home page. Documents point to the publication record’s at-uri via the site property. This creates backlinks. Documents accept https:// or at:// for the site property to support standalone documents and documents belonging to publications.

Why is "bsky" in a field name? Will we eventually need to add N app names to this lexicon?

the app.bsky lexicon is pretty much the defacto standard for micro-blogging in the atmosphere. we could've genericized the field name to "microblog" or something like that, but I don't see much benefit.

We also considered having an open ended "links" field, which maybe we could extend to be an array of objects with both "uri" and "rel" properties, and it could capture the bskyPostRef use case in a more extensible way?

Can you expand on the choice of block based document format over something human readable, and growing in popularity and usage because of #ai... why not Markdown? (i.e. like bsky posts, text+facets)

We don't define a content structure for documents. Platforms are are given the freedom to implement content in the way they see fit. For example, you could just create your own markdown lexicon, and use it in the `content` open union.

We do define a `textContent` (string) property as well, this should contain the text from the content body, used for search and I would imagine AI could easily tap into this if needed.

I understand I can do something different, in general, with lexicon. I'm curious to the choice to this specific block format for a proposed standard, over something like what Bsky did with text+facets My assumption is the choice is largely driven by the underlying pkgs/editors the apps here chose

For apps that do not separate publications from user accounts, is it recommended to implement the site.standard.document lexicon alone?