HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
bluesky-social
atproto
TypeScript2022–2026
bluesky-social / atproto

atproto

Social networking technology created by Bluesky

42Distinct people
53Mentions
0Explicit recommenders
9.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Social networking technology created by Bluesky

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:57:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year53 dated mentions

Observed mentions: 2022-05-04 20:26:28 UTC to 2026-08-12 13:05:33 UTC.

0510152022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 10 mentions; 3 submissions, 7 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 10 mentions; 4 submissions, 6 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 10 mentions; 2 submissions, 8 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 15 mentions; 1 submissions, 14 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC1037
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC1046
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC1028
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC15114
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC808

What Hacker News says

15 sources
I think they're saying using PLC as an identity method is not tied to buying into the whole AT spec. So you can use it for something else. >Isn’t PLC tied to bluesky (or some other central authority)? Yes, PLC is currently tied to Bluesky, and is in the process of moving out into a separate legal entity (https://docs.bsky.app/blog/plc-directory-org). It would indeed remain centralized. >Why didn’t they use some mechanism for decentralisation, like a DHT (e.g. did:pkarr)? AFAIK Bluesky is open to supporting more did methods in atproto in the future as long as they can act as permanent identifiers. I found a response from Bryan about `did:dht` here: https://github.com/bluesky-social/atproto/discussions/2705#d...: >did:dht is interesting and maybe could work, for atproto, but there have been many DHT projects in the history of decentralized
Read the rest
computing, and only a small handful have really worked out. AKA, been resilient to abuse, attacks, neglect, etc, over years and decades. magnet links are cool but kind of the exception to the rule. I think if the W3C standardized did:dht it could be a real contender, but somebody needs to carry the flag and demonstrate it working "in real life" with millions of users, and I suspect that will be difficult, and I would not expect Bluesky to lead that charge (we already have our own pet DID method to maintain and support).
In Where it's at://
If you did hijack the DNS and say `TXT _atproto.<handle>` points to `did:web:mycontrol.example` then that's a plausible attack, I guess, against did:web, but not against did:plc. And it'd assume that software in between hasn't cached the previous mappings, which typically it has. This is noted in the did:web spec, which isn't from Bluesky PBC / AT Protocol: https://w3c-ccg.github.io/did-method-web/#dns-considerations I should note though, that for many implementations, that'd mean poisoning a large DNS provider like google, cloudflare or quad8, since those are the DNS servers typically queried from servers, instead of going directly to the authoritative server itself. There's more technical details here: https://github.com/bluesky-social/atproto/tree/main/packages...
In Where it's at://
Great questions! Yeah, this is something I want to write about it in the future. An app can write to PDS if the user grants it access via OAuth. Currently this access is very coarse (which is bad!) although backing up the entire repo is easy (which is good! but should be made more accessible to normies). There is an active workstream on OAuth Scopes (already partially deployed) which will let apps request more granular access (e.g. apps can write to "their own" collections but also ask to write e.g. Bluesky posts). In UI, this is done through sort of "bundles" of permissions. See https://github.com/bluesky-social/atproto/discussions/4118 for tracking issue. > what if it pretends to write data in the Bluesky format, but e.g. leaves out a field that the Bluesky Appview expects, or writes data in a different format than it expects? Atproto d
Read the rest
ata is governed by "lexicons" which are essentially type definitions used by app authors. E.g. `app.bsky.feed.post` type definition is maintained by the Bluesky team. There's a codegen that generates validation code from that definition. If validation doesn't pass, the Bluesky app server will just ignore that record. Records are generally treated by apps as untrusted input, similar to form submissions. They can be validated during ingestion or in the process of usage later.
In Where it's at://
Thanks, so are both the Postgres and Scylla versions maintained in terms of new features? I wasn't aware that AppView v1 was open source, and the most recent info I'm aware of on the topic is https://alice.bsky.sh/post/3laega7icmi2q, https://github.com/bluesky-social/atproto/discussions/2961 and https://docs.bsky.app/docs/advanced-guides/federation-archit..., and everything I've heard about Bluesky was that open source appview is "still coming".
In When imperfect systems are good: Bluesky's lossy timelines
The App View frontend is open source: https://github.com/bluesky-social/social-app Much of the backend is open source as well: https://github.com/bluesky-social/atproto/tree/main/packages What is not are the extra services they run to provide a better and faster UX. Even if it was open source, it likely costs 10s of thousands to run per month (they have moved largely to "onprem" hardware instead of the cloud aiui)
In When imperfect systems are good: Bluesky's lossy timelines
yeah, that is my understanding, if I understand your question correctly. Of course it is all hidden from view, there is a merkle tree involved, and you probably want to use a higher level client than SQL This talks about why SQLite and not Postgres https://github.com/bluesky-social/atproto/discussions/2287 Repository spec: https://atproto.com/specs/repository Small program to export: https://github.com/bluesky-social/cookbook/tree/main/go-repo...
In NFL teams can't use Bluesky
The protocol is protected. https://github.com/bluesky-social/atproto/ "Dual MIT/Apache-2.0 License Copyright (c) 2022-2024 Bluesky PBC, and Contributors Except as otherwise noted in individual files, this software is licensed under the MIT license (<http://opensource.org/licenses/MIT>), or the Apache License, Version 2.0 (<http://www.apache.org/licenses/LICENSE-2.0>). Downstream projects and end users may chose either license individually, or both together, at their discretion. The motivation for this dual-licensing is the additional software patent assurance provided by Apache 2.0." Even when Bluesky decides to fuck around with the licenses, everybody is free to fork the current version crediting Bluesky PBC due to the MIT and Apache 2.0 license allowing this. And besides that, the community could also decide not to support AT at all but
Read the rest
put their full weight behind Nostr (https://nostr.com/) UPDATE: And the protocol spec is licensed under Creative Commons: https://github.com/bluesky-social/atproto-website/ "Creative Commons Attribution (CC-BY) Copyright (c) 2022-2024 Bluesky PBC, and Contributors Documentation text and blog posts in this repository are licensed under a permissive CC-BY license. For anybody interested in derivative works of documents and specifications, remember that: - you must give attribution (credit) to the original work - you must indicate any changes made - trademark rights are not granted (for example, to "Bluesky", "AT Protocol", or "atproto", or any logos or icons) Inline code examples, example data, and regular expressions are under Creative Commons Zero (CC-0, aka Public Domain) and copy/pasted without attribution."
In We need to protect the protocol that runs Bluesky
wants to create a nonprofit foundation to govern and protect the AT Protocol, outside of Bluesky the company Bluesky and Graber recognize the importance of this effort and have signaled their approval. But the point is, it can’t rely on them. What’s the point of this article? The repo is dual MIT/Apache [0]. Nothing seems to prevent the author from forking and hacking away. Just do it. 0. https://github.com/bluesky-social/atproto
In We need to protect the protocol that runs Bluesky

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.