Select * from Internet.blogposts

For blog posts, I'd look to RSS instead. That's where that content is traditionally published. Instead of SELECTing from bluesky's index, you can use OPML subscription lists. There are a bunch of places that curate feed lists, so it's significantly less likely to face API death like twitter did. There are multiple sites that support follower semantics over RSS. Feedland tracks subscriptions publicly, so you can see the blogs I read (https://feedland.com/?username=robalexdev), and who reads my blog (https://feedland.com/?feedurl=https%3A%2F%2Falexsci.com%2Fbl...). I run another variant which collects OPML blogrolls via crawling, so you can find out who else likes your favorite blog and what else they recommend. Here's the page for Simon Willison's blog (https://blogroll-network.alexsci.com/discover/feed-a34ee2a88...). Thinking of RSS and blogrolls as a network feels much more resilient than blueskys Jetstream api endpoint.

>Simple: the network won. The developers stopped being an asset, and the API progressively closed. You can add Reddit to that list, IPO is coming so better price out the third party apps we encouraged developers to build.

At first, I thought that the fraction of people who want this kind of network of peers would be rather small. I thought that almost all people want extensive restrictions on user agents and controlling how the data is revealed to the user. But Bluesky actually does not restrict AI scraping and consumption of data. You're just yet another consumer, subject to rate-limiting etc. whether you are browser or headless agent. I have to say that I am somewhat (pleasantly) surprised that this approach is accepted by Bluesky considering the community is more anti-AI than most. The fact that you're allowed to consume the feed is amazing. Good stuff!

> The web is a few dozen companies, each holding a filing cabinet, each with a receptionist posted out front. He'll read you one file at a time, but only files you can name, as fast as he cares to read, and as long as his boss allows. Fortunately this isn't true. Social media consists of a few big walled gardens, but the web itself is still open. Go forth and create a website!

There have been so, so many attempts to decentralize in my lifetime. I used to be a huge believer and worked on these problems, but have to admit I'm somewhat exhausted. The technology is not the problem. The problem is always quality, effort, and cost. If decentralization is ever going to win, it needs to be turnkey, explained without showing a network diagram, be basically free to run on your laptop, and actually have the content people want to see and not just be a bunch of people who speak lojban. [1] While I'm not sure how much of a legal leg X has to stand on, I understand why they'd rather Nitter not exist. Twitter tried (valiantly, imo) to stay open. What ultimately began the API lockdown was the need to stop bleeding financially. Ads were inevitable, and there being no reliable way to do that via API access. Twitter solved those three problems, and no one spends nearly as much time talking or caring about the technology used to do it than people who talk about decentralization. Myself included in my younger days. Now they're just defending their moat. 1: https://xkcd.com/191/