Lightnews — Scholar-powered news

Nick Gerakines @ngerakines.me · 4h

You did it! 🎉

Nick Gerakines @ngerakines.me · 8h

I want to learn more about how content goes from the PDS on create / put record events to the firehose. Anyone have any reference code, tutorials, or examples that breaks down the process at a technical level? I want to really get into the nitty gritty technical details. #ATProtocol #ATDev

1 1 12

Reposted by Nick Gerakines

Graze Social @graze.social · 11h

Huge milestone today! As of this morning, *Over 20%* of all ATProto accounts have accessed feeds powered by @graze.social. We're just about to surpass 8m lifetime readers, all looking for a new way to control their experiences online. On to the next 8m!

A juggler of worlds, https://pdimagearchive.org/images/3608ac54-4339-4583-99e2-3447dd1ae8c2/

2 4 48

Nick Gerakines @ngerakines.me · 10h

Yeah, it would be in the form of inline attestations / proofs.

1

Nick Gerakines @ngerakines.me · 11h

Tickets to Montreal booked 👀

1 8

Nick Gerakines @ngerakines.me · 12h

Check out @slices.network

Slices - Build AT Protocol AppViews in minutes, not months

The complete development platform for AT Protocol applications. Deploy schemas, query indexed data, authenticate users. Everything you need to ship your AppView.

slices.network

1 2

Reposted by Nick Gerakines

Laurens @laurenshof.online · 13h

this weeks fediverse news, with some more on Tumblr-like platform Wafrn. it connects natively to both the fediverse and Bluesky, and you can now migrate your Bluesky account to a Wafrn server

connectedplaces.online/reports/fedi...

Fediverse Report – #138

A closer look at the Tumblr-like platform Wafrn, and Loops is getting closer to federating.

connectedplaces.online

17 38

Nick Gerakines @ngerakines.me · 19h

“lowest-common denominator protocol development” oof

Happens everywhere too. This is why I refused to use the pin emoji bookmark tooling.

Emelia @thisismissem.social · 20h

So a funny thing people in the ActivityPub world love to hate on is AT Protocol's lexicons, claiming they make interoperability between different software harder.

Meanwhile a new TikTok like platform just joined the Fediverse. Guess what object type they use for federation! Is it going to be Video?

1 20

Nick Gerakines @ngerakines.me · 20h

Just to be clear, every record you create in your repository is “signed” with the atproto key listed in your DID document. The process for endorsements and endorsement proofs isn’t adding additional signing above and beyond that.

1 3

Nick Gerakines @ngerakines.me · 1d

Tron: Ares 5/10 better than expected

4

Nick Gerakines @ngerakines.me · 1d

Very cool. I’d love to expand on that and add support to github.com/graze-social...

GitHub - graze-social/aip: ATmosphere Authentication, Identity, and Permission Proxy

ATmosphere Authentication, Identity, and Permission Proxy - graze-social/aip

github.com

1 2

Nick Gerakines @ngerakines.me · 1d

👋

1

Reposted by Nick Gerakines

Graze Social @graze.social · 1d

ATProto is a team sport - we build better together. That's why, effective today, we're opening up access to the enriched archive we use to power Graze, so anyone can build great services on top of ATProto without reinventing the wheel. Read more in the @leaflet.pub post below for details!

Announcing the Graze Archives

A brief tour of the S3 requestor-pays archives of the Graze turbostream and freshly-announced megastream

graze.leaflet.pub

10 35 150

Nick Gerakines @ngerakines.me · 1d

That's a different and unrelated problem for what this proposal and implementation does.

1 1

Nick Gerakines @ngerakines.me · 1d

I was going to wait to publish this tomorrow, but here's a more technical deep-dive into what the records and process looks like.

Unforgeable Endorsements Technical Deep-Dive - Nick's Blog

Deep technical implementation of the unforgeable endorsement system. Covers step-by-step CID computation, complete code for the endorsement workflow, validation algorithms, firehose event processing, ...

ngerakines.leaflet.pub

1 4

Nick Gerakines @ngerakines.me · 1d

For an endorsement, perhaps, but this is a general pattern that could apply to a lot of things.

Proof of payment?
Waitlist for a table?
Entitlement to a media resource?
Contract obligation?

Lots of use cases where both parties want to be able to pull the ripcord.

1

Nick Gerakines @ngerakines.me · 1d

I think this is a gap in the atprotocol ecosystem. A while ago I created a record-escrow service to support this idea that one AppView or thing may produce a record for an identity to "claim" or pick-up and have inserted into their PDS after review.

@smokesignal.events/gnosco

Gnosco is a Rust-based escrow and badging application that integrates with the AT Protocol ecosystem..

tangled.org

2

Nick Gerakines @ngerakines.me · 1d

As in how would @atwork.place determine if two identities are valid apart from resolving handles to identities and ensuring everything validates?

1

Nick Gerakines @ngerakines.me · 1d

Thanks! I think there is so much potential for applications to fully embrace transparent data and trust networks like this. I’d love to talk to them about what’s possible.

2

Nick Gerakines @ngerakines.me · 1d

This pattern generalizes beyond endorsements. Any scenario requiring mutual agreement (collaborations, peer reviews, verified relationships, etc.) can use the same two-record architecture to create verifiable trust networks.

2 7

Nick Gerakines @ngerakines.me · 1d

The consent requirement also provides protection. You can’t be endorsed for something you disagree with. You can’t have fake endorsements attached to your reputation. You have complete control over what attestations become part of your public profile.

1 3

Nick Gerakines @ngerakines.me · 1d

Because attestations live on Personal Data Servers, not platform databases, your trust network is portable. Switch PDS providers, change apps, your verified endorsements and trust relationships move with you. The network follows your identity.

1 3

Nick Gerakines @ngerakines.me · 1d

This bidirectional consent creates stronger trust signals. When you see a verified endorsement, you know both parties agreed to that specific content. Not just that Alice clicked something, but that Bob reviewed and explicitly accepted it.

1 2

Nick Gerakines @ngerakines.me · 1d

Our system requires active, cryptographic consent from both parties. Alice publishes a proof committing to specific endorsement text. Bob reviews it and decides: accept (publish matching proof) or reject (nothing becomes public). No passive acceptance.

1 4

Nick Gerakines @ngerakines.me · 1d

Traditional endorsement systems are one-sided. Alice endorses Bob by clicking a button. Bob never explicitly consents to the endorsement or its content. He might not even know it exists. This creates weak, unverified trust signals.

1 4