This is wild but also not the first time I’ve seen reference to nonsense like this 😅 Multi-authenticated authorship is possible with atproto, yes? 😇 @chive.pub @atproto.science
Jean Léon Maître
I have seen a paper being published by the first author without any of the other authors being aware of it. 1st author made bogus Gmail addresses. Pretty wild 😱 I don't think asking for all of this contact info will help prevent a motivated fraudster though. Only annoying the rest of us 😮💨
Jul 16, 2026 at 3:47 AM
Understanding ATProtoFans: A Technical Deep Dive into Verifiable Creator Support - ATProtoFans Blog
Building Unforgeable Professional Endorsements with ATProtocol - Nick's Blog
Traditional professional endorsements on platforms like LinkedIn lack cryptographic proof—anyone could forge them, and the platform controls the truth. This article introduces a two-record architecture using ATProtocol's Content Identifiers (CIDs) and Decentralized Identifiers (DIDs) to create mathematically unforgeable mutual attestations. By separating proof creation from endorsement acceptance and leveraging the firehose for distributed validation, we build a system where both parties cryptographically consent and no central authority can manipulate the record.
asq.fyi — ask anyone, anything (on atproto)
A public square for questions both silly and serious. Built on the AT Protocol, so your account, followers, and answers belong to you — not us.
ATProtoFans - Support Your Favorite Creators
Decentralized supporter attestation service for the ATProtocol ecosystem. Support creators with cryptographically verifiable relationships.
ATProtoFans - Support Your Favorite Creators
Decentralized supporter attestation service for the ATProtocol ecosystem. Support creators with cryptographically verifiable relationships.
Account delegation for atproto: orgs, aliases, alts and more - Nel Ramblings
Introducing ATProtoFans: A New Way to Support Creators You Love - ATProtoFans Blog
Who Actually Owns Your ATProto Identity? Hint: It's Probably Not You
ATProto gives your PDS operator full control of your signing and rotation keys, letting them impersonate you across every app in the ecosystem or kill
This is wild but also not the first time I’ve seen reference to nonsense like this 😅 Multi-authenticated authorship is possible with atproto, yes? 😇 @chive.pub @atproto.science
Jean Léon Maître
I have seen a paper being published by the first author without any of the other authors being aware of it. 1st author made bogus Gmail addresses. Pretty wild 😱 I don't think asking for all of this contact info will help prevent a motivated fraudster though. Only annoying the rest of us 😮💨
Have had this conversation more than once that essentially having to buy a domain and host a distinct machine for every single idea to be a poc in ATProto sux
Graham
Tbh the main reason I’ve been averse to publishing lexicons is that I felt it was necessary to do so under brand accounts for each project. Nevermind the breaking changes, I haven’t had enough users to worry about that—I just didn’t want to juggle so many identities.
We're thinking about publishing a compendium of #ATScience projects submitted to the workshop (incl abstracts, preprints and published works) - @aaronstevenwhite.io could @chive.pub potentially support that use case?
Yep. This is what is missing in the ATProto vision. The lexicons should've been a like schema.org instead of domain name-based. Everyone who wants to improve it can discuss it, similar to, well, schema.org. The frontend must be separate from the content. It's beneficial in many ways.
jack
we have standard.site but wen standard.pics? rn I’m juggling between @grain.social, @flashes.blue & @sprk.so for image sharing 😭
Well, atproto *is* an open protocol so... I'm looking into an excension of the schema to allow accounts that are declaring that they're automated to optionally declare details about that automation, including an operator, a purpose, even an interaction model. Aids in both discovery and moderation!
