SaturdayMP Show 103: HTTP Server in C (Part 1 - Listen is Working)

In this episode we start writing a custom HTTP Server in C because Omar wanted to learn more about HTTP, servers, and low-level networking. We get a simple app that listens on a port and writes out to the command line what was sent to it. We also have a good discussion about C strings at 1:08:53.

Part 2, if it happens, we will add an HTTP response. We are not very consistent.

[Read More]

SaturdayMP Show #90: Claude Code Plugin Marketplace

Join me as I finish creating a Claude Plugin Marketplace and my first plugin that validates and fixes GitHub PR review feedback.

P.S. - The “Marketplace” logo was created using Claude. I usually use ChatGPT or Gemini as they create better images, in my opinion, but felt it appropriate to use Claude for this one.

SaturdayMP Claude Marketplace:
https://github.com/saturdaymp/claude-plugins

[Read More]

SaturdayMP Show 86: Creating PostCast (Part 8 – Investigate Keyring Libraries)

In this episode Omar Ashour and myself (Chris C.) investigate several Golang keyring libraries and try to get the keyring to work on my Windows Subsystem for Linux (WSL). Spoiler: it was working all along, I was just too dumb to notice. Learned about Seahorse, a handy tool for viewing keychain entries.

We also discuses what the Windows Registry. Spoiler: it is just a big dumping ground of key-value pairs.

[Read More]

SaturdayMP Show 84: Creating PostCast (Part 6 – Create Fyne Main Screen)

In episode 84 of the SaturdayMP show, Omar Ashour and myself (Chris C.) create a very basic main screen using Fyne to input the text to post and a button to create the LinkedIn post. That said, the GUI doesn’t do anything yet, except look nice-ish. Lots of reading the Fyne documentation and experimenting with Fyne.

*PostCast is just a place holder name and might change. The goofy PostCast placeholder image was generated by ChatGPT and will likely change.

[Read More]

SaturdayMP Show 83: Creating PostCast (Part 5 – Go PoC for LinkedIn API)

We get a Proof of Concept (PoC) in Go that completes the LinkedIn authorization. We end up figuring out the difference between a LinkedIn code and token. Get a code by entering your LinkedIn username and password, then use that code to get a token. We also spin up a local webserver to deal with the callback which is required to enter credentials and get the code.

*PostCast is just a place holder name and might change. The goofy PostCast placeholder image was generated by ChatGPT and will likely change.

[Read More]