fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

9.8K
active users

#GoBlog

1 post1 participant0 posts today
Replied in thread

Für Blogs ist Mastodon denkbar ungeeinget.

Wer schon ein Wordpress hat, könnte das ActivityPub Plugin aktivieren, das ist wohl der einfachste Weg.

Sonst einfach mal auf #fediverse.party schauen und ein Häckchen bei "Blog and Publishing" machen.

#WriteFreely und #GoBlog schauen interessant aus und werden auch noch aktiv entwickeln. Ich selber verwende #Friendica als Software "für alles" - damit kann man auch sehr gut lange formatierte Artikel erstellen.

@roblen @nick @meikerenschbergner

fediverse.partyThemed servers - Fediverse.Party - explore federated networksLet's make social media free, federated and fun! Fediverse.Party is your guide into the world of decentralized, autonomous networks running on free open software on a myriad of servers across the world. No ads and no algorithms. Join Fediverse and become part of the new interconnected Web!

It’s not a winter wonderland out here, but with Christmas and winter coming soon, maybe a little snow on my blog isn’t a bad idea. I’ve just programmed a snow animation for another project and thought I could reuse the code in the form of a simple GoBlog plugin. ❄❄❄

It took me so long to find the cause of a memory leak in GoBlog. I thought it was smart to use a cache for prepared database statements. But I didn’t read the documentation and didn’t know that prepared statements need to be closed when they are no longer needed to free up the allocated resources. 🤦‍♂️ I finally fixed it by removing the prepared statement cache altogether. Less code, fewer problems in the future, and the cache wasn’t much of an improvement anyway. I also learned about the usefulness of memory profiling.

It seems like I finally fixed a memory leak in GoBlog yesterday, that sometimes made my blog crashing. How? I used Anthropic’s new Claude 3.5 Sonnet to write me a new HTTP compression middleware that compresses HTTP responses using zstd or gzip when possible. I needed to instruct a few changes and modify some code lines as the initial implementation was wrong, but thereafter, it finally seems to work better than my original implementation that probably leaked some objects anywhere. Claude also helped me to write unit tests (which I adapted a bit, though) and increase code coverage.

Today, I finally finished the reworked MicroPub endpoint in GoBlog using the indielib library by Henrique. It killed about 400 lines of my spaghetti code. 😅

And I also improved the system prompt of the AI summary plugin a bit. First, I tried to write the system prompt myself, but GPT-3.5-Turbo just didn’t want to do what I tasked it to do. So I asked Bing Chat (GPT-4) to help me with the task of writing a good system prompt. In my tests it looked more promising then. Let’s hope for better AI summaries on my blog posts in the future. 😄

Now that I have vacation, it seems like my motivation to work on GoBlog (and blog) is back a bit…

GitHubGitHub - hacdias/indielib: An IndieWeb toolkit in Go.An IndieWeb toolkit in Go. Contribute to hacdias/indielib development by creating an account on GitHub.

💭 While some people like to jump between blogging software all the time, or go back to Hugo from a custom one, I don’t really miss Hugo after switching to GoBlog in 2020, but enjoy having my own system quite a bit. Not that Hugo, WordPress, etc. are bad blogging systems, but I really enjoy being able to quickly code a fix without having to research docs, StackOverflow, or the source on GitHub. And when I have an idea for a new feature, it would often not be easy to implement in the existing systems.