←back to thread

239 points colinprince | 8 comments | | HN request time: 0.6s | source | bottom
1. hobs ◴[] No.42152933[source]
I dont understand why I would build on bluesky when it seems like it would have the same medium term issues that the twitter api had anyway, but enjoy it while it lasts I guess.
replies(1): >>42153082 #
2. marviel ◴[] No.42153082[source]
say more? I thought the protocol was designed to be able to handle decentralization
replies(2): >>42153266 #>>42153304 #
3. koolala ◴[] No.42153266[source]
So a firehose isn't different than re-hosting Bluesky and it encourages re-hosting?
replies(1): >>42153289 #
4. marviel ◴[] No.42153289{3}[source]
If you're critiquing, could you spell out your point more plainly?
replies(1): >>42184839 #
5. Zamiel_Snawley ◴[] No.42153304[source]
There is still major centralization. Essentially, the relays crawl the network and provide an aggregated data stream, their firehose.

Independent relays can exist, which is better than the fully centralized options.

There is no financial incentive to bear the cost of running a public relay.

replies(1): >>42153383 #
6. marviel ◴[] No.42153383{3}[source]
Thank you for the explanation!

Are there efforts to build a similar type of network which rewards running a public relay? I'm not sure how, for instance, Mastodon solves this problem

replies(1): >>42153469 #
7. Zamiel_Snawley ◴[] No.42153469{4}[source]
Mastodon has a completely different architecture.

In Activity Pub each node is essentially the full stack of what ATProto breaks up into individual entities. This means that each node in the fediverse is incented to connect to other nodes in the network, to provide good coverage to their users.

8. koolala ◴[] No.42184839{4}[source]
I was just trying to extrapolate. Seems like if you can manage the firehose you could almost host your own indepenant non-central interface.