I agree with Nick that you have noted a big hard problem, with Zooko’s triangle type trade-offs. (For a semi-related example that is “easier” but still crazy difficult, see our “PeerFlow: Secure Load Balancing in Tor” https://doi.org/10.1515/popets-2017-0017 ) As noted or implied already in this thread: in the end, if someone can cheaply spin up indefinite unlinked identities and build good reputations for them, and if trust is based on such reputations, it is hard (impossible?) to avoid them s...
Rashid Aziz: Extending ATproto for private data - ATProto Community
EigenTrust
The EigenTrust algorithm is a reputation management algorithm for peer-to-peer networks, developed by Sep Kamvar, Mario Schlosser, and Hector Garcia-Molina.[1] The algorithm provides each peer in the network a unique global trust value based on the peer's history of uploads and thus aims to reduce the number of inauthentic files in a P2P network. It has been cited by approximately 5800 other articles according to Google Scholar.[2]
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.
Introducing attested.network: Proof of Payment for ATProtocol - Nick's Blog
attested.network is an open spec for decentralized proof of payments on ATProtocol, built on what we learned making atprotofans.com. It formalizes the three-party attestation model and opens it up for any app to implement.
A Model for addressing privacy on ATproto
When I first got involved with Northsky social, we knew we would have to eventually address the elephant in the room. How do we proactively protect a community from outside influences without relying purely on moderation? And more importantly, how do we keep bad actors from simply pulling their data straight from a relay?
LinkedClaims — Decentralized Verifiable Claims on ATProto
LinkedClaims: publish and verify decentralized claims about any URI-addressable subject on the AT Protocol. Open standard by DIF Labs.
attested.network — Proof of Payment for ATProtocol
An open specification for decentralized, cryptographically verifiable proof of payments.
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.
About Atproto w/ Dan Abramov | Wireframe Live
About Atproto w/ Dan Abramov | Wireframe Live
As atproto matures, adversarial actors will reveal all the places where trust is implicit rather than managed - maybe time to build reputation mechanisms for PDSs like we do for email servers? It'll likely need to be default-block/prove-healthy, or default throttle until proven typical?
Scoiattolo
They've got a huge network that I'm in the process of graphing. They're now setting up their own PDSes. It's sophisticated.
As atproto matures, adversarial actors will reveal all the places where trust is implicit rather than managed - maybe time to build reputation mechanisms for PDSs like we do for email servers? It'll likely need to be default-block/prove-healthy, or default throttle until proven typical?
Scoiattolo
They've got a huge network that I'm in the process of graphing. They're now setting up their own PDSes. It's sophisticated.
this is kinda another reason im starting to think more and more that there would be worth in splitting atprotos identity layer out as its own spec and standard. building up handles and oauth around a DID makes for a really flexible cross platform (and potentially cross ecosystem) identity system
Nelind
i kinda hate how atproto adopting DIDs has made people intrinsically associate DIDs with atproto ... it makes some people see me as some annoying bitch trying to shove atproto into places it obviously doesnt belong in when i suggest using DIDs as user identifiers for other systems
If WSocial sold people on the idea that everyone they would interact with is ID-verified, then indeed, every single open ATProto community would act as a back door of sorts. The only way for them to deliver would be to de-federate entirely. And it's always a bad idea to bet against openness.
Wimster9030 🇪🇺 🇧🇪
I know, Daniel, but that's not the way WSocial "sold" it to us. We could only access trough ID-verification so we know for 100% they are EU and a "real person". That was the whole point. So we went trough that process, but now it seems that the backdoor are the other ATProt platforms to get in too.
