Bluesky signups are now open to the public

Original Article ↗ Hacker News Discussion ↗

Bluesky, a decentralized Twitter-style social network built on the AT Protocol, has opened signups to the public, prompting renewed scrutiny of its technical choices, culture, and long-term viability. Commenters weigh its promises of account portability, pluggable moderation, and third‑party feeds against concerns over VC funding, unclear business models, mandatory phone verification, and a user culture some see as an insular “Twitter 2014” remake. Many compare it to Mastodon and Threads, questioning whether any new microblogging platform can escape enshittification, bot problems, and outrage-driven feeds—or whether smaller, topic-focused communities are a better path forward.

Overview & Context

  • Bluesky removed its invite-only gate, prompting discussion of its goals as a decentralized Twitter-like network.
  • Several commenters treat this as a significant milestone, but others feel the move is late relative to the peak “Twitter exodus.”

Protocol, Federation, and Technical Design

  • Bluesky uses its own AT Protocol instead of ActivityPub; a core rationale given is strong account portability (moving identity, data, and social graph between servers).
  • Architecture: per-user repositories in many SQLite DBs, ScyllaDB-based global index (“AppView”), standalone personal data servers (PDS), and relays that aggregate data for subscribers.
  • Open federation on the production network is promised “this month”; anyone will be able to run PDSes and relays.
  • Bridges to ActivityPub (e.g., via BridgyFed) exist, but full native interop with Mastodon is not present.

Moderation, Culture, and Feeds

  • Key feature: composable, “stackable” moderation lists run by third parties; users can opt in to different labeling/filtering services, including none.
  • Some see this as a major advantage for federated social media; others worry it just re-creates arbitrary instance-level power or deepens “filter bubbles.”
  • Early culture emphasizes aggressive blocking; some like this as troll/bot defense, others see it as overzealous and fragmenting.
  • Default/Discover feeds are widely criticized as dominated by US politics, meta-discussion about Twitter, and niche subcultures (e.g., furries), with weak alignment to stated interests.
  • Custom algorithmic feeds (third-party-defined filters over the public firehose) are praised as a powerful but poorly surfaced feature.

Identity, Signups, and Privacy

  • Handles: many desired simple usernames are taken; Bluesky encourages using personal domains as handles, which some like and others find impractical or namespace-confusing.
  • Concerns about needing two accounts (bsky.social and own-domain) to prevent brand impersonation.
  • New public signup requires SMS phone verification and date of birth; justified as an anti-bot and minor-safety measure, but heavily criticized as privacy-hostile, easily bypassed by bad actors, and buggy for some international numbers.
  • Self-hosted PDSes will not be required to do SMS verification, but questions remain on how the network will handle abusive or spammy external PDSes.

Business Model and Trust

  • Bluesky is VC-funded; commenters repeatedly question the absence of a clear, detailed business model and fear eventual ad-driven “enshittification” or closure.
  • Team references a prior blog post about selling domains and says finances are stable for now with a small team and a goal of long-term sustainability.
  • Some are skeptical that “locked open” protocol design can truly prevent future centralization or walled-garden behavior, citing history with other platforms; others counter that open protocols plus third-party servers/clients are still a real improvement.

Comparisons to Other Platforms

  • Versus Mastodon/ActivityPub: Bluesky is seen as more polished and “normie-friendly” by some; others argue Mastodon already has (partial) account migration and that efforts should focus on improving ActivityPub rather than inventing a new protocol.
  • Versus Threads: Threads has large user numbers and early ActivityPub federation steps; some view its AP work as regulatory theatre rather than genuine commitment.
  • Versus Twitter/X: Bluesky feels like early Twitter (fewer gifs/video, more text jokes) to some; others say it has simply inherited Twitter-style outrage culture.
  • Some commenters prefer Mastodon, Lemmy, or Nostr on ideological or technical grounds; a few describe Bluesky as an ideological echo chamber.

Adoption, Timing, and Social Media Fatigue

  • Several users think Bluesky’s long invite period squandered the best migration window and that key communities (especially tech, AI, finance) stayed on Twitter, Mastodon, or Threads.
  • Others report low engagement or “quiet” timelines, despite some niche feeds and communities.
  • Many express general burnout on “yet another social network,” preference for smaller/niche or forum-style communities, and distrust of any new, centralized or VC-backed social platform, regardless of protocol openness.