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

social-app

The Bluesky Social application for Web, iOS, and Android

24Distinct people
28Mentions
0Explicit recommenders
18.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The Bluesky Social application for Web, iOS, and Android

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 year28 dated mentions

Observed mentions: 2023-05-15 22:17:26 UTC to 2026-08-26 18:25:00 UTC.

0510152023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 13 mentions; 3 submissions, 10 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 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
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC422
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC13310
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC808
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC303

What Hacker News says

8 sources
> Do they? I didn't observe any breaks when I did my DNS verification. I went to one of my posts and clicked "copy link to post." that gives me an URL like this: https://bsky.app/profile/steveklabnik.com/post/3lndppxy7xc2a If I change my account to `steveklabniklol.com`, then this URL wouldn't work, as that url turns into https://bsky.app/profile/steveklabniklol.com/post/3lndppxy7x... See here for more: https://github.com/bluesky-social/social-app/issues/1221 > People are paying attention to the Display Handle and not the address one I agree, and that's why people don't like changing it. > it doesn't seem like Bluesky's implementation will do this It does.
In A new form of verification on Bluesky
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
Agreed and there's also the problem that on Bluesky, one user blocking another means that the thread of conversation gets broken for everyone else who may read it. See e.g. https://github.com/bluesky-social/social-app/issues/7021 > As it stands, if 20 people are involved in a discussion, and ONE single person decides to block someone, then all of a sudden, the 19 other people in the discussion (+ any other viewers) are now inconvenienced simply because one person had an issue with someone else. > Bluesky does have a bit of a block culture, and as such, this issue is only going to get worse and worse, and threads are going to get harder and harder to read and follow as more and more people get blocked. Trying to create a Reddit-like experience around this limitation would be very difficult, as the thread breakage is done server-side so the
Read the rest
clients don't even get enough info to reconstruct the conversation.
In Show HN: I Built a Reddit-style Bluesky client – still rough, but open to ideas
You have misunderstood. The way Bluesky blocking works is not just about controlling who else can interact with your posts, it affects the posts of others too, and applies to every other user whether they like it or not. See https://github.com/bluesky-social/social-app/issues/7021 for more detail. A relevant comment from that issue: > As it stands, if 20 people are involved in a discussion, and ONE single person decides to block someone, then all of a sudden, the 19 other people in the discussion (+ any other viewers) are now inconvenienced simply because one person had an issue with someone else. > Bluesky does have a bit of a block culture, and as such, this issue is only going to get worse and worse, and threads are going to get harder and harder to read and follow as more and more people get blocked. > Just the other day I got a notif
Read the rest
ication, and I clicked on it, and once again, the post they were replying to was "blocked", not because of me, but because the person who made the post blocked the person they were responding to. I was trying to make sense of their post, but now I couldn't as I had no idea what the hell they were replying to... then I think I found the post they replied to; it showed "1 reply", but when I clicked on it, no replies were shown. > Now, this functionality was probably done with good intentions - but you know what they say, "The road to hell is paved with good intentions". Another comment explaining the problem: > This is working as intended but I agree it should be reassessed. For example: > 1. In a popular thread, User A posts some nonsense > 2. User B replies to that reply explaining why it's nonsense > 3. User A blocks User B > 4. Now User A has successfully hidden the rebuttal to his comment from everyone. The only defense against this is if the thread OP happens to block User A. > This is a pretty serious downside of the "nuclear block" system imo. It creates an escalation ladder of blocking where the first user to hit "block" is advantaged. On the other hand it causes me personally to avoid blocking where I otherwise would, because I want the conversation to still be visible for others. > There should at least be a "show reply" button on posts that are hidden for this reason IMO. Otherwise you've given every user the unilateral power to hide a reply, for everyone, permanently. If I hide a reply the normal way, it's not deleted for everyone! There is a "show hidden reply" button! The effect of hiding someone else's reply should be consistent across these two ways to do it.
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.