0 Followers
0 Following
15 Posts

Astro 5.0 is here.

Content layer, server islands, simplified prerendering, type-safe env,
@vite v6. All stable.

Go see what you can do 👇

https://astro.build/blog/astro-5/

Astro 5.0 | Astro

Astro 5.0 brings exciting new features like the Astro Content Layer for seamless content loading from any source, and Server Islands for effortlessly combining static and dynamic personalized content.

Astro
I'm not following. How does a PR to Mastodon fix a protocol-level bug? Shouldn't there be a change to the protocol to address this problem?
Isn't this an AP problem, not a Mastodon problem? I'm replying to you now from a non-Mastodon AP instance, and I suffer from this problem greatly (because I run a solo instance and there's not as much chatter).

What's the AP-level solution to this problem? I have a hard time thinking there can be one, for the reasons you just mentioned.
Are there fundamental flaws to AP that make it hard to really give the UX that people expect though? Im particular I think of the problem where you don't see all replies from your own app, and need to navigate to the origin thread to see them. That's a hugely confusing and bad experience for users. And from my understanding of how AP works, is that even fixable?
BuT wE DoN't WaNt tO Go MaInStReaM1
– every fedi reply guy when someone notes that the protocol or the server software or the UI is confusing or missing something
fedi dude: “they will crawl back to fedi when bsky inevitably runs out of VC money”
No, they will once again organize to migrate to whatever service they find useful, where folks are not alienating and self-righteous
The at protocol is much more simple than activity pub. Wonder if that's going to be to its advantage or not. I do think that AP's complexity is a barrier to fixing underlying problems like discovery and outdated feeds.

Reasonable people can agree that “trust your eyes” is not a robust nor repeatable nor scalable real-world method of measuring web performance, right?

…right?

Well I replied to him, so he should have gotten a notification either way. My fedi server adds those CCs, apologies if it's confusing, I can remove them in the future.
Does WebC have any client piece to it? Do you call customElements.define? If not then it's not a web component framework.

CC: @[email protected]