Earlier quoted context omitted.
Skeets
Bleats
Firesky – The Bluesky Firehose
31–38 of 38 posts
Re: Firesky – The Bluesky Firehose
#32This is amazing & will obviously never last. :/
Re: Firesky – The Bluesky Firehose
#33This looks so cool! Are there any resources on how to build your own systems to post to the protocol, and read from it? Would be so useful as a generalized automated events messenger service
https://github.com/bluesky-social/atproto-ecosystem provides a good overview of the current ecosystem. If you wanna see how something is done, best to find another project already doing it and get inspired from them.
Re: Firesky – The Bluesky Firehose
#34Re: Firesky – The Bluesky Firehose
#35Would be cool to hook this up into a Bluesky network graph like [0] and pulse the node every time someone posts. Some interesting patterns might emerge. [0] https://bsky.jazco.dev/
Re: Firesky – The Bluesky Firehose
#36I feel like this unfiltered format is going to make any Twitter-like site look awful. But having said that, looking at this, I don't have any desire to get an account on bluesky. There's still lots of content/people like this on Twitter.
The biggest “killer feature” is also its biggest detractment. The existing cool kids are already invited and building their base. Little people like you and me (regardless of our successes and personal prestige) are still excluded. I will continue to regard this as just another echo chamber
Re: Firesky – The Bluesky Firehose
#37Earlier quoted context omitted.
I thought BlueSky was a protocol, not just a service. How can there be only one instance of a protocol?
Bluesky is the app/one UI. AT Protocol is the protocol. Currently there is only one widely used implementation of the protocol. Probably because they're still working out exactly how federation will be added to the protocol.