Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bluesky Protocol Services

atproto.com

Post reply on HN
Print view View original

51–60 of 87 posts

Re: Bluesky Protocol Services

#51

Post by eviks »

Gareth321 wrote: post #39
erryy wrote: post #30

Neat protocol, shame about the users. Also the VC-backed funding for this infrastructure will run out eventually. It's not self-sustaining, and Bluesky have no viable route to profitability.

[Bluesky proves that for social media, no matter what your technology stack, capabilities, or mission, if your community is awful, growth will never follow.]( https://blueskyfeeds.com/bluesky-user-growth?t=3m )

> no matter what your technology stack, capabilities

We haven't had many of the good sets of these to get any proof

Re: Bluesky Protocol Services

#56

Post by [deleted] »

afavour wrote: post #40
gkbrk wrote: post #35

Earlier quoted context omitted.

It still has an internal GraphQL API. How would the official web app and mobile apps work without an API?

Right but that doesn’t mean anything about authorisation. If you’re using a key you ripped from an official app you could easily be blocked tomorrow. Makes the effort considerably less worthwhile.

[deleted]

Re: Bluesky Protocol Services

#57

Post by josephg »

inigyou wrote: post #43
josephg wrote: post #27

Earlier quoted context omitted.

What baby? DNS doesn't have the double spend problem. Why is the blockchain good for this?

The double spend problem for domains is the double domain purchase problem. I claim example.com and you also claim it, who wins?

Whoever buys it first. With a centralised database, this is trivial.

Usernames are the same. Who gets @example.bsky.social ? Whoever registers it first. Problem solved.

Re: Bluesky Protocol Services

#59

Post by josephg »

inigyou wrote: post #36
josephg wrote: post #10

I wonder if it would be a good idea to remake DNS on top of bluesky. The basic idea is that, if you own a domain name, you post DNS updates in a bluesky feed. The firehose itself is authoritative. DNS servers sit downstream of the firehose. All the updates to domain names get written into a database, and they essentially just respond to queries hitting that database. This would let anyone (with enough bandwidth) run…

How do you prove you own a domain with no records?

We’d need a registry of some sort. And a name space. Register a name, associated to a Bluesky account. Then use that Bluesky account to update dns records.
Post reply on HN