Post

I see a huge opportunity for how the AT Protocol could reshape academic publishing. Imagine researchers publishing continuously and atomically — before, during, and after research projects — in public connected continuous streams of discovery and insight.

Leaflet@leaflet.pub

Some notes on how we can make Leaflet more useful for scientists and academic communities — touching on things like annotation, standalone doc publishing, new block types, post reactions, references & backlinks… Second in a series, and intended as a living doc — we'd love to hear your thoughts!

7 reposts27 likes

This protocol has the potential to turn research into an open conversation — not a gated archive with peaks of occasional information releases. It would protect ownership, credit, and integrity while 100X the time to the next big discovery or paradigm shift. (A new home/model for preprints?)

Publishing atomically through the AT Protocol could let researchers build and share work across their entire careers — transparently, collaboratively, and safely — without fear of being scooped or losing rights. (A viable replacement for ORCID?)

More than any emergent tech I’ve seen in the past decade, I believe the AT Protocol has the right foundational elements to make this real: open standards, interoperability, collaboration, and individual ownership, all in the DNA.

Verifiable identities, the PDS, shared lexicons for documents, data, and soon maybe peer review and indexing, plus labelers and moderation lists to surface quality, uphold research integrity, mitigate bad actors, and feeds to support discovery.

Great question. #ATproto is the open, decentralised social web protocol that powers Bluesky. It’s built around a portable identity, personal data servers (PDS) where *all* *my* stuff is stored, and “lexicons” (definition of any “thing” that can be written/read by anyone/anything on the network).

A “book” lexicon has a title, author, ISBN, date published, cover art, license, and content… so anyone could create/sell/share/read it on AT. The data stays *in the author’s PDS*. Authors, publishers, book reviews, book collections, licenses, etc could also be defined and reused widely.

I’m simplifying but this foundation lets people and apps interoperate freely without a single company owning the network or data trafficked across it.