new blog post: how standard.horse works. wherein I accident…

well that’s going to rattle around the back of my mind for the next 5 years

Minor Mobius 31 May

wtf that was less than two weeks ago 😱

advaith 31 May

feels weird that the embed's colorful cta goes to the site homepage instead of the linked article. I tapped that first and was confused to land on the wrong page

EconReporter 30 May

So... Bluesky is never twitter alternative, it is Google Reader alternative all along🫵

1 5

at://tkdodo.eu/site.standard.publication/3mmyb25hudm2r

Yeah bluesky basically is google reader but only for posts that conform to a set of rules and identify themselves as bluesky posts.

1 2

Dominik 🔮31 May

I logged in and it tells me "You don’t have a standard.site publication yet." which is wrong because I do: pdsls.dev/at://did:plc... Anything I'm doing wrong?

pdsls.dev

I believe it’s failing record validation because the icon is 1.4mb (max is specified as 1mb) kinda awkward! I would like to build better tooling around this for sure

it also doesn’t really handle the case where the content is *not* specified in the record itself, like how your blog works. I need to think about how to handle that nicely 🤔

Dominik 🔮31 May

I wanted to maybe add content but getting it into straight markdown isn't easy

Markpub.at Markdown Lexicon

have you seen markpub.at? pretty straightforward lexicon for just storing content as a big ol’ markdown string. this is what my blog does :)

Providing a Lexicon for putting Markdown in the ATmosphere.

markpub.at

Killed by Google is the open source list of dead Google products, services, and devices. It serves as a tribute and memorial of beloved services and products killed by Google.

Dominik 🔮31 May

Will take a look, but I need to get from mdx to md first

Emelia 31 May

"This is Google Reader and you can find more information about it at killedbygoogle.com " 🤣🤣

Killed by Google

killedbygoogle.com

Live multi-format rich text translation demo

To be annoying and nitpick-ey, RSS can be used in a push mode and this has been possible for over a decade. The protocol for push-based RSS feed updates is called WebSub (you may also hear the term PubSubHubbub or PuSH, that's the same thing), and most large blogging sites/feed readers implement it.

Blaine 31 May

Nice work! I haven't updated it since before standard.site really existed, but relationaltext.org (esp demo.relationaltext.org) and @aaronstevenwhite.io's panproto.dev might be of interest. 😊

RelationalText Demo

demo.relationaltext.org

Sven laa 30 May

"unknown to anyone under the age of 25" ❌ wrong. incorrect.

Samuel 30 May

spiritually 38 years old if so

1 2

Sven laa 4 Jun

i am honoured

Tassis 2 Jun

How do you usually handle provider-specific blocks like Leaflet’s Poll, Page, or Canvas? I’m finding it hard to map them cleanly into Markdown without losing information.

Samuel 2 Jun

it’s just lossy

What happens if I want to run an atproto blog where the blog itself is outside of BlueSky services? Then I'd need to setup and maintain the infrastructure instead of where a blog is just a webserver, html, and some way to route it, right?

I guess for me, I'm still having trouble understanding the value of atproto because, if I really want to become decentralized and not rely on bluesky services, I need spend hundreds of dollars and do a lot of maintenance in order to host the entire system.

So it's probably cool that logs can exist on at proto now, but it doesn't really acknowledge the fact of all the other parts of the chain and how it still is not decentralized because we all rely on bluesky services to some degree. The only group I know not doing that is blacksky.

I still think decentralization is a myth because all that's happening here by putting blogs on at proto is that you're forcing blogs to exist in the at proto landscape and the at proto landscape is dominated by Bluesky's infrastructure. So where does the decentralization happen?

And in this case now what I guess is happening is that if I wanted to run my own blog and have all of my data saved for myself, I would need to set up my own PDS anyway which is its own whole thing, especially because I need to have infrastructure that can support enough users.

This pales in comparison to being able to just put an HTML file behind a web server which is behind a cloudflare which just caches all of my stuff. Why not just have something that is at proto readable instead of having to rely on the at proto system itself? Isn't that what RSS is?

Maybe I'm missing something here but every time that I read anything about additional things on at proto I just can't wrap my head around it because I don't understand the value that's being provided.

I just find it really confusing why Bluesky Social continues to work on stuff like this when I can't really see a legitimate value, compared to so many other changes they could be making. The direction that atproto and bluesky is going is just really confusing to me.

Running your own pds is extremely cheap (it's like running a webserver), and standard.site doesn't really depend on any bluesky infrastructure. (well, except plc, which we're stuck with. That's why that's being turned into its own foundation so bsky doesn't have unilateral control over it)

I think you're confusing the costs of hosting a bluesky-like application with the costs of using atproto for anything period.