From bb8f62a5a8a5c78db3ee3c396ce729cb7ddaf86d Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 4 Mar 2025 21:23:05 +0200 Subject: Update content for html --- about/resources.html | 189 ++++---- about/technical-books.txt | 1 + ...025-03-05-sharing-on-social-media-with-gos.html | 394 ++++++++++++++++ gemfeed/atom.xml | 523 +++++++++++++++------ gemfeed/index.html | 1 + .../gos-screenshot.png | Bin 0 -> 137561 bytes gemfeed/sharing-on-social-media-with-gos/gos.png | Bin 0 -> 3861 bytes index.html | 3 +- uptime-stats.html | 2 +- 9 files changed, 882 insertions(+), 231 deletions(-) create mode 100644 gemfeed/2025-03-05-sharing-on-social-media-with-gos.html create mode 100644 gemfeed/sharing-on-social-media-with-gos/gos-screenshot.png create mode 100644 gemfeed/sharing-on-social-media-with-gos/gos.png diff --git a/about/resources.html b/about/resources.html index 2672db3f..06fac94e 100644 --- a/about/resources.html +++ b/about/resources.html @@ -50,103 +50,104 @@ In random order:


Technical references



I didn't read them from the beginning to the end, but I am using them to look up things. The books are in random order:


Self-development and soft-skills books



In random order:


Here are notes of mine for some of the books

@@ -155,31 +156,31 @@ Some of these were in-person with exams; others were online learning lectures only. In random order:


Technical guides



These are not whole books, but guides (smaller or larger) which I found very useful. in random order:


Podcasts



@@ -188,48 +189,48 @@ In random order:


Podcasts I liked



I liked them but am not listening to them anymore. The podcasts have either "finished" (no more episodes) or I stopped listening to them due to time constraints or a shift in my interests.


Newsletters I like



This is a mix of tech and non-tech newsletters I am subscribed to. In random order:


Formal education



diff --git a/about/technical-books.txt b/about/technical-books.txt index fa7c6a8a..da745eea 100644 --- a/about/technical-books.txt +++ b/about/technical-books.txt @@ -25,6 +25,7 @@ * Object-Oriented Programming with ANSI-C; Axel-Tobias Schreiner * Perl New Features; Joshua McAdams, brian d foy; Perl School * Polished Ruby Programming; Jeremy Evans; Packt Publishing +* Programming Ruby 3.3 (5th Edition); Noel Rappin, with Dave Thomas; The Pragmatic Bookshelf * Programming Perl aka "The Camel Book"; Tom Christiansen, brian d foy, Larry Wall & Jon Orwant; O'Reilly * Pro Puppet; James Turnbull, Jeffrey McCune; Apress * Raku Fundamentals; Moritz Lenz; Apress diff --git a/gemfeed/2025-03-05-sharing-on-social-media-with-gos.html b/gemfeed/2025-03-05-sharing-on-social-media-with-gos.html new file mode 100644 index 00000000..0d6b82f3 --- /dev/null +++ b/gemfeed/2025-03-05-sharing-on-social-media-with-gos.html @@ -0,0 +1,394 @@ + + + + +Sharing on Social Media with Gos v1.0.0 + + + + + +

+Home | Markdown | Gemini +

+

Sharing on Social Media with Gos v1.0.0


+
+Published at 2025-03-04T21:22:07+02:00
+
+As you may have noticed, I like to share on Mastodon and LinkedIn all the technical things I find interesting, and this blog post is technically all about that.
+
+Gos logo
+
+

Table of Contents


+
+
+

Introduction


+
+Gos is a Go-based replacement (which I wrote) for Buffer.com, providing the ability to schedule and manage social media posts from the command line. It can be run, for example, every time you open a new shell or only once every N hours when you open a new shell.
+
+I used Buffer.com to schedule and post my social media messages for a long time. However, over time, there were more problems with that service, including a slow and unintuitive UI, and the free version only allows scheduling up to 10 messages. At one point, they started to integrate an AI assistant (which would seemingly randomly pop up in separate JavaScript-powered input boxes), and then I had enough and decided I had to build my own social sharing tool—and Gos was born.
+
+https://buffer.com
+https://codeberg.org/snonux/gos
+
+

Gos features


+
+
+

Installation


+
+

Prequisites


+
+The prerequisites are:
+
+
+

Build and install


+
+Clone the repository:
+
+ +
git clone https://codeberg.org/snonux/gos.git
+cd gos
+
+
+Build the binaries:
+
+ +
go build -o gos ./cmd/gos
+go build -o gosc ./cmd/gosc
+sudo mv gos ~/go/bin
+sudo mv gosc ~/go/bin
+
+
+Or, if you want to use the Taskfile:
+
+ +
go-task install
+
+
+

Configuration


+
+Gos requires a configuration file to store API secrets and OAuth2 credentials for each supported social media platform. The configuration is managed using a Secrets structure, which is stored as a JSON file in ~/.config/gos/gos.json.
+
+Example Configuration File (~/.config/gos/gos.json):
+
+ +
{
+  "MastodonURL": "https://mastodon.example.com",
+  "MastodonAccessToken": "your-mastodon-access-token",
+  "LinkedInClientID": "your-linkedin-client-id",
+  "LinkedInSecret": "your-linkedin-client-secret",
+  "LinkedInRedirectURL": "http://localhost:8080/callback",
+}
+
+
+

Configuration fields


+
+
+

Automatically managed fields


+
+Once you finish the OAuth2 setup (after the initial run of gos), some fields—like LinkedInAccessToken and LinkedInPersonID will get filled in automatically. To check if everything's working without actually posting anything, you can run the app in dry run mode with the --dry option. After OAuth2 is successful, the file will be updated with LinkedInClientID and LinkedInAccessToken. If the access token expires, it will go through the OAuth2 process again.
+
+

Invoking Gos


+
+Gos is a command-line tool for posting updates to multiple social media platforms. You can run it with various flags to customize its behaviour, such as posting in dry run mode, limiting posts by size, or targeting specific platforms.
+
+Flags control the tool's behavior. Below are several common ways to invoke Gos and descriptions of the available flags.
+
+

Common flags


+
+
+

Examples


+
+*Dry run mode*
+
+Dry run mode lets you simulate the entire posting process without actually sending the posts. This is useful for testing configurations or seeing what would happen before making real posts.
+
+ +
./gos --dry
+
+
+*Normal run*
+
+Sharing to all platforms is as simple as the following (assuming it is configured correctly):
+
+ +
./gos 
+
+
+:-)
+
+Gos Screenshot
+
+However, you will notice that no messages are queued to be posted yet (not like on the screenshot yet!). Relax and read on...
+
+

Composing messages to be posted


+
+To post messages using Gos, you need to create text files containing the posts' content. These files are placed inside the directory specified by the --gosDir flag (the default directory is ~/.gosdir). Each text file represents a single post and must have the .txt extension. You can also simply run gos --compose to compose a new entry. It will open simply a new text file in gosDir.
+
+

Basic structure of a message file


+
+Each text file should contain the message you want to post on the specified platforms. That's it. Example of a Basic Post File ~/.gosdir/samplepost.txt:
+
+
+This is a sample message to be posted on social media platforms.
+
+Maybe add a link here: https://foo.zone
+
+#foo #cool #gos #golang
+
+
+The message is just arbitrary text, and, besides inline share tags (see later in this document) at the beginning, Gos does not parse any of the content other than ensuring the overall allowed size for the social media platform isn't exceeded. If it exceeds the limit, Gos will prompt you to edit the post using your standard text editor (as specified by the EDITOR environment variable). When posting, all the hyperlinks, hashtags, etc., are interpreted by the social platforms themselves (e.g., Mastodon, LinkedIn).
+
+

Adding share tags in the filename


+
+You can control which platforms a post is shared to, and manage other behaviors using tags embedded in the filename. Add tags in the format share:platform1.-platform2 to target specific platforms within the filename. This instructs Gos to share the message only to platform1 (e.g., Mastodon) and explicitly exclude platform2 (e.g., LinkedIn). You can include multiple platforms by listing them after share:, separated by a .. Use the - symbol to exclude a platform.
+
+Currently, only linkedin and mastodon are supported, and the shortcuts li and ma also work.
+
+**Examples:**
+
+
+Besides encoding share tags in the filename, they can also be embedded within the .txt file content to be queued. For example, a file named ~/.gosdir/foopost.txt with the following content:
+
+
+share:mastodon The content of the post here
+
+
+or
+
+
+share:mastodon
+
+The content of the post is here https://some.foo/link
+
+#some #hashtags
+
+
+Gos will parse this content, extract the tags, and queue it as ~/.gosdir/db/platforms/mastodon/foopost.share:mastodon.extracted.txt.... (see how post queueing works later in this document).
+
+

Using the prio tag


+
+Gos randomly picks any queued message without any specific order or priority. However, you can assign a higher priority to a message. The priority determines the order in which posts are processed, with messages without a priority tag being posted last and those with priority tags being posted first. If multiple messages have the priority tag, then a random message will be selected from them.
+
+*Examples using the Priority tag:*
+
+
+There is more: you can also use the soon tag. It is almost the same as the prio tag, just with one lower priority.
+
+

More tags


+
+
+So you could also have filenames like those:
+
+
+etc...
+
+All of the above also works with embedded tags. E.g.:
+
+
+share:mastodon,ask,prio Hello wold :-)
+
+
+or
+
+
+share:mastodon,ask,prio
+
+Hello World :-)
+
+
+

The gosc binary


+
+gosc stands for Gos Composer and will simply launch your $EDITOR on a new text file in the gosDir. It's the same as running gos --compose, really. It is a quick way of composing new posts. Once composed, it will ask for your confirmation on whether the message should be queued or not.
+
+

How queueing works in gos


+
+When you place a message file in the gosDir, Gos processes it by moving the message through a queueing system before posting it to the target social media platforms. A message's lifecycle includes several key stages, from creation to posting, all managed through the ./db/platforms/PLATFORM directories.
+
+

Step-by-step queueing process


+
+1. Inserting a Message into gosDir: You start by creating a text file that represents your post (e.g., foo.txt) and placing it in the gosDir. When Gos runs, this file is processed. The easiest way is to use gosc here.
+
+2. Moving to the Queue: Upon running Gos, the tool identifies the message in the gosDir and places it into the queue for the specified platform. The message is moved into the appropriate directory for each platform in ./db/platforms/PLATFORM. During this stage, the message file is renamed to include a timestamp indicating when it was queued and given a .queued extension.
+
+*Example: If a message is queued for LinkedIn, the filename might look like this:*
+
+
+~/.gosdir/db/platforms/linkedin/foo.share:-mastodon.txt.20241022-102343.queued
+
+
+3. Posting the Message: Once a message is placed in the queue, Gos posts it to the specified social media platforms.
+
+4. Renaming to .posted: After a message is successfully posted to a platform, the corresponding .queued file is renamed to have a .posted extension, and the filename timestamp is also updated. This signals that the post has been processed and published.
+
+*Example - After a successful post to LinkedIn, the message file might look like this:*
+
+
+./db/platforms/linkedin/foo.share:-mastodon.txt.20241112-121323.posted
+
+
+

How message selection works in gos


+
+Gos decides which messages to post using a combination of priority, platform-specific tags, and timing rules. The message selection process ensures that messages are posted according to your configured cadence and targets while respecting pauses between posts and previously met goals.
+
+The key factors in message selection are:
+
+
+

Post summary as gemini gemtext


+
+For my blog, I want to post a summary of all the social messages posted over the last couple of months. For an example, have a look here:
+
+https://foo.zone/gemfeed/2025-01-01-posts-from-october-to-december-2024.html
+
+To accomplish this, run:
+
+ +
gos --geminiSummaryFor 202410,202411,202412
+
+
+This outputs the summary for the three specified months, as shown in the example. The summary includes posts from all social media networks but removes duplicates.
+
+Also, add the --gemtexterEnable flag, if you are using Gemtexter:
+
+
+ +
gos --gemtexterEnable --geminiSummaryFor 202410,202411,202412
+
+
+Gemtexter
+
+In case there are HTTP links that translate directly to the Geminispace for certain capsules, specify the Gemini capsules as a comma-separated list as follows:
+
+ +
gos --gemtexterEnable --geminiSummaryFor 202410,202411,202412 --geminiCapsules "foo.zone,paul.buetow.org"
+
+
+It will then also generate Gemini Gemtext links in the summary page and flag them with (Gemini).
+
+

Conclusion


+
+Overall, this was a fun little Go project with practical use for me personally. I hope you also had fun reading this, and maybe you will use it as well.
+
+E-Mail your comments to paul@nospam.buetow.org :-)
+
+Back to the main site
+

+Generated with Gemtexter 3.0.1-develop | +served by OpenBSD/relayd(8)+httpd(8) | +Site Mirrors +

+ + diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 217390a1..af4d196f 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,11 +1,398 @@ - 2025-02-22T21:06:27+02:00 + 2025-03-04T21:22:08+02:00 foo.zone feed To be in the .zone! https://foo.zone/ + + Sharing on Social Media with Gos v1.0.0 + + https://foo.zone/gemfeed/2025-03-05-sharing-on-social-media-with-gos.html + 2025-03-04T21:22:07+02:00 + + Paul Buetow aka snonux + paul@dev.buetow.org + + As you may have noticed, I like to share on Mastodon and LinkedIn all the technical things I find interesting, and this blog post is technically all about that. + +
+

Sharing on Social Media with Gos v1.0.0


+
+As you may have noticed, I like to share on Mastodon and LinkedIn all the technical things I find interesting, and this blog post is technically all about that.
+
+Gos logo
+
+

Table of Contents


+
+
+

Introduction


+
+Gos is a Go-based replacement (which I wrote) for Buffer.com, providing the ability to schedule and manage social media posts from the command line. It can be run, for example, every time you open a new shell or only once every N hours when you open a new shell.
+
+I used Buffer.com to schedule and post my social media messages for a long time. However, over time, there were more problems with that service, including a slow and unintuitive UI, and the free version only allows scheduling up to 10 messages. At one point, they started to integrate an AI assistant (which would seemingly randomly pop up in separate JavaScript-powered input boxes), and then I had enough and decided I had to build my own social sharing tool—and Gos was born.
+
+https://buffer.com
+https://codeberg.org/snonux/gos
+
+

Gos features


+
+
    +
  • Mastodon and LinkedIn support.
    • +
  • Dry run mode for testing posts without actually publishing.
    • +
  • Configurable via flags and environment variables.
    • +
  • Easy to integrate into automated workflows.
    • +
  • OAuth2 authentication for LinkedIn.
    • +
  • Image previews for LinkedIn posts.
    • +

+

Installation


+
+

Prequisites


+
+The prerequisites are:
+
+
    +
  • Go (version 1.24 or later)
    • +
  • Supported browsers like Firefox, Chrome, etc for oauth2.
    • +

+

Build and install


+
+Clone the repository:
+
+ +
git clone https://codeberg.org/snonux/gos.git
+cd gos
+
+
+Build the binaries:
+
+ +
go build -o gos ./cmd/gos
+go build -o gosc ./cmd/gosc
+sudo mv gos ~/go/bin
+sudo mv gosc ~/go/bin
+
+
+Or, if you want to use the Taskfile:
+
+ +
go-task install
+
+
+

Configuration


+
+Gos requires a configuration file to store API secrets and OAuth2 credentials for each supported social media platform. The configuration is managed using a Secrets structure, which is stored as a JSON file in ~/.config/gos/gos.json.
+
+Example Configuration File (~/.config/gos/gos.json):
+
+ +
{
+  "MastodonURL": "https://mastodon.example.com",
+  "MastodonAccessToken": "your-mastodon-access-token",
+  "LinkedInClientID": "your-linkedin-client-id",
+  "LinkedInSecret": "your-linkedin-client-secret",
+  "LinkedInRedirectURL": "http://localhost:8080/callback",
+}
+
+
+

Configuration fields


+
+
    +
  • MastodonURL: The base URL of the Mastodon instance you are using (e.g., https://mastodon.social).
    • +
  • MastodonAccessToken: Your access token for the Mastodon API, which is used to authenticate your posts.
    • +
  • LinkedInClientID: The client ID for your LinkedIn app, which is needed for OAuth2 authentication.
    • +
  • LinkedInSecret: The client secret for your LinkedIn app.
    • +
  • LinkedInRedirectURL: The redirect URL configured for handling OAuth2 responses.
    • +
  • LinkedInAccessToken: Gos will automatically update this after successful OAuth2 authentication with LinkedIn.
    • +
  • LinkedInPersonID: Gos will automatically update this after successful OAuth2 authentication with LinkedIn.
    • +

+

Automatically managed fields


+
+Once you finish the OAuth2 setup (after the initial run of gos), some fields—like LinkedInAccessToken and LinkedInPersonID will get filled in automatically. To check if everything's working without actually posting anything, you can run the app in dry run mode with the --dry option. After OAuth2 is successful, the file will be updated with LinkedInClientID and LinkedInAccessToken. If the access token expires, it will go through the OAuth2 process again.
+
+

Invoking Gos


+
+Gos is a command-line tool for posting updates to multiple social media platforms. You can run it with various flags to customize its behaviour, such as posting in dry run mode, limiting posts by size, or targeting specific platforms.
+
+Flags control the tool's behavior. Below are several common ways to invoke Gos and descriptions of the available flags.
+
+

Common flags


+
+
    +
  • -dry: Run the application in dry run mode, simulating operations without making any changes.
    • +
  • -version: Display the current version of the application.
    • +
  • -compose: Compose a new entry. Default is set by composeEntryDefault.
    • +
  • -gosDir: Specify the directory for Gos' queue and database files. The default is ~/.gosdir.
    • +
  • —cacheDir: Specify the directory for Gos' cache. The default is based on the gosDir path.
    • +
  • -browser: Choose the browser for OAuth2 processes. The default is "firefox".
    • +
  • -configPath: Path to the configuration file. Default is ~/.config/gos/gos.json.
    • +
  • —platforms: The enabled platforms and their post size limits. The default is "Mastodon:500,LinkedIn:1000."
    • +
  • -target: Target number of posts per week. The default is 2.
    • +
  • -minQueued: Minimum number of queued items before a warning message is printed. The default is 4.
    • +
  • -maxDaysQueued: Maximum number of days' worth of queued posts before the target increases and pauseDays decreases. The default is 365.
    • +
  • -pauseDays: Number of days until the next post can be submitted. The default is 3.
    • +
  • -runInterval: Number of hours until the next post run. The default is 12.
    • +
  • —lookback: The number of days to look back in time to review posting history. The default is 30.
    • +
  • -geminiSummaryFor: Generate a Gemini Gemtext format summary specifying months as a comma-separated string.
    • +
  • -geminiCapsules: Comma-separated list of Gemini capsules. Used to detect Gemtext links.
    • +
  • -gemtexterEnable: Add special tags for Gemtexter, the static site generator, to the Gemini Gemtext summary.
    • +
  • -dev: For internal development purposes only.
    • +

+

Examples


+
+*Dry run mode*
+
+Dry run mode lets you simulate the entire posting process without actually sending the posts. This is useful for testing configurations or seeing what would happen before making real posts.
+
+ +
./gos --dry
+
+
+*Normal run*
+
+Sharing to all platforms is as simple as the following (assuming it is configured correctly):
+
+ +
./gos 
+
+
+:-)
+
+Gos Screenshot
+
+However, you will notice that no messages are queued to be posted yet (not like on the screenshot yet!). Relax and read on...
+
+

Composing messages to be posted


+
+To post messages using Gos, you need to create text files containing the posts' content. These files are placed inside the directory specified by the --gosDir flag (the default directory is ~/.gosdir). Each text file represents a single post and must have the .txt extension. You can also simply run gos --compose to compose a new entry. It will open simply a new text file in gosDir.
+
+

Basic structure of a message file


+
+Each text file should contain the message you want to post on the specified platforms. That's it. Example of a Basic Post File ~/.gosdir/samplepost.txt:
+
+
+This is a sample message to be posted on social media platforms.
+
+Maybe add a link here: https://foo.zone
+
+#foo #cool #gos #golang
+
+
+The message is just arbitrary text, and, besides inline share tags (see later in this document) at the beginning, Gos does not parse any of the content other than ensuring the overall allowed size for the social media platform isn't exceeded. If it exceeds the limit, Gos will prompt you to edit the post using your standard text editor (as specified by the EDITOR environment variable). When posting, all the hyperlinks, hashtags, etc., are interpreted by the social platforms themselves (e.g., Mastodon, LinkedIn).
+
+

Adding share tags in the filename


+
+You can control which platforms a post is shared to, and manage other behaviors using tags embedded in the filename. Add tags in the format share:platform1.-platform2 to target specific platforms within the filename. This instructs Gos to share the message only to platform1 (e.g., Mastodon) and explicitly exclude platform2 (e.g., LinkedIn). You can include multiple platforms by listing them after share:, separated by a .. Use the - symbol to exclude a platform.
+
+Currently, only linkedin and mastodon are supported, and the shortcuts li and ma also work.
+
+**Examples:**
+
+
    +
  • To share only on Mastodon: ~/.gosdir/foopost.share:mastodon.txt
    • +
  • To exclude sharing on LinkedIn: ~/.gosdir/foopost.share:-linkedin.txt
    • +
  • To explicitly share on both LinkedIn and Mastodon: ~/.gosdir/foopost.share:linkedin:mastodon.txt
    • +
  • To explicitly share only on LinkedIn and exclude Mastodon: ~/.gosdir/foopost.share:linkedin:-mastodon.txt
    • +

+Besides encoding share tags in the filename, they can also be embedded within the .txt file content to be queued. For example, a file named ~/.gosdir/foopost.txt with the following content:
+
+
+share:mastodon The content of the post here
+
+
+or
+
+
+share:mastodon
+
+The content of the post is here https://some.foo/link
+
+#some #hashtags
+
+
+Gos will parse this content, extract the tags, and queue it as ~/.gosdir/db/platforms/mastodon/foopost.share:mastodon.extracted.txt.... (see how post queueing works later in this document).
+
+

Using the prio tag


+
+Gos randomly picks any queued message without any specific order or priority. However, you can assign a higher priority to a message. The priority determines the order in which posts are processed, with messages without a priority tag being posted last and those with priority tags being posted first. If multiple messages have the priority tag, then a random message will be selected from them.
+
+*Examples using the Priority tag:*
+
+
    +
  • To share only on Mastodon: ~/.gosdir/foopost.prio.share:mastodon.txt
    • +
  • To not share on LinkedIn: ~/.gosdir/foopost.prio.share:-linkedin.txt
    • +
  • To explicitly share on both: ~/.gosdir/foopost.prio.share:linkedin:mastodon.txt
    • +
  • To explicitly share on only linkedin: ~/.gosdir/foopost.prio.share:linkedin:-mastodon.txt
    • +

+There is more: you can also use the soon tag. It is almost the same as the prio tag, just with one lower priority.
+
+

More tags


+
+
    +
  • A .ask. in the filename will prompt you to choose whether to queue, edit, or delete a file before queuing it.
    • +
  • A .now. in the filename will schedule a post immediately, regardless of the target status.
    • +

+So you could also have filenames like those:
+
+
    +
  • ~/.gosdir/foopost.ask.txt
    • +
  • ~/.gosdir/foopost.now.txt
    • +
  • ~/.gosdir/foopost.ask.share:mastodon.txt
    • +
  • ~/.gosdir/foopost.ask.prio.share:mastodon.txt
    • +
  • ~/.gosdir/foopost.ask.now.share:-mastodon.txt
    • +
  • ~/.gosdir/foopost.now.share:-linkedin.txt
    • +

+etc...
+
+All of the above also works with embedded tags. E.g.:
+
+
+share:mastodon,ask,prio Hello wold :-)
+
+
+or
+
+
+share:mastodon,ask,prio
+
+Hello World :-)
+
+
+

The gosc binary


+
+gosc stands for Gos Composer and will simply launch your $EDITOR on a new text file in the gosDir. It's the same as running gos --compose, really. It is a quick way of composing new posts. Once composed, it will ask for your confirmation on whether the message should be queued or not.
+
+

How queueing works in gos


+
+When you place a message file in the gosDir, Gos processes it by moving the message through a queueing system before posting it to the target social media platforms. A message's lifecycle includes several key stages, from creation to posting, all managed through the ./db/platforms/PLATFORM directories.
+
+

Step-by-step queueing process


+
+1. Inserting a Message into gosDir: You start by creating a text file that represents your post (e.g., foo.txt) and placing it in the gosDir. When Gos runs, this file is processed. The easiest way is to use gosc here.
+
+2. Moving to the Queue: Upon running Gos, the tool identifies the message in the gosDir and places it into the queue for the specified platform. The message is moved into the appropriate directory for each platform in ./db/platforms/PLATFORM. During this stage, the message file is renamed to include a timestamp indicating when it was queued and given a .queued extension.
+
+*Example: If a message is queued for LinkedIn, the filename might look like this:*
+
+
+~/.gosdir/db/platforms/linkedin/foo.share:-mastodon.txt.20241022-102343.queued
+
+
+3. Posting the Message: Once a message is placed in the queue, Gos posts it to the specified social media platforms.
+
+4. Renaming to .posted: After a message is successfully posted to a platform, the corresponding .queued file is renamed to have a .posted extension, and the filename timestamp is also updated. This signals that the post has been processed and published.
+
+*Example - After a successful post to LinkedIn, the message file might look like this:*
+
+
+./db/platforms/linkedin/foo.share:-mastodon.txt.20241112-121323.posted
+
+
+

How message selection works in gos


+
+Gos decides which messages to post using a combination of priority, platform-specific tags, and timing rules. The message selection process ensures that messages are posted according to your configured cadence and targets while respecting pauses between posts and previously met goals.
+
+The key factors in message selection are:
+
+
    +
  • Target Number of Posts Per Week: The -target flag defines how many posts per week should be made to a specific platform. This target helps Gos manage the posting rate, ensuring that the right number of posts are made without exceeding the desired frequency.
    • +
  • Post History Lookback: The -lookback flag tells Gos how many days back to look in the post history to calculate whether the weekly post target has already been met. It ensures that previously posted content is considered before deciding to queue up another message.
    • +
  • Message Priority: Messages with no priority value are processed after those with priority. If two messages have the same priority, one is selected randomly.
    • +
  • Pause Between Posts: The -pauseDays flag allows you to specify a minimum number of days to wait between posts for the same platform. This prevents oversaturation of content and ensures that posts are spread out over time.
    • +

+

Post summary as gemini gemtext


+
+For my blog, I want to post a summary of all the social messages posted over the last couple of months. For an example, have a look here:
+
+https://foo.zone/gemfeed/2025-01-01-posts-from-october-to-december-2024.html
+
+To accomplish this, run:
+
+ +
gos --geminiSummaryFor 202410,202411,202412
+
+
+This outputs the summary for the three specified months, as shown in the example. The summary includes posts from all social media networks but removes duplicates.
+
+Also, add the --gemtexterEnable flag, if you are using Gemtexter:
+
+
+ +
gos --gemtexterEnable --geminiSummaryFor 202410,202411,202412
+
+
+Gemtexter
+
+In case there are HTTP links that translate directly to the Geminispace for certain capsules, specify the Gemini capsules as a comma-separated list as follows:
+
+ +
gos --gemtexterEnable --geminiSummaryFor 202410,202411,202412 --geminiCapsules "foo.zone,paul.buetow.org"
+
+
+It will then also generate Gemini Gemtext links in the summary page and flag them with (Gemini).
+
+

Conclusion


+
+Overall, this was a fun little Go project with practical use for me personally. I hope you also had fun reading this, and maybe you will use it as well.
+
+E-Mail your comments to paul@nospam.buetow.org :-)
+
+Back to the main site
+
+ + Random Weird Things - Part Ⅱ @@ -8756,140 +9143,6 @@ REMOTE|fishfinger|100|7|fstab|093f510ec5c0f512.h /usr/local ffs rw,wxallowed,nod 2022-03-06 The release of DTail 4.0.0
2021-04-22 DTail - The distributed log tail program

-Back to the main site
- - - - - After a bad night's sleep - - https://foo.zone/gemfeed/2022-09-30-after-a-bad-nights-sleep.html - 2022-09-30T09:53:23+03:00 - - Paul Buetow aka snonux - paul@dev.buetow.org - - Everyone has it once in a while: A bad night's sleep. Here I attempt to list valuable tips on how to deal with it. - -
-

After a bad night's sleep


-
-Published at 2022-09-30T09:53:23+03:00; Updated at 2022-10-12
-
-Everyone has it once in a while: A bad night's sleep. Here I attempt to list valuable tips on how to deal with it.
-
-
-               z
-                z
-                 Z
-       .--.  Z Z
-      / _(c\   .-.     __
-     | / /  '-;   \'-'`  `\______
-     \_\/'/ __/ )  /  )   |      \--,
-     | \`""`__-/ .'--/   /--------\  \
-      \\`  ///-\/   /   /---;-.    '-'
-jgs                (________\  \
-                             '-'
-
-
-

Table of Contents


-
-
-

Don't take the day off.


-
-Don't take a day off after not sleeping enough the previous night. That would be wasting the holiday allowance. It wouldn't be possible to enjoy my free time anyway, so why not just work? There's still a way for an IT Engineer to be productive (sometimes even more) with half or less of the concentration power available!
-
-

Start work early


-
-Probably I am already awake early and am unable to fall asleep again. My strategy here is to "attack" the day: Start work early and finish early. The early bird will also encounter fewer distractions from colleagues.
-
-

Sweat the small stuff


-
-There's never a shortage of small items to hook off my list. Most of these items don't require my full concentration power, and I will be happy to get them off my list so that the next day, after a good night's sleep, I can immerse myself again in focused, deep work with all concentration powers at hand.
-
-Examples of "small work items" are:
-
-
    -
  • Tidying up the workspace.
    • -
  • Installing pending computer software updates.
    • -
  • Going through the work backlog: Create new tickets, close obsolete ones, and roughly pre-plan upcoming work.
    • -
  • Finishing off the easy tickets from the current sprint.
    • -
  • Going through any tedious paperwork.
    • -
  • Catch up with the journal and mark off all trivial action items.
    • -

-

Enter the flow state


-
-I find it easy to enter the "flow state" after a bad night's sleep. All I need to do is to put on some ambient music (preferably instrumental chill house) and start to work on a not-too-difficult ticket.
-
-Usually, the "flow state" is associated with deep-focused work, but deep-focused work isn't easily possible under sleep deprivation. It's still possible to be in the flow by working on more manageable tasks and leaving the difficult ones for the next day.
-
-

Reschedule meetings


-
-I find engaging in discussions and demanding meetings challenging after a lousy night's sleep. I still attend the sessions I am invited to as "only" a participant, but I prefer to reschedule all meetings I am the primary driver of.
-
-This, unfortunately, also includes interviews. Interviews require full concentration power. So for interviews, I would find a colleague to step in for me or ask to reschedule the interview altogether. Everything else wouldn't make it justice and would waste everyone's time!
-
-

Invent


-
-The mind works differently under sleep deprivation: It's easier to invent new stuff as it's easier to have a look at things from different perspectives. Until an hour ago, I didn't know yet what I would be blogging about for this month, and then I just started writing this, and it took me only half an hour to write the first draft of this blog post!
-
-

Fast


-
-I don't eat breakfast, and I don't eat lunch on these days. I only have dinner. Not eating means my mind doesn't get foggy, and I keep up the work momentum. This is called intermittent fasting, which not only generally helps to keep the weight under control and boosts the concentration power. Furthermore, intermittent fasting is healthy. You should include it in your routine, even after a good night's sleep.
-
-

Stretch


-
-I won't have enough energy for strenuous physical exercise on those days, but a 30 to a 60-minute stretching session can make the day. Stretching will even hurt less under sleep deprivation! The stretching could also be substituted with a light Yoga session.
-
-

Walk


-
-Walking is healthy, and the time can be used to listen to interesting podcasts. The available concentration power might not be enough for more sophisticated audio literature. I will have enough energy for one or two daily walks (~10k steps for the day in total). Sometimes, I listen to music during walks. I also try to catch the bright sunlight.
-
-

Red Bull


-
-I don't think that Red Bull is a healthy drink. But once in a while, a can in the early afternoon brings wonders, and productivity will skyrocket. Other than Red Bull, drink a lot of water throughout the day. Don't forget to drink the sugar-free version; otherwise, your intermittent fast will be broken.
-
-

Power nap


-
-I don't know how to "enforce" a nap, but sometimes I manage to power nap, and it helps wonders. A 30-minute nap sometimes brings me back to normal. If you don't tend to fast as you are too hungry, it helps to try to nap approximately 30 minutes after eating something.
-
-

Don't take anything personally.


-
-It's much more challenging to keep the mind "under control" in this state. Every annoyance can potentially upset, which could reflect on the work colleagues. It is wise to attempt to go with a positive attitude into the day, always smile and be polite to the family and colleagues at work. Don't let anything drop out to the people next; they don't deserve it as they didn't do anything wrong! Also, remember, it can't be controlled at all. It's time to let go of the annoyances for the day.
-
-

Meditate


-
-To keep the good vibe, it helps to meditate for 10 minutes. Meditation must nothing be fancy. It can be just lying on the sofa and observing your thoughts as they come and go. Don't judge your thoughts, as that could put you in a negative mood. It's not necessary to sit in an uncomfortable Yoga pose, and it is not required to chant "Ohhmmmmm".
-
-

Write things down


-
-Sometimes something requiring more concentration power demands time. This is where it helps to write a note in a journal and return to it another day. This doesn't mean slacking off but managing the rarely available concentration power for the day. I might repeat myself: Today, sweat all the small stuff. Tomorrow, do the deep-focused work on that crucial project again.
-
-It's easier to forget things on those days, so everything should be written down so that it can be worked off later. Things written down will not be overlooked!
-
-

Social media


-
-I wouldn't say I like checking social media, as it can consume a lot of time and can become addictive. But once in a while, I want to catch up with my "networks". After a bad night's sleep, it's the perfect time to check your social media. Once done, you don't have to do it anymore for the next couple of days!
-
-E-Mail your comments to paul@nospam.buetow.org :-)
-
Back to the main site
 diff --git a/gemfeed/index.html b/gemfeed/index.html index e997f0c7..df598414 100644 --- a/gemfeed/index.html +++ b/gemfeed/index.html @@ -15,6 +15,7 @@

To be in the .zone!



+2025-03-05 - Sharing on Social Media with Gos v1.0.0
2025-02-08 - Random Weird Things - Part Ⅱ
2025-02-01 - f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts
2025-01-15 - Working with an SRE Interview
diff --git a/gemfeed/sharing-on-social-media-with-gos/gos-screenshot.png b/gemfeed/sharing-on-social-media-with-gos/gos-screenshot.png new file mode 100644 index 00000000..cc873df3 Binary files /dev/null and b/gemfeed/sharing-on-social-media-with-gos/gos-screenshot.png differ diff --git a/gemfeed/sharing-on-social-media-with-gos/gos.png b/gemfeed/sharing-on-social-media-with-gos/gos.png new file mode 100644 index 00000000..dc2808ce Binary files /dev/null and b/gemfeed/sharing-on-social-media-with-gos/gos.png differ diff --git a/index.html b/index.html index 856605ca..d804fafb 100644 --- a/index.html +++ b/index.html @@ -13,7 +13,7 @@

Hello!



-This site was generated at 2025-02-23T21:49:52+02:00 by Gemtexter
+This site was generated at 2025-03-04T21:22:08+02:00 by Gemtexter

Welcome to the ...

@@ -51,6 +51,7 @@

Posts



+2025-03-05 - Sharing on Social Media with Gos v1.0.0
2025-02-08 - Random Weird Things - Part Ⅱ
2025-02-01 - f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts
2025-01-15 - Working with an SRE Interview
diff --git a/uptime-stats.html b/uptime-stats.html index 0068cc7b..d547b88b 100644 --- a/uptime-stats.html +++ b/uptime-stats.html @@ -13,7 +13,7 @@

My machine uptime stats



-This site was last updated at 2025-02-23T21:49:51+02:00
+This site was last updated at 2025-03-04T21:22:08+02:00

The following stats were collected via uptimed on all of my personal computers over many years and the output was generated by guprecords, the global uptime records stats analyser of mine.

-- cgit v1.2.3