"Hmm. This website is kinda sketchy. I think I'll actually check the privacy policy" [the specific page of the privacy policy is error 500] "Ominous. And the terms of service?" [the specific page of the terms of service is error 500]

Astro 7 is here! A new Rust compiler, a new Rust Markdown/MDX processor, Vite 8 and more. Get ready for 60%+ faster builds. astro.build/blog/astro-7/

i need a firefox kit plushie,,,

compatible with Firefox OS (tm)

congrats @sharpmars.nekoweb.org for having the @standard.site document with the oldest publishedAt date on the network! you win a prize

friends let friends install fedora KDE (with rpmfusion and without fedora flatpaks)

@standard.site document publish dates, by weekday. this doesn't seem right... who would publish ~170k spam documents??

now my Astro integration publishes @standard.site records with content! (@markpub.at schema) will have to look more into @standard-reader.app's HTML sanitization...

don't think it don't say it don't think it don't say it don't think it don't say it don't think it don't say it don't think it don't say it don't think it don't say it don't think it don't say it don't think it don't say it don't think it don't say it don't think it don't say it

hello @archive.org!

@astro.build content collections map really well to @standard.site lexicons.. hmm

I'm working on writing documentation and getting a lot of insight from diataxis.fr shoutout to the default Starlight docs from @astro.build for surfacing this link

it's a start... I've done some research on ways of integrating standard.site documents with Astro, and none of the existing solutions seem ideal to me (so, time to make my own 🙃)

One benefit of @npmx.dev that I didn't realize - outdated dependency indicators are potential avenues for new contributors, instead of just warnings. Thanks @yusukebe.bsky.social! (pr)

does anyone know what day it is today

i should frame this

New blog post! gu5.org/blog/integra...

Working on a new @prometheus.io client for TypeScript (github.com/thegu5/neoprom) - it's interesting to experiment with creating new API surfaces based on upcoming JS features e.g. decorators:

reading: www.ryzokuken.dev/blog/about-e... really interesting stuff

relevant to any OSS work i think "The author must have permission to contribute the work, explain the contribution, and present it in a way that is reviewable, maintainable, and debuggable by others. (That means code changes that a human reviewer can digest, not multi-thousand-line changes.)"

I WILL WRITE A BLOG POST I WILL WRITE A BLOG POST I WILL WRITE A BLOG POST I WILL WRITE A BLOG POST I WILL WRITE A BLOG POST

starting to tinker with @e18e.dev's module-replacements! github.com/e18e/module-...