git.stevedylan.dev

chore: updated post 29bb63e1

Steve · 2026-01-12 06:08 1 file(s) · +2 −2

packages/client/src/content/post/standard-site-the-publishing-gateway.mdx +2 −2


Of course this idea does face its own special challenges. Standard.site lexicons will only work if they truly become the standard (clever domain by the way). If there are other competing standards that start to also gain traction then you will have issues getting everyone on the same page. With that said I think Standard.site stands a good chance: it's well thought out, simple, and people already love it. Even if more competition arises, people will generally go with whatever is the most popular and give them the most distribution. Even still, there's nothing stopping anyone from taking the same piece of content and creating multiple records to meet multiple standards to get as much attention as possible. 

The other challenge I can see is the Bluesky relay. You can run other relays and have your PDS make a request to them for scraping, but the reality is `bluesky.network` is the most popular and comes predefined if you run the main PDS implementation. With that said I think it's still early and not a huge concern right now. In truth we have a lot to thank from Bluesky with their work on ATProto and the promises it brings. I do plan to eventually get these blog posts on Standard.site lexicons as well, just a bit trickier since these are markdown posts that I would like to keep locally. If you're interested in any of the code mentioned in this post, it's all open source: 
The other challenge I can see is the Bluesky relay. You can run other relays and have your PDS make a request to them for scraping, but the reality is `bluesky.network` is the most popular and comes predefined if you run the main PDS implementation. With that said I think it's still early and not a huge concern right now. In truth we have a lot to thank from Bluesky with their work on ATProto and the promises it brings. If you're interested in any of the code mentioned in this post, it's all open source: 

- [Personal Site](https://github.com/stevedylandev/stevedylan.dev)
- [Tap Fork](https://github.com/stevedylandev/indigo/tree/main/cmd/tap)

I also plan to include a link to this post as an update on my [/now](/now) page if you want to check out the implementation and leave a comment!
I also plan to include a link to this post as an update on my [/now](/now) page if you want to check out the implementation and leave a comment! While my main blog doesn't have comments I did write a script that will now create documents on ATProto so they should be indexed as well.

Wrapping up, this experience has been a great culmination of everything I've been prioritizing with the web, that being content publishing and sharing that content through open channels like RSS. Standard.site opens up a whole new world of possibilities for that this could look like in the near future, and takes us a step closer to a truly open web that I long to see.

97	97
98	98		Of course this idea does face its own special challenges. Standard.site lexicons will only work if they truly become the standard (clever domain by the way). If there are other competing standards that start to also gain traction then you will have issues getting everyone on the same page. With that said I think Standard.site stands a good chance: it's well thought out, simple, and people already love it. Even if more competition arises, people will generally go with whatever is the most popular and give them the most distribution. Even still, there's nothing stopping anyone from taking the same piece of content and creating multiple records to meet multiple standards to get as much attention as possible.
99	99
100		-	The other challenge I can see is the Bluesky relay. You can run other relays and have your PDS make a request to them for scraping, but the reality is `bluesky.network` is the most popular and comes predefined if you run the main PDS implementation. With that said I think it's still early and not a huge concern right now. In truth we have a lot to thank from Bluesky with their work on ATProto and the promises it brings. I do plan to eventually get these blog posts on Standard.site lexicons as well, just a bit trickier since these are markdown posts that I would like to keep locally. If you're interested in any of the code mentioned in this post, it's all open source:
	100	+	The other challenge I can see is the Bluesky relay. You can run other relays and have your PDS make a request to them for scraping, but the reality is `bluesky.network` is the most popular and comes predefined if you run the main PDS implementation. With that said I think it's still early and not a huge concern right now. In truth we have a lot to thank from Bluesky with their work on ATProto and the promises it brings. If you're interested in any of the code mentioned in this post, it's all open source:
101	101
102	102		- [Personal Site](https://github.com/stevedylandev/stevedylan.dev)
103	103		- [Tap Fork](https://github.com/stevedylandev/indigo/tree/main/cmd/tap)
104	104
105		-	I also plan to include a link to this post as an update on my [/now](/now) page if you want to check out the implementation and leave a comment!
	105	+	I also plan to include a link to this post as an update on my [/now](/now) page if you want to check out the implementation and leave a comment! While my main blog doesn't have comments I did write a script that will now create documents on ATProto so they should be indexed as well.
106	106
107	107		Wrapping up, this experience has been a great culmination of everything I've been prioritizing with the web, that being content publishing and sharing that content through open channels like RSS. Standard.site opens up a whole new world of possibilities for that this could look like in the near future, and takes us a step closer to a truly open web that I long to see.