Monkinetic Weblog

XVI Edition, September 2025

More Navigation

Entries for #goldfrog

← first ← previous page 2 of 3 next → last →


Manual Indie Comments

Chris Aldrich wrote a blog post about manually adding Webmentions for links to his posts from sites that are not themselves Webmention-enabled.

This reminded me that I'd like to add a "I linked to you" feature for the post detail page in #goldfrog for this site. (Goldfrog does support Webmentions, so Chris should get an automatic link from this post :))


Did my first live webmention test on monkinetic #webmention #indieweb #goldfrog


Finished #webmention discovery in #goldfrog, all 23 discovery tests on https://webmention.rocks pass. :)


For my next #indieweb trick: I'm working on adding support for Webmention in #goldfrog.

https://github.com/sivy/goldfrog/issues/9

Client:

  • Endpoint discovery (header, link, a)
  • Send basic webmentions
  • Send "special" webmentions (ie Likes)

Server:

  • Provide discovery (header, link, a)
  • Receive basic webmentions
  • Receive "special" webmentions (ie Likes)

Ultimately I'd like to break out my webmention code into a releasable #golang module that can provide reusable http.Handler functions that can be plugged into any Go mux that supports them.


I've added POSSE-style notes to #goldfrog.

https://indieweb.org/POSSE


None

Golang Templates Cheatsheet

This resource really helped as I’ve been building #goldfrog.

Golang Templates Cheatsheet

#python

https://t.co/tcXZqriOlQ


Goldfrog: cross-posting to Mastodon works

Ooooooh, yeah #goldfrog #mastodon

https://t.co/ruJEPNr7oC


Twitter cross-posting for #goldfrog is technically working, but the templates are not yet rendering the twitter metadata properly, so links are not showing up as nicely as I wish they would.

Next up will be mastodon posting.


Ooooooh, yeah #goldfrog #mastodon

(SORRY, LOST IMAGE)

Thanks to go-mastodon this was super easy.


This resource really helped as I've been building #goldfrog.

Golang Templates Cheatsheet

Go's template system is rich and powerful, and not much at all like systems in #Python, which is why it's been breaking my brain.


@bitprophet That was one of the motivations for #goldfrog - needed a positive direction for my brain to go


Another aspect to creating my own blogging software: I can finally start implementing some of #indieweb principles I've been watching for a while.

One of those is POSSE (Publish Own Site, Syndicate Everywhere) - which means everything you write starts on your own site, and content is syndicated to the appropriate kinds of sites as desired. This could include things like:

  • Articles are syndicated via RSS (done, no brainer)
  • Short posts (notes) are automatically or optionally published whole to Twitter, Mastodon, or the microblog of your choice
  • Articles are automatically or optionally shared to a microblog site with a link back to your own site

Goldfrog + Twitter

While I generally find Twitter overwhelming and frustrating (not nearly as much so as the less-privileged do), I just finished adding a Twitter cross-poster to #goldfrog. I'll be implementing a Mastodon cross-poster in the next few days (/me waves @ toot.cafe), now that I've figured out and implemented the pattern.

The Twitter cross poster will send the title, some text, and a link back to the post. So, let's see if deploying the new feature worked. :D


A late feature I added to #goldfrog that I was really happy about: hashtags! I love them on social media, and since I included a tags fields in the blog schema... so I added some code that parses hashtags when posts are saved, and adds them to the post tags. I also added a tag search to the site, and I have a filter that auto-links hashtags to the tag search.

So be prepared to see lots of #hashtags in my posts now :)


What is the difference between this:

/static/images/Screen Shot 2020-01-08 at 1.17.44 PM.png

Posted by Dave Winer with a theverge.com link, and this:

/static/images/Screen Shot 2020-01-08 at 1.17.59 PM.png

Posted by #goldfrog via the Twitter API with a link to this site?


Write The Web, 2020

For 2020, I'm writing a new blog app. It's just for myself, a toy to remind me why I love the web. It's called Goldfrog, and it sounds a bit like "Go, blog!"

Why in the hack, in this day and age, would I spend time writing my own #blogging software, when you can't sign up for a VPS anywhere without tripping over offers to help you set up Wordpress, or Ghost, or what have you?

A few reasons.

New Year, New You

2019 was shite-filled, and due to politics, the tech trashfire, and the friction of blogging through several variations of static, git-powered versions of this site, I simply stopped blogging. I've wanted to, but the effort killed the motivation before I could get some words out.

So I finally decided to write something myself, that did just the things I wanted #goldfrog is written in Go, because while I will love Python to my dying day, my brain needed a kick in the pants this year, which relates to my next point.

The Builder's High

Rands writes eloquently on the builder's high. With family engagements and work over the last few years my hobby coding has dropped to almost nil (None if I were writing Python).

I needed something to reboot my creative juices, and trying to write something I really wanted, that thought would be quick, in a new language, seemed like a good way to go (I did want it, it wasn't easy, and Go hates me. But I'm learning and that feels great!)

Goldfrog

/static/images/Screen Shot 2020-01-07 at 4.51.44 PM.png

A bit more about Goldfrog: the single feature I wanted was a posting form on the home page, right up front. Various Userland products had had this, and it always felt right.

Second to this was an "Edit" link next to every post, wherever it was found on the site.

Finally, my main technical "innovation": My content is still stored on the filesystem as Jekyll-compatible Markdown files. However, build times via Jekyll or Hugo are fairly slow for my 2800+ posts (since 2000, baby) and I hate that. So #goldfrog indexes all posts in a sqlite database on disk. Post creation and edits go to the DB and to the filesystem, so I can still periodically sync the changes to the git repo I have checked out there. But all the list views, archives, tag pages, and search functionality go to the DB, and are really fast.

The Setup

This is really the app I've wanted for a long time.

  • It's hosted on a Linode "nano"
  • The app builds on CircleCI and the binary is pushed to an S3 bucket.
  • I've got ansible playbooks that setup the VPS pretty much from scratch with Nginx fronting Goldfrog.

Next

I really need to get my logging story fixed, and I've got some idea on adding basic metric tracking to the app.


#goldfrog is coming along - archive pages done and image uploading works. I think the image upload feature is a nice addition and doesn’t add a lot of complexity


Got #circleci working better than Travis, also added a new feature to #goldfrog today that worked first time, so of course my server setup is like a flaming turd


@travisci #goldfrog #blogging taking a code break to fiddle with ansible and make pretty pictures https://t.co/XEvs7j6Lv9


Progress today: post editing and deleting, many template updates.

I managed NOT to throw the laptop across the room when figuring out golang html/template :win:

Working on a @TravisCI build pipeline, here’s to again not throwing my laptop

#goldfrog #blogging #writetheweb


This is one reason I’m building #goldfrog https://t.co/onvOioQmEA

← first ← previous page 2 of 3 next → last →