Post

@leaflet.pub documents and comments that reference an eprint now show up on it. Chive picks up the reference whether it's an inline link in the prose, a website block, or the subject of a comment.

New eprints publish a site.standard.document record, so @standard.site readers can pick them up. Sharing an eprint to bluesky also records the post on that document, which makes the reply thread findable from the paper.

You can now post an event with @smokesignal.events or anything else using community.lexicon.calendar.event, list the eprint among its URIs, and the paper shows where it was presented.

0 reposts0 likes

You can also point a paper at a @layers.pub dataset it introduces or uses. A dataset is named by at-uri rather than by a URL at some host, so the reference is to the record and doesn't depend on a particular page staying up.

Chive now reads your @sifa.id profile if you have one and populates your public profile with current and previous affiliations automatically.

Hi! Out of curiosity, why did you choose this option rather than using DOIs, which in most cases resolve to the current version of the paper? And a second question, is it on the roadmap to include other preprint sources, like bioRxiv?

That post is talking specifically about layers.pub datasets, which are collections of ATProto records. Papers can point to DOIs (inside the publishedVersion field). We don’t mint DOIs however, so they need to come from some other source.