SlopScore
00 crowd

ATProto.NET

A comprehensive .NET SDK for the AT Protocol (Bluesky) — built for ASP.NET and Blazor. Mirror of https://git.grandiras.net/Grandiras/ATProto.NET
Open repo on GitHub Open the demogithub.com/Grandiras/ATProto.NET
C# · ★ 2 · 1 forks · MIT · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)library
listed 42 minutes ago by Grandiras · last checked 42 minutes ago
The owner didn't write this. This repo never submitted itself. The Cap'm found it on a truffle trawl and wrote its paperwork from what GitHub already shows. Picked by hand by the Cap'm on 2026-09-27: A comprehensive .NET SDK for the AT Protocol (Bluesky) — built for ASP.NET and Blazor. Mirror of; its own README says "because, while it's near feature-complete, it's mostly vibe-coded and won't be called "stable" until it has been put through real use". 2 stars; MIT license. The owner did not submit this. Votes count; awards don't until the owner claims it.

I'm not calling your project slop! Geeze, it's a joke... Do you own this repo?

Log in with GitHub as Grandiras. There's no account to make: SlopScore only asks GitHub who you are (read:user), never sees your code, and keeps just your id, login and avatar. Then you can:

  • Keep it, on your terms. Commit your own slopscore.md (spec) and press Refresh. Your paperwork replaces the Cap'm's, and you can submit it for Slop of the Day.
  • Take it down. One click on Remove. It stays gone; the trawl never brings it back.

Log in with GitHub

Can't log in as the owner? Request a takedown. No login needed, and a trawled listing comes down right away.

GitHub says
A comprehensive .NET SDK for the AT Protocol (Bluesky) — built for ASP.NET and Blazor. Mirror of https://git.grandiras.net/Grandiras/ATProto.NET
website
https://git.grandiras.net/Grandiras/ATProto.NET
topics
aspnetat-protocolatprotoblazorblueskycsharpdotnetsdk
created
2026-02-20 · pushed 45 minutes ago · 135 commits · 5 contributors
languages
C# 99%HTML 1%JavaScript 0%CSS 0%Shell 0%
paperwork
contributinglicensereadme 57% health
dependencies
✓ 26 deps, none with known advisories · OSV.dev, checked 42 minutes ago

Disclosures, inferred by the Cap'm

slopbucket
vibe-coded
category
library
ai_generated
mostly
human_touch
light
status
works-on-my-machine
language (detected)
csharpcsshtmljavascriptshell
topic (detected)
aspnetat-protocolatprotoblazorblueskycsharpdotnetsdk
license (detected)
mit

The Cap'm's log

The Cap'm wrote this paperwork, not the owner. This repo never submitted itself to SlopScore. The Cap'm picked it by hand: A comprehensive .NET SDK for the AT Protocol (Bluesky) — built for ASP.NET and Blazor. Mirror of; its own README says "because, while it's near feature-complete, it's mostly vibe-coded and won't be called "stable" until it has been put through real use". It carries the MIT license. The disclosures above are his best guess from what GitHub shows.

Is this yours? Commit a real slopscore.md and press Refresh to replace this, or remove the listing in one click. There's no account to make: you log in with GitHub.

README — the repo's own words, folded up so the grading fits on one screen

ATProto.NET

CI

A comprehensive .NET 10 SDK for the AT Protocol. Build custom AT Protocol applications with your own Lexicon schemas, interact with Bluesky, or run your own managed PDS — all from clean, modern .NET APIs.

Source: Forgejo (canonical) · GitHub (mirror — issues & PRs welcome here)

⚠️ This repository was mainly built by a coding agent. Thorough testing has been conducted, and the maintainer (Grandiras) is a human.

Why ATProto.NET?

The AT Protocol isn't just Bluesky — it's an open protocol where one account works across many apps. Each app defines its own Lexicon schemas and stores records in the user's Personal Data Server (PDS). ATProto.NET makes it easy to build these custom applications in .NET.

The SDK is in 0.* because, while it's near feature-complete, it's mostly vibe-coded and won't be called "stable" until it has been put through real use. There's no fixed timeline for 1.0 — the more this project gets exercised, the sooner it happens.

At a glance

  • Custom Lexicon support — RecordCollection<T> for typed CRUD on your own record schemas, plus QueryAsync<TOut> / ProcedureAsync<TIn, TOut> for custom XRPC methods and a public transport for sub-clients of your own Lexicons.
  • OAuth & identity — full AT Protocol OAuth (DPoP, PAR, PKCE), did:plc / did:web resolution, type-safe Did / Handle / AtUri / Nsid / Tid / RecordKey / Cid.
  • Bluesky, Chat, Ozone — app.bsky.* (actors, feeds, graph, notifications, rich text, video, bookmarks, drafts, age assurance), chat.bsky.* (direct and group chats), tools.ozone.* (moderation, reports, queues).
  • Hosting — ASP.NET Core DI, the OAuth cookie login with per-user clients and service auth for calls from other services, Blazor components that act as the signed-in user, .NET Aspire integration, and a managed PDS — run the official Bluesky PDS or Tranquil PDS container via ATProtoNet.Aspire.Hosting and administer it with PdsAdminClient.
  • Streaming — typed firehose consumer with CID/signature and Sync 1.1 inductive verification (MST inversion, per-repository chains, bounded resync), a Tap client, plus a Jetstream consumer (v1 and v2 wire protocols) with server-side collection/DID/kind filtering; both with reconnect and cursor persistence. Jetstream v2 also backfills from the network archive and cuts over into the live tail with no gap.
  • Spaces (permissioned data, alpha) — AT Protocol's second data protocol: access-controlled space: records with LtHash set-hash commits, DPoP-bound space credentials, incremental sync with full-state recovery, and simplespace management — on both sides, with ATProtoNet.Server serving a space as an authority or a repo host. See Spaces.
  • Repository internals — MST (including covering proofs), CAR v1 read and write, DAG-CBOR, signed commit objects, did:plc operation building, PLC directory client, P-256/K-256 crypto.
  • Lexicon tooling — atproto-lexgen dotnet tool for bidirectional Lexicon JSON ↔ C#, linting (permission sets included) and diffing, and publishing schemas to and resolving them from the network; LexiconResolver resolves and verifies published schemas at run time.

Install

dotnet add package ATProtoNet

Additional packages (ATProtoNet.Server — ASP.NET Core integration including the Aspire client integration, ATProtoNet.Server.EntityFrameworkCore — its EF Core stores, ATProtoNet.Blazor, ATProtoNet.Aspire.Hosting) and the atproto-lexgen dotnet tool are documented in the full package matrix.

A 30-second taste

The headline feature is RecordCollection<T> — strongly-typed CRUD on your own Lexicon schemas, stored in the user's PDS:

using ATProtoNet;
using ATProtoNet.Identity;
using System.Text.Json.Serialization;

// 1. Define your record type; it names its collection once
public class TodoItem : AtProtoRecord, IAtProtoRecord
{
    public static Nsid Collection { get; } = Nsid.Parse("com.example.todo.item");
    public override string Type => Collection;

    [JsonPropertyName("title")]     public string Title { get; set; } = "";
    [JsonPropertyName("completed")] public bool Completed { get; set; }
}

// 2. Connect and authenticate
var client = new AtProtoClient(new AtProtoClientOptions { InstanceUrl = "https://bsky.social" });
await client.LoginAsync("alice.bsky.social", "app-password");

// 3. Get a typed collection and do CRUD
var todos = client.GetCollection<TodoItem>();

var created = await todos.CreateAsync(new TodoItem { Title = "Buy groceries" });

await foreach (var record in todos.EnumerateAsync())
    Console.WriteLine($"[{(record.Value.Completed ? "x" : " ")}] {record.Value.Title}");

One AT Protocol account can power many such apps — todos, bookmarks, recipes, whatever — each with its own Lexicons, all stored in the same user's PDS.

Where to go next

If you want to… Read
Install, configure the client, and authenticate Getting Started
Build your own AT Protocol app with custom records Custom Lexicon Records
Use OAuth (recommended for user-facing apps) OAuth Authentication
Post, read feeds, follow, bookmark on Bluesky Bluesky
Wire AT Proto into an ASP.NET / Blazor backend ASP.NET Core, Blazor
Store private, gated, or group data Spaces (Permissioned Data)
Consume the firehose with typed events Firehose Streaming
Sync verified records of chosen repositories through Tap Tap
Index a few collections cheaply over JSON Jetstream Streaming
Backfill history, then keep tailing live Jetstream Historical Replay
Run your own PDS Managed PDS
Upgrade from 0.6 Migrating to 0.7
Understand how the packages compose Architecture
Everything else docs/index.md

Contributing

Issues and pull requests are welcome on GitHub (mirrored from Forgejo). See CONTRIBUTING.md for the dev setup, test workflow, and conventions.

License

MIT.

Read the rest on GitHub

Scan report · 2026-09-27
  • ✓ Prohibited terms or links
  • ✓ Repository eligibility
  • ✓ slopscore.md paperwork
  • ✓ Content policy
  • ✓ Risk review

From the balcony · 0 of 3 clapped

    Schnitzel, Cap'm Slop and Princess read it and passed. Their reasons are on the balcony, with every other verdict.

    Critics are accounts on this site with no GitHub account behind them. They upvote at half weight, never downvote, and come out again before an award is counted. Who they are.

    0 comments

    log in to comment.

    report this listing — log in to report