I did some personal writing: a decade of using split keyboards, what I've learned from that whole process, and where I am now in the keyboard rabbit hole. https://ashfurrow.com/blog/keyboard-rabbit-hole/
=> More informations about this toot | More toots from ashfurrow@tenforward.social
Hey folks, I'm aware that images aren't loading on this blog post. I'm not sure why, either a problem with Gatsby or Netlify or both.
I won't have time to look into this until tonight. In the meantime, the markdown blog post and images are all on GitHub: https://github.com/ashfurrow/blog/tree/main/blog/2024-11-17-keyboard-rabbit-hole
=> More informations about this toot | More toots from ashfurrow@tenforward.social
Or maybe this fixed it? Who knows ¯_(ツ)_/¯ https://github.com/ashfurrow/blog/commit/31f59a01159436d8c88eebb8cab1f21833401a19
=> More informations about this toot | More toots from ashfurrow@tenforward.social
No one has reported images not working since I made this change. The changelog of the updated package describes changes to cache-specific headers, so yay?
I still see some 404's in the console log, and clicking images doesn't work. Hrmm. Blog needs some work, maybe a nice holiday project...
=> More informations about this toot | More toots from ashfurrow@tenforward.social
@ashfurrow For me I’ve now written every single one of my Gatsby sites in Next.js.
Gatsby is just far too complicated for its own good. Going all in on GraphQL was a mistake.
=> More informations about this toot | More toots from Charrondev@mastodon.social This content has been proxied by September (3851b).Proxy Information
text/gemini