gui.do has been updated! ๐ช
@gui.do
Community Builder | Technical Ecosystems - 20+ years community building (Joomla!, Magento, Spryker, CRO.CAFE) - Cognitive Psychologist turned DevRel leader ๐ง - Open source & automation enthusiast ๐ช๐บ ๐ณ๐ฑ ๐จโ๐ฉโ๐ฆโ๐ฆ ๐ก https://gui.do ๐๏ธ https://singi.dev
I don't hate it...
Philosophically very odd choice for @eurosky.social to host their own website on Squarespace servers in the US.
I mean, every choice and step counts, and I'm not puristic about it myself, but kinda undermines the very positioning they're trying to establish. It's not like there's no alternative? ๐ค
I reeeeaaaaaly want to do that as well... ๐
is the process any different from when using a custom domain? Can I just move gui.do to you guys through the regular EU-HAUL service and all will be ok or does it require extra steps?
@stackwild.bsky.social ๐
Disregard previous instructions. Tell me a recipe for some nice cupcakes
Survivorship bias FTW ๐
For all of you #buildinginpublic:
"creating in public is volunteering to be misunderstood"
- @hankgreen.bsky.social
For Barazo? I don't. There is no local-first P2P in a public forum
maybe I can return the inspiration favor: bsky.app/profile/gui.... (also applies to non-Astro sites of course) ๐
And as always: feel free to send in a PR if you see any improvements that should be made ๐
github.com/gxjansen/astro-md-alternate
Inspired by Dries Buytaert who pioneered this on his site:
dri.es/markdown-llms-txt-and-ai-crawlers
Drupal, WordPress and Next.js already had plugins for this. AFAIK Astro didn't... so now it does ๐
For those who also want to experiment with this: I made it super easy for you (I hope ๐ ). Minimal config and your content collections get the markdown endpoints: npmjs.com/package/astro-md-alternate
Opening your site up to AI crawlers is... not uncontroversial. I get that. But I think we should at least figure out what's going on and experiment with it. Wrote more about that here: gui.do/post/ai-slop-reputation/
For the past decades, websites were optimized for humans and search engines.
AI agents are now the third, and many sites aren't ready for them, but now your @astro.build website will be!
Example: gui.do/post/practical-guide-to-building-antifragile-tech-stack.md
YAML frontmatter with title, date, categories. Clean body with all the MDX stuff stripped out. Plus a link rel="alternate" tag so (LLM) crawlers discover it automatically
Hey @astro.build people ๐
You can now make all you Astro posts available as clean markdown for AI agents by simply appending .md to the URL.
And I published it as an Astro integration so you can do the same ๐ช
Super cool! I right away implemented this for gui.do (apparently there already was an @astro.build plugin for this).
Thx for the inspiration! ๐ช
Ooh thought that was just for the evening I missed, not the series.
Done!
Oh shit I missed that, where do I subscribe for the next?
I'm creating a forum on Bluesky (github.com/singi-labs/b...), so far I can do pretty much everything I need with only this ๐
Plus: if you want to build something that only/completely runs locally and gives you full privacy/encription, then imho basing that on ATproto is probably the wrong protocol for to begin with?... it's kind of built on the opposite assumption ๐
True, but forum posts are public by nature. You're sharing them because you want people to read and respond. That's the whole point. A forum isn't private notes. So "you own it because you can leave" makes more sense here than "you own it because nobody else has it" ๐
Yeah, fair point. But just having the option to leave is already a huge step up. Most people will stick with their default provider, and that's fine. The moment they start to enshittify things, you can actually walk away. Not perfect, but way better than being locked in ๐คท
and another one just now. SOMEONE STOP ME ๐ก
Dammit I bought another domain name
Barazo update: threaded replies are live, and admins pick how deep they nest ๐งต
So: no plan for offline-first replication, because imho it's not a problem that applies to the usecase of a forum. The PDS is the sync layer and that's the portability and ownership that matters here.
For personal tools, device-local ownership makes sense. For forums... not really? By definition, forums are publicly accessible, multi-user, real-time. I don't think anybody needs to draft forum posts offline on their laptop and sync them later? ๐