Select * from Internet.blogposts
pfrazee.leaflet.pub43 points by mmattbtw 4 hours ago
43 points by mmattbtw 4 hours ago
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.
> Thinking of RSS and blogrolls as a network feels much more resilient than blueskys Jetstream api endpoint.
Nothing to do with Bluesky services. There are many independent firehoses and relays. Here's a stream of standard.site blog posts coming in over a firehose hosted in Chennai. Every single one. No curator between me and the posts, and no work by me to crawl the whole network for them. https://pdsls.dev/jetstream?instance=wss%3A%2F%2Fchennai.fir...
Edit: ok there is an aggregator, the relay is scraping all of the PDSs out there to build the event stream. Notably this is not possible with RSS, where you need to build a large index with knowledge. PDSs request relays to crawl and that's that.
>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.
ATProto has the hardest working developer relations department in the game right now.
I can't decide if ATProto is actually amazing or if its proponents are just dazzled by their own tech. Is it truly decentralized? What makes it better than Mastodon or Matrix or Scuttlebutt? Of course, at the end of the day, it's the network effects that matter. Attention is all you need indeed.
The team came from the IPFS and Scuttlebutt worlds. "Better" is relative to your design goals. Iroh is better for point-to-point connections & localfirst. Matrix is better for chat rooms. Etc. The general logic of atproto was to serve large scale publishing with an open model that doesn't seriously degrade the UX. The scale orientation means - at least until the non-public spaces land - you're syncing a lot of records to provide an alternative microblogger to bluesky. The account hosting system, however - the pds - remains exceedingly cheap and easy to run. Pros and cons, matching with the design goals.
I will say that I have no relation to bluesky so it's not my tech and I do find it amazing. This post from Dan Abramov might help in clarifying how 'decentralized' it is compared to the threadiverse https://overreacted.io/there-are-no-instances-in-atproto/
The Twitter-competitive social site is moribund, so I think maybe what you're seeing more and more of is the pivot towards infrastructure --- always planned, but not before such a big part of the messaging.
There are invariably 3 solutions to all “federated” web problems:
- Semantic HTML
- Web indexing services
In this case, it's mostly indexing and a little of the other two if you want to add social features. I despite ATProto with all my soul for taking a problem with such a simple and standard solution and totally obscuring it behind hundreds of layers of JSON, faux federated services, and technical jargon, all in service of creating an inferior version of Twitter. I guess it wouldn't be as sexy to offer a web indexing service instead.
Genuinely curious, how would you build it differently? Would you stick with atproto's indexing model and try to simplify it, or would you use another approach?
You send a request to a web indexer with a page you want added to the network, it scans your page for outgoing links and sends an email to the owners of any domains who are also on the service.
One can imagine making it a little more featureful, for instance indexing OPML blogrolls which would allow you to see whom a person follows and https://microformats.org/wiki/h-entry which would allow outgoing links to be categorised (like, reply, etc) so notifications filtered. With that, it would be possible to add a front-end site imitating one of the popular social media paradigms (Reddit-style or Twitter-style being the most obvious).
If there's one genuine design decision I would give for it beyond what is basically a cobbling together of existing interfaces, it would be to charge users per page uploaded. Likely very detrimental to growing the service, but I think one of the simplest ways to weed out spam and junk. A real problem with many web services is that the receiver of the message pays for it in terms of attention, where in other mediums the sender has to pay. Given that uploading crap is basically free, that's all you get. Increasing the cost of upload would weed out those endless AI summaries and lists of affiliate links.
The issue with ATProto is that it operates on too many layers. You can see lacking in what I have described here the concept of durable authorship, but this is a property of content not how the content is distributed. Perhaps someone will invent a standard way to sign HTML documents, in which case you could base user accounts on that instead of DNS. AT enforces this centrally but it does not need to. It is walling itself off from the common and decentralised software ecosystem of the web for no good reason.
Yeah that'd be interesting to try. If you extend the endpoints and the vocabularies around RSS/OPML enough, you could likely create a fairly robust dataset replication protocol. Microformats are a decent schema basis, but you might want to build upon them as well. If you want to make the users' sites reusable as a datastore across applications, you could introduce an oauth flow to enable 3rd party writes. You might also want to add content signatures so you can verify the data authenticity from third parties (e.g. to support the equivalent of reposts).
I'm sorry, but this blog post is written as if the described functionality should obviously be available and supported by the Internet and companies who expose their data.
I agree it would be neat.
But, when did we conclude this "should" be possible and thus warrant such a whiny post?
Not a would be cool, is cool. At least now that the atproto network has proved it is in fact cool.